From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <htd@fancy-poultry.org>
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.13])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Sun,  9 Mar 2014 18:48:24 +0100 (CET)
Date: Sun, 9 Mar 2014 18:42:47 +0100
From: Heinz Diehl <htd@fancy-poultry.org>
Message-ID: <20140309174247.GA1752@fancy-poultry.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [dm-crypt] SHAx and LUKS/cryptsetup
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

Hi,

while experimenting with LUKS/dmcrypt, I prepared a partition
using "-h ripemd160 -c aes-xts-plain64". LuksDump shows:

Version:       	    1
Cipher name:   	    aes
Cipher mode:   	    xts-plain64
Hash spec:     	    ripemd160

However, lsmod shows that both sha1_generic and sha1_ssse3 modules are
loaded. So I did a reboot without touching the encrypted device, and
there was no SHAx module loaded. After accessing the encrypted drive
it was, hence this is clearly the cause that these modules get loaded.

My question: why are there any SHA1 modules loaded when then encrypted
drive is NOT using it?