"And their firewalls didn't detect the melamine in the imported DNS records? Pitiful."
I was going to recommend lead but I forgot this isn't the 80s-90s any longer.
Lead would've made a better explanation for the slower speeds and 'cancerous' degradation that's been showing up on The Internet Traffic Report (currently at 62% as of this posting) with lead being heavier and all that fun chemistry stuff.;)
The entire industry couldn't handle the allied front of "First Sale Doctrine" lawsuits that would come about as a result. Very rarely has an allied front been used in a court but the few times it has it's been devastating to the defendant when settlement isn't an option. When an entire class of people come after you in court, you fucked up and even the court knows it.
"If my console breaks and I have to get it replaced I am going to be pissed off if I have to re-purchase DLC that I already own."
Well, considering those DLCs are usually tied to an account made on the console, as long as you remember your login and password there should be no problems with that.
But they can't determine without actually having the hardware to install and test the game to make sure that either the DLC code has been used or not - that's too much time, money, and effort.
'If there's some kind of bold feature list that says "free downloadable content" on the game's cover, then GameSpot and other sellers need to take a marker or sticker and block it out, because otherwise it's false advertising."
Just how is it GS's fault that the PUBLISHER THAT PRINTED THE GAME BOX contains false advertising?
I think you might want to look up some prior caselaw concerning modified product without permission - even a modified game box can be considered a breach of trademark. Mattel did this with modified Barbie dolls that had been legally purchased beforehand.
If you understand the native language for your target machine, you're better off. If the iPhone kept to the same hardware and only updated hardware revisions every once in a while unlike the current every six months or a year nonsense, it wouldn't be too terribly difficult to write bulletproof code and apps.
Yes, since in order to understand assembler you need to understand both the hardware itself and it's actual physical limitations, and you need to know the language.
I've got a recompiled MenuetOS install on my desktop, built by a friend of mine that knows a fair bit more about AMD64 than I. I've purposely left it wide-open direct-connect to the cable modem and invited people to hack it when I feel like testing a new module he's made. I still do. It's been bulletproof. I'm waiting for his router module/frontend with much anticipation, as I'm getting sick of my Linksys with DD-WRT and it's being written for Atheros.
Hardware exploits are typically much harder to accomplish versus software, generally because of the straightforward layout of the circuits versus the convoluted nature of software programming.
It barely provides a solution for any percentage of users, that's the problem, especially if taken at the face value it has been stated - livecd + netbook are almost always exclusionary.
Then we have the issue of making sure that one distro is capable of supporting all of the wireless cards netbooks use (not easy) and maybe even laptops or desktops, since not everyone will have a netbook.
Flash drives to just hand out will get prohibitvely expensive soon enough.
This is really a non-win for anybody, as far as I can see.
Good thing I have two desktops, two laptops, a hypervisor-cracked OS-installed PS3, and I'll be buying a netbook sometime soon pretty much for business/banking travel.
Assembler, by a rule, is just harder. Most 'programmers' couldn't understand the machine's native language if their life depended upon it. They are relying upon someone else's code to translate down to that, and if those methods are flawed they're screwed.
All security begins with the basics, and for computing devices, that basic is their native machine language. If you ignore the basics, you're going to be fucked later on.
Also, if you're too far away from the router, you're too far away. Just because it can transmit further out doesn't mean your wireless card can, unless you have utilities that allow you to adjust the transmission power. (Like in the DD-WRT firmware, you can take a Linksys from 71mW to 251mW and I can receive the signal out at the pool. I still can't access it because my laptop card won't transmit that far.
Some of these exploits only took two weeks from conception to exploitation. TWO WEEKS. New product comes out, and POSSIBLY in 14 days you're fucked?
It seriously sounds like these idiots need to drop all high-level programming and go straight back to learning the BASICS first. Assembler and tight fucking code and source control.
'Tell me when you see stadiums with concrete roofs."
What sort of stadium? I know of several marine life stadiums with concrete roofs. I can think of one in Florida, one in Washington, and one in Mississippi. I'm sure there are several in Oregon. In fact, the ENTIRE STRUCTURE for these stadiums is solid concrete.
Slashdot Mirror
"And their firewalls didn't detect the melamine in the imported DNS records? Pitiful."
I was going to recommend lead but I forgot this isn't the 80s-90s any longer.
Lead would've made a better explanation for the slower speeds and 'cancerous' degradation that's been showing up on The Internet Traffic Report (currently at 62% as of this posting) with lead being heavier and all that fun chemistry stuff. ;)
"So it's a DNS for Chinese people. Why does ISP's in other countries use it?"
Because they're just as controlling. Duh.
The entire industry couldn't handle the allied front of "First Sale Doctrine" lawsuits that would come about as a result. Very rarely has an allied front been used in a court but the few times it has it's been devastating to the defendant when settlement isn't an option. When an entire class of people come after you in court, you fucked up and even the court knows it.
"If my console breaks and I have to get it replaced I am going to be pissed off if I have to re-purchase DLC that I already own."
Well, considering those DLCs are usually tied to an account made on the console, as long as you remember your login and password there should be no problems with that.
Even Steam figured this one out.
But they can't determine without actually having the hardware to install and test the game to make sure that either the DLC code has been used or not - that's too much time, money, and effort.
Because it's not gamestop creating the false advertising, it's the fucking game publisher.
Did you people not pay attention when I smacked EA over the Spore DRM and misleading advertising? Go check out McQuown vs Electronic Arts and read.
No, the people that printed the box are liable, as it's their product and their advertisement.
Liability is a bitch.
'If there's some kind of bold feature list that says "free downloadable content" on the game's cover, then GameSpot and other sellers need to take a marker or sticker and block it out, because otherwise it's false advertising."
Just how is it GS's fault that the PUBLISHER THAT PRINTED THE GAME BOX contains false advertising?
I think you might want to look up some prior caselaw concerning modified product without permission - even a modified game box can be considered a breach of trademark. Mattel did this with modified Barbie dolls that had been legally purchased beforehand.
I got news for you.
Any sale is a retail sale unless you have a reseller license.
Check your local state laws on sales tax - it explicitly defines a retail sale.
If you understand the native language for your target machine, you're better off. If the iPhone kept to the same hardware and only updated hardware revisions every once in a while unlike the current every six months or a year nonsense, it wouldn't be too terribly difficult to write bulletproof code and apps.
Yes, since in order to understand assembler you need to understand both the hardware itself and it's actual physical limitations, and you need to know the language.
I've got a recompiled MenuetOS install on my desktop, built by a friend of mine that knows a fair bit more about AMD64 than I. I've purposely left it wide-open direct-connect to the cable modem and invited people to hack it when I feel like testing a new module he's made. I still do. It's been bulletproof. I'm waiting for his router module/frontend with much anticipation, as I'm getting sick of my Linksys with DD-WRT and it's being written for Atheros.
Hardware exploits are typically much harder to accomplish versus software, generally because of the straightforward layout of the circuits versus the convoluted nature of software programming.
"How about a USB pen drive writing port on the cash machine?"
Oh yes, that'd be pretty EASILY exploited.
No thanks.
It barely provides a solution for any percentage of users, that's the problem, especially if taken at the face value it has been stated - livecd + netbook are almost always exclusionary.
Then we have the issue of making sure that one distro is capable of supporting all of the wireless cards netbooks use (not easy) and maybe even laptops or desktops, since not everyone will have a netbook.
Flash drives to just hand out will get prohibitvely expensive soon enough.
This is really a non-win for anybody, as far as I can see.
Good thing I have two desktops, two laptops, a hypervisor-cracked OS-installed PS3, and I'll be buying a netbook sometime soon pretty much for business/banking travel.
Not counting the modded PSP.
I have no good sense of pornographic humor. Most of my humor involves dead baby jokes, ethnic jokes, and schadenfreude.
Yes, they'll spend all that money to have bootable LiveDrives to hand out?
"They could ship you a free NetBook w/ CD."
How many netbooks actually come with an optical drive?
"Gives the user something physical to insert"
Except the netbook owners, whom have no optical drive.
I work silicon, not software. I don't get exploited, nimrod, because I leave nothing for anyone to exploit.
Assembler, by a rule, is just harder. Most 'programmers' couldn't understand the machine's native language if their life depended upon it. They are relying upon someone else's code to translate down to that, and if those methods are flawed they're screwed.
All security begins with the basics, and for computing devices, that basic is their native machine language. If you ignore the basics, you're going to be fucked later on.
Also, if you're too far away from the router, you're too far away. Just because it can transmit further out doesn't mean your wireless card can, unless you have utilities that allow you to adjust the transmission power. (Like in the DD-WRT firmware, you can take a Linksys from 71mW to 251mW and I can receive the signal out at the pool. I still can't access it because my laptop card won't transmit that far.
You DO realize Tennessee was a major front line in our own civil war, yes? So what nonsense are you spewing?
Some of these exploits only took two weeks from conception to exploitation. TWO WEEKS. New product comes out, and POSSIBLY in 14 days you're fucked?
It seriously sounds like these idiots need to drop all high-level programming and go straight back to learning the BASICS first. Assembler and tight fucking code and source control.
'Tell me when you see stadiums with concrete roofs."
What sort of stadium? I know of several marine life stadiums with concrete roofs. I can think of one in Florida, one in Washington, and one in Mississippi. I'm sure there are several in Oregon. In fact, the ENTIRE STRUCTURE for these stadiums is solid concrete.
make a plane out of this stuff and put it in the air, as long as it is in the air, it's earthquake-proof 100%.