On the OTHER hand... we could have assholes running around changing legitimate plates to alert that the car is STOLEN
No hacking needed. A few stickers will do the job.
(And is a good way to protest this - get everybody to put 'STOLEN' stickers on their cars to waste police time - it's easy to claim you just came out of Walmart and somebody must have done it while you were in there. There's no way they can prove it's not true...)
No, that's not sufficient. Encrypted data still exposes metadata: Who, when, where.
The NSA isn't going to learn much from knowing you write to your mom. There's anonymous mail drops, remailers, etc. for the important stuff. We shouldn't delay encryption of the contents just because the system isn't flawless yet.
How about an encryption key that evolves based on previous emails, so that unless the NSA have your entire email history with another person stored and unencrypted, they will have to brute force the key each time.
a) There's no reason to the NSA won't have that complete history - they're spying on you, right? b) The NSA can't brute force your key. They don't have enough electricity to power a computer that big, or even a place to hide it (it would be bigger then the Earth).
You don't even need to exchange the key through gmail. You can simply host the encrypted mail on Google's servers, download it, and exchange the key through a third party service.
That doesn't sound as 'simple' as via email attachments. The point is to make it a complete no-brainer for people to use. Any extra step is one step too many.
That's never going to be even moderately secure. If you type the cleartext into a browser window with Javascript or read the cleartext in a browser window with Javascript, then any encryption is moot.
Packet sniffers would soon reveal any nefarious business, and there's plenty of people who'd run a sniffer just to be able to prove something was going on.
The real problem right now is proving anything - anybody in a position to provide hard proof is being gagged. An encrypting plugin plus sniffer would enable anybody to prove it.
even if it worked, it would still leave the metadata wide open: Who, when, where.
I admit that's a tougher problem to solve.
One step at a time, though. Let's start by encrypting the contents...
Make it really easy to encrypt/base-64 encode your emails before they're uploaded to Gmail/Hotmail/Yahooo/Facebook/etc.
"Transparent to the user" would be ideal. I don't know if a browser plugin could manage that but I don't see why not - just intercept the "send" process.
Encryption keys could be generated automatically during the first few exchanges with another person by attaching information to the end of the email. After two or three replies the displayed email address turns green and you're good to go.
Yes, they could do mass man-in-the-middle attacks during the key exchange but so long as two people can verify their keys by phone (or whatever) then we'll know about it. More importantly, we'll be able to prove they're doing it. That would lead to more news stories about what the NSA does and more public awareness of the importance of installing an encryption plugin.
If no compelling medical issue requires sequencing in a newborn, it is invasive and coercive to conduct it.
Why? They might have some genetic problem which will appear later in life.
The real problem isn't the medical implications, it's the fact that we know the government is going to want a copy of the data (for the baby's own protection, of course...)
There is not going to be privacy as long as the physical links are not in the hands of the people. You are not the king of your castle if you rent. People need to start digging ditches and burying fiber to connect to their neighbors.
...or just encrypt all the data that passes along the existing cables.
To claim "people don't want to work" I say is an appeal to emotion argument that nobody should fall for (yet sadly many do). People do want to work assuming that they get paid fairly for the work being done.
Try getting the playstaion generation to go outdoors and move plant pots around all day. You'll soon be browsing robot catalogs...
It also means that if one cell fails, the car isn't crippled in a major way. You need lots of little cells to fail for the car to be disabled, instead of just one big cell failing.
I'm fairly sure I used the words 'few dozen'.
If you have a few dozen big cells you can tell which one failed and replace it. Back to full range again.
Little ones failing inside sealed boxes is harder (more expensive) to route around and harder to fix. It's the battery equivalent of the death of a thousand cuts.
Slashdot Mirror
Google for "Related-Key Attack on the Full AES-256"
http://eprint.iacr.org/2009/317.pdf
How will a regular musician know if the format or encoding is common enough to have decoders in the future? That's hard to predict.
No it isn't. "RAW" format will always be readable.
On the OTHER hand... we could have assholes running around changing legitimate plates to alert that the car is STOLEN
No hacking needed. A few stickers will do the job.
(And is a good way to protest this - get everybody to put 'STOLEN' stickers on their cars to waste police time - it's easy to claim you just came out of Walmart and somebody must have done it while you were in there. There's no way they can prove it's not true...)
Driving with a broken plate will be an offense.
Just be thankful they don't feel the urge to explain what 'scrambling' is.
(Somehow everybody knows what 'scrambling' is. From birth.)
128-bit is impossible to brute force with any conceivable amount of resources.
Be careful: 256-bit AES turned out to be not much stronger than 128-bit.
(256 bit AES is a hacked-around version of 128 bit AES, made to satisfy the NIS competition requirements. It didn't really work out...)
No, that's not sufficient. Encrypted data still exposes metadata: Who, when, where.
The NSA isn't going to learn much from knowing you write to your mom. There's anonymous mail drops, remailers, etc. for the important stuff. We shouldn't delay encryption of the contents just because the system isn't flawless yet.
https://en.wikipedia.org/wiki/Nirvana_fallacy#Perfect_solution_fallacy
How about an encryption key that evolves based on previous emails, so that unless the NSA have your entire email history with another person stored and unencrypted, they will have to brute force the key each time.
a) There's no reason to the NSA won't have that complete history - they're spying on you, right?
b) The NSA can't brute force your key. They don't have enough electricity to power a computer that big, or even a place to hide it (it would be bigger then the Earth).
Nope. Most people do 'email' via a website.
You don't even need to exchange the key through gmail. You can simply host the encrypted mail on Google's servers, download it, and exchange the key through a third party service.
That doesn't sound as 'simple' as via email attachments. The point is to make it a complete no-brainer for people to use. Any extra step is one step too many.
Nobody can brute force 128-bit encryption.
That's never going to be even moderately secure. If you type the cleartext into a browser window with Javascript or read the cleartext in a browser window with Javascript, then any encryption is moot.
Packet sniffers would soon reveal any nefarious business, and there's plenty of people who'd run a sniffer just to be able to prove something was going on.
The real problem right now is proving anything - anybody in a position to provide hard proof is being gagged. An encrypting plugin plus sniffer would enable anybody to prove it.
even if it worked, it would still leave the metadata wide open: Who, when, where.
I admit that's a tougher problem to solve.
One step at a time, though. Let's start by encrypting the contents...
Update:
According to Wikipedia a new edition was printed last year - https://en.wikipedia.org/wiki/Take_Back_Your_Government
That's quite timely...
Make it really easy to encrypt/base-64 encode your emails before they're uploaded to Gmail/Hotmail/Yahooo/Facebook/etc.
"Transparent to the user" would be ideal. I don't know if a browser plugin could manage that but I don't see why not - just intercept the "send" process.
Encryption keys could be generated automatically during the first few exchanges with another person by attaching information to the end of the email. After two or three replies the displayed email address turns green and you're good to go.
Yes, they could do mass man-in-the-middle attacks during the key exchange but so long as two people can verify their keys by phone (or whatever) then we'll know about it. More importantly, we'll be able to prove they're doing it. That would lead to more news stories about what the NSA does and more public awareness of the importance of installing an encryption plugin.
If no compelling medical issue requires sequencing in a newborn, it is invasive and coercive to conduct it.
Why? They might have some genetic problem which will appear later in life.
The real problem isn't the medical implications, it's the fact that we know the government is going to want a copy of the data (for the baby's own protection, of course...)
Neither will make a difference so long as people use Gmail/Hotmail/Yahooo/Facebook/etc.
If your communications go through a large US corporation then no amount of quantum-encrypted cables (or whatever) will help.
See Robert Heinlein's book "Take Back Your Government" for details.
Unfortunately, it needs people like you to get up from their sofas and actually do something instead of just grumbling about it.
There is not going to be privacy as long as the physical links are not in the hands of the people. You are not the king of your castle if you rent. People need to start digging ditches and burying fiber to connect to their neighbors.
...or just encrypt all the data that passes along the existing cables.
And if its like most clocks, its useless for me, since it automatically sets DST.
How irresponsible of anybody to manufacture something that doesn't work in 0.00001% of the world.
Pretty much every auto-setting clock I've owned has gone in the trash
Fool you twice...?
We have enough studies telling you not to do this particular thing where you feel like complete and utter crap if you do.
Unless you're Michelangelo. Or DaVinci, or Edison...or Napoleon. All people who clearly weren't operating at their best.
(Or Madonna, Jay Leno, Margaret Thatcher...all complete losers by any measure)
Back in the 80's, I constantly heard "You'll sleep enough when you're dead." or "Sleep is for wimps."
It was a trap! They wanted you at your worst.
The problem is that the biggest risk factor is not genetic - it is Islam.
And Christianity...and every other organized religion.
Don't Christians in the USA go around telling each other the president is infallible and that they should respect the police?
If you can control the major religions, you're halfway to dictatorship.
To claim "people don't want to work" I say is an appeal to emotion argument that nobody should fall for (yet sadly many do). People do want to work assuming that they get paid fairly for the work being done.
Try getting the playstaion generation to go outdoors and move plant pots around all day. You'll soon be browsing robot catalogs...
It also means that if one cell fails, the car isn't crippled in a major way. You need lots of little cells to fail for the car to be disabled, instead of just one big cell failing.
I'm fairly sure I used the words 'few dozen'.
If you have a few dozen big cells you can tell which one failed and replace it. Back to full range again.
Little ones failing inside sealed boxes is harder (more expensive) to route around and harder to fix. It's the battery equivalent of the death of a thousand cuts.
They using the same alphabet I'm using?
Let's see:
" J (elly Bean) followed I (ce Cream Sandwich) which followed H (oneycomb)".
Yes, I think they are. Why do you ask?