From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sat, 1 Mar 2014 17:50:32 +0100 (CET) Date: Sat, 1 Mar 2014 17:50:25 +0100 From: Heinz Diehl Message-ID: <20140301165025.GA1719@fancy-poultry.org> References: <530F4E30.6000204@gmail.com> <530F7644.4040003@archlinux.org> <5310731F.2080701@gmail.com> <20140228214601.GA23681@tansi.org> <517e087c5ca5b9ddb2669a60df76dd51.squirrel@ssl.verfeiert.org> <20140228232742.GA24931@tansi.org> <53119BBB.4060006@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53119BBB.4060006@gmail.com> Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.4 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 01.03.2014, Milan Broz wrote: > (I would say - this is a good lesson to think why there are safe defaults > and why you should not change encryption parameters without good reason :-) It's not always the facts which leads to action, but the peoples assumptions and beliefs. After all, there's a general disbelief in all things the NSA put their fingers on. That said, it is not hard for me to understand what people moves to use whirlpool over SHAx..