Yes, routinely. And it's not that hard to do while you're not attempting to twiddle with either OS internals, or direct hardware. And even for those, there's likely an interop layer that exists, or could be written, to smooth over even those differences. It _does_ require some discipline when coding though.
OK, this is a pet peeve of mine, but why the heck do these get called "Zero-day vulnerabilities". Yes, I understand that the definition is that the zero-day refers to the time between the vulnerability is made public and the time that an exploit is made available. However, I don't get why this needs an additional moniker on top of being a vulnerability in the first place. Don't most of the vulnerabilities have an exploit the same day that the vulerability is published (wouldn't you want to have a proof of concept that the vulnerability exists, I'd assume one was created.)? I haven't heard of many "7-day vulnerabilities". So why isn't the "zero-day" thing implied? If a vulnerability is exposed and there is no exploit available, the vendors already make statements such as "there are no known exploits for this". Where I would think that the "zero-day" moniker would actually add some information is if the vulnerability is exposed on the zeroith day of release of the product in question. _That_ would be something to give a special name to. That would mean that the developer has botched it so badly that it didn't even take 24 hours before someone found a hole. As it is now (IMHO) the "zero-day" moniker is simply being alarmist and only trying to add sparkle to the term, and carries no significant information.
Apparently you don't understand the idea of faulty arguments. By stating CDMC the person isn't dismissing the results out of hand. The person is stating that the argument is faulty and that the conclusion hasn't been proven (not necessarily wrong, but hasn't been proven right either).
And that defeats the purpose. The internet got away from classes of IPs and went to classless delegation for a reason. Now they want to bring it back. And if the concern was really for geolocation purposes, then the ISP can simply put a recursive nameserver close to the clients (say only 1 hop up from the client). Since all of the client's traffic must pass by that hop anyway, that DNS will be close enough to determine where the client is.
Actually, that's exactly how I'm describing the iPad to anybody. It's an iPod touch with larger screen real estate. I saw no other significant features over the iPod touch. The eBook thing is already done on the iPod (Stanza and others), iWork could have been done on the iPod (but the screen size could make it inconvenient). The only real extra feature that I saw was the 3G modem, but that simply makes it a little closer to an iPhone. Also, tying it to the app store I find too limiting. It otherwise could have been a viable alternate computing platform, but if I wanted to do something for the internal employees of my company, I'd have to buy into the Apple developer network, and get my app approved by the app store before I could load it onto the iPad (Jailbreaking is not an acceptable option). 10 hour battery life is not enough for an ebook reader. 2 weeks on my Kindle.
If I've got a device that size, I'll go use my desktop. And for book reading, the 10 hour battery life is lousy, I'll keep my Kindle with the 2 week battery life. For movies, I've got a TV with an actual sound system.
Sorry, I'm underwhelmed by the iPad. It's an iPod with more screen real estate, and still no way to distribute one's own apps except by the app sort (OK, other than jailbreaking it).
How many home users actually use more than one of the 5 IP addresses that they've been allowed? And since they're assigned by DHCP, there's not 5 specific IPs for that user, but 5 IPs out of whatever IP space has been assigned to that network segment.
You do realize that some of those types of comments aren't really intended for humans anyway, but more for documentation generators like javadoc and doc++ ?
Breach of contract. The user had contracted to use XBL with an unmodded XBox. The user then uses a modded XBox. The remainder of the XBL fee is forfeit. MS (in this case) isn't terminating the contract on a whim, the user broke the contract.
IMHO, a zero-day exploit should be exactly that. An exploit that was found on the zeroith day of release. Otherwise what makes a "zero day" exploit so special that it needs the extra moniker of "zero day"? Why is it so special that if you find an exploit, and have code to exploit it the same day? How else did you verify that the exploit actually works without crafting an appropriate program to exploit t?
A true "zero day" epxloit would be a special thing as that would represent a hole so easy to find that it took less than 24 hours to find the hole from the time that the researcher could obtain the application. Applying the term "zero day" to other types of exploits is simply trying to attach some sort of buzzword to artificially increase the prestige of the explot.
For that matter, why are we still defining code chunks via brackets instead of the indentation that's already there?
Are you insane? Have you ever written a parser? And being dependent on particular whitespace is really asking for trouble. Now, are those tabs or spaces? How many spaces? One of the earlier languages had position dependent coding (code had to start on column 3 or something like that. The name eludes me at the moment).
Regarding side-buttons? I love my side buttons. However, it is a small button and doesn't rest under my thumb in the normal rest position. Microsoft Comfort Optical Mouse 3000. (OK, it is a wired mouse).
Are you willing to pay for the proofs of the program's correctness? And then prove it's correctness in the presence of failing hardware? Hint: it wouldn't be cheap, nor would it be fast.
You know what else you can do with this? Instead of a wristwatch, how about an anklet? Oh yeah, they already have them. Used for people under house arrest....
Um... Why is there even mention of the Harper government (Federal) when this was the BC Court of Appeal (Provincial)? You'd want to poke at the Campbell government.
People who need to learn to type will learn on their own
Ha ha, right... tell that to half of the programmers at my workplace --- have you actually looked at a typical workplace, or are you still in school?
I'd have to agree with this. I'm rather shocked at how badly many of the other developers in my shop are at typing. They tend to be amazed at how well I can type, how well I can type while talking to them, etc. I would have thought that the daily exposure would encourage them.... apparently not.
Hardly a tiny spot. It's still going strong. And every smartphone I've used has had bad characteristics. Mostly in battery life, the rest being network traffic charges. I want my phone to last over a week between charges (my current phone does), not a day (my previous smartphone).
Why would this possibly be a minefield or even difficult? The licensing choice is right there in the requirements: "Write a GPLed...". Use the GPL, done. OK, one choice: GPLv2 vs. GPLv3. Although in common usage GPL refers to GPLv2, anytime someone means GPLv3 it's been rather carefully specified that it is GPLv3 that is being used.
Yep, in fine/. tradition, I didn't RTFA. However now it's proposing that an ISP runs a large proxy for their clients. So the FTP issue goes away, but now you've got an intentional man-in-the-middle server in your ISP. Why bother hacking individual clients when you can hack these proxy and get access to hundreds to thousands of users?
Doesn't anyone remember FTP? And why Passive-mode FTP was developed? All of the same reasons why this isn't a good idea. Your web browser ends up behind a NAT firewall and poof, this no longer works. (Without some deep packet inspection on the firewall to automatically open the ports, or UPnP, or SOCKS, or some other protocol for the web client to negotiate with the firewall to allow the connections).
I can see these things coming up:
1) Companies requiring genetic therapy to retroactively apply this mutation to you.
2) Extending the work day as the workers don't need as much sleep
Slashdot Mirror
You went rock climbing and didn't have everything tethered to yourself?
Yes, routinely. And it's not that hard to do while you're not attempting to twiddle with either OS internals, or direct hardware. And even for those, there's likely an interop layer that exists, or could be written, to smooth over even those differences. It _does_ require some discipline when coding though.
OK, this is a pet peeve of mine, but why the heck do these get called "Zero-day vulnerabilities". Yes, I understand that the definition is that the zero-day refers to the time between the vulnerability is made public and the time that an exploit is made available. However, I don't get why this needs an additional moniker on top of being a vulnerability in the first place. Don't most of the vulnerabilities have an exploit the same day that the vulerability is published (wouldn't you want to have a proof of concept that the vulnerability exists, I'd assume one was created.)? I haven't heard of many "7-day vulnerabilities". So why isn't the "zero-day" thing implied? If a vulnerability is exposed and there is no exploit available, the vendors already make statements such as "there are no known exploits for this". Where I would think that the "zero-day" moniker would actually add some information is if the vulnerability is exposed on the zeroith day of release of the product in question. _That_ would be something to give a special name to. That would mean that the developer has botched it so badly that it didn't even take 24 hours before someone found a hole. As it is now (IMHO) the "zero-day" moniker is simply being alarmist and only trying to add sparkle to the term, and carries no significant information.
Apparently you don't understand the idea of faulty arguments. By stating CDMC the person isn't dismissing the results out of hand. The person is stating that the argument is faulty and that the conclusion hasn't been proven (not necessarily wrong, but hasn't been proven right either).
And that defeats the purpose. The internet got away from classes of IPs and went to classless delegation for a reason. Now they want to bring it back. And if the concern was really for geolocation purposes, then the ISP can simply put a recursive nameserver close to the clients (say only 1 hop up from the client). Since all of the client's traffic must pass by that hop anyway, that DNS will be close enough to determine where the client is.
Actually, that's exactly how I'm describing the iPad to anybody. It's an iPod touch with larger screen real estate. I saw no other significant features over the iPod touch. The eBook thing is already done on the iPod (Stanza and others), iWork could have been done on the iPod (but the screen size could make it inconvenient). The only real extra feature that I saw was the 3G modem, but that simply makes it a little closer to an iPhone. Also, tying it to the app store I find too limiting. It otherwise could have been a viable alternate computing platform, but if I wanted to do something for the internal employees of my company, I'd have to buy into the Apple developer network, and get my app approved by the app store before I could load it onto the iPad (Jailbreaking is not an acceptable option). 10 hour battery life is not enough for an ebook reader. 2 weeks on my Kindle.
If I've got a device that size, I'll go use my desktop. And for book reading, the 10 hour battery life is lousy, I'll keep my Kindle with the 2 week battery life. For movies, I've got a TV with an actual sound system. Sorry, I'm underwhelmed by the iPad. It's an iPod with more screen real estate, and still no way to distribute one's own apps except by the app sort (OK, other than jailbreaking it).
Perhaps because one does not wish to engage in copyright infringement?
How many home users actually use more than one of the 5 IP addresses that they've been allowed? And since they're assigned by DHCP, there's not 5 specific IPs for that user, but 5 IPs out of whatever IP space has been assigned to that network segment.
Sorry, you've failed code review. I don't see a comments on the "else" line.
You do realize that some of those types of comments aren't really intended for humans anyway, but more for documentation generators like javadoc and doc++ ?
Independance War somewhat had this (Speeds around c), as did Elite II: Frontier (having to slingshot around your combat due to realistic physics).
Breach of contract. The user had contracted to use XBL with an unmodded XBox. The user then uses a modded XBox. The remainder of the XBL fee is forfeit. MS (in this case) isn't terminating the contract on a whim, the user broke the contract.
A true "zero day" epxloit would be a special thing as that would represent a hole so easy to find that it took less than 24 hours to find the hole from the time that the researcher could obtain the application. Applying the term "zero day" to other types of exploits is simply trying to attach some sort of buzzword to artificially increase the prestige of the explot.
For that matter, why are we still defining code chunks via brackets instead of the indentation that's already there?
Are you insane? Have you ever written a parser? And being dependent on particular whitespace is really asking for trouble. Now, are those tabs or spaces? How many spaces? One of the earlier languages had position dependent coding (code had to start on column 3 or something like that. The name eludes me at the moment).
Regarding side-buttons? I love my side buttons. However, it is a small button and doesn't rest under my thumb in the normal rest position. Microsoft Comfort Optical Mouse 3000. (OK, it is a wired mouse).
Are you willing to pay for the proofs of the program's correctness? And then prove it's correctness in the presence of failing hardware? Hint: it wouldn't be cheap, nor would it be fast.
You know what else you can do with this? Instead of a wristwatch, how about an anklet? Oh yeah, they already have them. Used for people under house arrest....
Um... Why is there even mention of the Harper government (Federal) when this was the BC Court of Appeal (Provincial)? You'd want to poke at the Campbell government.
People who need to learn to type will learn on their own
Ha ha, right ... tell that to half of the programmers at my workplace --- have you actually looked at a typical workplace, or are you still in school?
I'd have to agree with this. I'm rather shocked at how badly many of the other developers in my shop are at typing. They tend to be amazed at how well I can type, how well I can type while talking to them, etc. I would have thought that the daily exposure would encourage them.... apparently not.
Hardly a tiny spot. It's still going strong. And every smartphone I've used has had bad characteristics. Mostly in battery life, the rest being network traffic charges. I want my phone to last over a week between charges (my current phone does), not a day (my previous smartphone).
Why would this possibly be a minefield or even difficult? The licensing choice is right there in the requirements: "Write a GPLed ...". Use the GPL, done. OK, one choice: GPLv2 vs. GPLv3. Although in common usage GPL refers to GPLv2, anytime someone means GPLv3 it's been rather carefully specified that it is GPLv3 that is being used.
Yep, in fine /. tradition, I didn't RTFA. However now it's proposing that an ISP runs a large proxy for their clients. So the FTP issue goes away, but now you've got an intentional man-in-the-middle server in your ISP. Why bother hacking individual clients when you can hack these proxy and get access to hundreds to thousands of users?
Doesn't anyone remember FTP? And why Passive-mode FTP was developed? All of the same reasons why this isn't a good idea. Your web browser ends up behind a NAT firewall and poof, this no longer works. (Without some deep packet inspection on the firewall to automatically open the ports, or UPnP, or SOCKS, or some other protocol for the web client to negotiate with the firewall to allow the connections).
I can see these things coming up: 1) Companies requiring genetic therapy to retroactively apply this mutation to you. 2) Extending the work day as the workers don't need as much sleep