lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 13 Nov 2007 16:38:39 -0500
From: Valdis.Kletnieks@...edu
To: johan beisser <jb@...stic.org>
Cc: Paul Wouters <paul@...net.nl>,
	Florian Echtler <echtler@...tum.de>,
	"Matt D. Harris" <mdh@...itox.net>,
	Paul Sebastian Ziegler <psz@...erved.de>, bugtraq@...urityfocus.com
Subject: Re: Standing Up Against German Laws - Project HayNeedle

On Tue, 13 Nov 2007 13:07:02 PST, johan beisser said:
> Actually, that's not really part of the issue. The logs don't contain  
> context, just who/where/when. While encryption will prevent (one  
> hopes) the capability of recovering context, who you talked to is not  
> kept private or otherwise secret.

It's probably a good idea to deploy encryption *now*, and use it for
*everything*, and be ready for when (not if) they decide to be more draconian
in their logging requirements.  And yes, encrypt *everything* - that way you
make it a lot harder to do traffic analysis.  If only the "interesting" 10% is
encrypted, they know which 10% are interesting connections, which may be as
important as the actual content.



Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ