The legislation doesn't say break, it says circumvent. If you are able to copy the disk (which is what the DRM attempts to prevent) by copying the DRM as well, then you effectively circumvented it.
Except that those locks are designed to prevent you from copying the media. So if you copy the DVD/CD (even 1:1 bitwise), you have technically circumvented the lock (notice the legislation says circumvent, not break!)
This is meant as an alternative to requiring quantumly entangled bits to be distributed to everyone in pairs. I don't think this is meant as a way for random people on the internet to communicate, but for creating secure connections between 2 parties that consistently communicate (bank back-ends, government offices, university campuses, etc).
You don't wrap hard drives in it, you wrap full towers and other generally static-safe systems in it. If your enclosures can't handle the shock of carpets, I sure as hell hope nobody with some built-up static in them touches anything!
Out of pure curiosity, if the network is capable of being operated at the remote location and the remote location doesn't get the hurricanes, why don't they just LEAVE the network there...?
Seeing as he obviously has enough time to wait for slashdot responses, I'd just start a new offsite-backup run and lock the doors on my way home to evacuate my family.
As much as I disagree with the whole hardware-evacuation idea in the first place (backups + insurance is ALL you should need), I'd just like to mention that carpeted floors + box cutter = blankets:)
If you find out you work for a business with large quantities of server equipment that doesn't have FIRE INSURANCE, the only things you should take with you are
- 1 UPS
- 1 computer (desktop/laptop/whatever)
- 1 printer
- 1 reem of paper
Now you have all you need to print resume's while driving the hell away from that building as fast as you can!
Personally I wouldn't take anything unless it is 100% un-replaceable (discontinued systems and since-last-offisite-transfer backups). Remember, your insurance will (if the person that negotiated it wasn't a complete moron) cover ALL hardware that is caught in the fire, they might NOT cover hardware that you broke in the U-Haul truck while trying to save it. You should already have offsite backups, so at the most you should save the "didn't make it to offsite yet" recent backups (1 day to 1 week's worth depending on your setup). For everything else: let it burn, that's what you pay those high insurance premiums for! If your insurance company doesn't like that plan, THEY can move it out of the f*$ing building.
Not really, they only need 1 cert per HTTPS website (you can even reuse each one for every person in the company). HTTP websites would just proxy normally (no cert required). HTTPS sites tend to be few and popular, so with only generating 100 certs you could easily cover 90% of webmail, IM, bank, insurance and social network website your employees would ever access.
Once HTTPS becomes more commonplace, there WILL be more certs needing generation, but you still only need 1 cert per domain.
I don't think any ISP's are installing root certs right now (we would have heard of it), but most large ISP's expect you to install a CD full of "drivers and stuff" when you sign up. They could EASILY stick a root cert in there. Then again, technical people (those that would notice an extra root cert) just use the CD as a coaster, so maybe they ARE already doing this....
Slashdot Mirror
The legislation doesn't say break, it says circumvent. If you are able to copy the disk (which is what the DRM attempts to prevent) by copying the DRM as well, then you effectively circumvented it.
Except that those locks are designed to prevent you from copying the media. So if you copy the DVD/CD (even 1:1 bitwise), you have technically circumvented the lock (notice the legislation says circumvent, not break!)
This is meant as an alternative to requiring quantumly entangled bits to be distributed to everyone in pairs. I don't think this is meant as a way for random people on the internet to communicate, but for creating secure connections between 2 parties that consistently communicate (bank back-ends, government offices, university campuses, etc).
Except one-time pads don't have keys.
Yes, yes they do.
Actually they don't, they ARE keys.
Computational power can simply brute any public key into the private, given enough time.
How much do you really care that your great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great, great (repeat about 10 million times) grandchildren may stumble accross a computer that's been breaking your key for the last couple million years?
3) 'ps aux | grep ">> /dev/null"' by any user where process pid's and names are not protected (FreeBSD protects, Linux does not).
1) I think you meant "echo", unless of course your message is already in plaintext! /dev/null" ~/.bash_history
2) grep ">>
Gah, spell checker. See what I mean?!?
You don't wrap hard drives in it, you wrap full towers and other generally static-safe systems in it. If your enclosures can't handle the shock of carpets, I sure as hell hope nobody with some built-up static in them touches anything!
Firefox's spellchecker keeps disabling itself and it IS starting to piss me off!
Out of pure curiosity, if the network is capable of being operated at the remote location and the remote location doesn't get the hurricanes, why don't they just LEAVE the network there...?
Oh, no doubt there, but they'll probably just pull the same "here's a crappy binary that sorta works" stunt they do with laptop cards.
Intel makes more than just the GMA950 you know.
I was under the assumption that you thought router-blocked was equivalent to not-blocked-at-all.
That's a common misconception in many countries, I *highly* recommend you verify that information for your geographic area.
You do know slashdot already uses it right...?
Those "employees" are probably using all the trunk space they have for the stuff they are rescuing from their homes!
Seeing as he obviously has enough time to wait for slashdot responses, I'd just start a new offsite-backup run and lock the doors on my way home to evacuate my family.
I don't know about that. "Have offsite backups and fire insurance." sounds pretty fucking simple to me!
As much as I disagree with the whole hardware-evacuation idea in the first place (backups + insurance is ALL you should need), I'd just like to mention that carpeted floors + box cutter = blankets :)
If you find out you work for a business with large quantities of server equipment that doesn't have FIRE INSURANCE, the only things you should take with you are
- 1 UPS
- 1 computer (desktop/laptop/whatever)
- 1 printer
- 1 reem of paper
Now you have all you need to print resume's while driving the hell away from that building as fast as you can!
Personally I wouldn't take anything unless it is 100% un-replaceable (discontinued systems and since-last-offisite-transfer backups). Remember, your insurance will (if the person that negotiated it wasn't a complete moron) cover ALL hardware that is caught in the fire, they might NOT cover hardware that you broke in the U-Haul truck while trying to save it. You should already have offsite backups, so at the most you should save the "didn't make it to offsite yet" recent backups (1 day to 1 week's worth depending on your setup). For everything else: let it burn, that's what you pay those high insurance premiums for! If your insurance company doesn't like that plan, THEY can move it out of the f*$ing building.
One of the common reasons is the detection of malware.
Not really, they only need 1 cert per HTTPS website (you can even reuse each one for every person in the company). HTTP websites would just proxy normally (no cert required). HTTPS sites tend to be few and popular, so with only generating 100 certs you could easily cover 90% of webmail, IM, bank, insurance and social network website your employees would ever access.
Once HTTPS becomes more commonplace, there WILL be more certs needing generation, but you still only need 1 cert per domain.
I don't think any ISP's are installing root certs right now (we would have heard of it), but most large ISP's expect you to install a CD full of "drivers and stuff" when you sign up. They could EASILY stick a root cert in there. Then again, technical people (those that would notice an extra root cert) just use the CD as a coaster, so maybe they ARE already doing this....