I always used https://mail.google.com/ and also set it as the start page for my mother, father & girlfriend... Just wondering: as it was always there, why Google announced it recently?!?!
Oh, by the way, more SSL caveats here: The Pirate Bay SSL proven little effective. Please comment!
You may not store individual encrypted files, as SOMETIMES the file length could be used to guess it's content!!! You should always encrypt & pack as many files as you can in a single archive to avoid this. However, this way you'll be unable to do incremental backups:(
BTW, check out the "file length match trick" applied to the new ThePirateBay SSL system: http://slashdot.org/firehose.pl?op=view&id=803927
Slashdot Mirror
I always used https://mail.google.com/ and also set it as the start page for my mother, father & girlfriend... Just wondering: as it was always there, why Google announced it recently?!?! Oh, by the way, more SSL caveats here: The Pirate Bay SSL proven little effective. Please comment!
You may not store individual encrypted files, as SOMETIMES the file length could be used to guess it's content!!! You should always encrypt & pack as many files as you can in a single archive to avoid this. However, this way you'll be unable to do incremental backups :(
BTW, check out the "file length match trick" applied to the new ThePirateBay SSL system:
http://slashdot.org/firehose.pl?op=view&id=803927
SSL is still vulnerable to the known size attack: http://slashdot.org/firehose.pl?op=view&id=803927
Hey, remember that?! ;)
Compressed VoIP Calls Vulnerable To Bugging
Exactly the same principle could be applied on HTTPS connections, also:
The Pirate Bay SSL proven ineffective
Think VPN if you want a bit of privacy
Another one about the old bugs floating out of the void... Please vote :)
http://slashdot.org/firehose.pl?op=view&id=803927
The Pirate Bay SSL proven ineffective: http://slashdot.org/firehose.pl?op=view&id=803927