From: Johnathan Corgan <jcorgan@aeinet.com>
To: Andy Brown <asb@nexor.co.uk>
Message Hash: 1188edba7bd869412f5956d346f45b62039b425745b3d135288cd20519321e89
Message ID: <Pine.LNX.3.91.950727085755.104A-100000@comet.aeinet.com>
Reply To: <Pine.SOL.3.91.950727104038.17605B-100000@eagle.nexor.co.uk>
UTC Datetime: 1995-07-27 16:06:49 UTC
Raw Date: Thu, 27 Jul 95 09:06:49 PDT
From: Johnathan Corgan <jcorgan@aeinet.com>
Date: Thu, 27 Jul 95 09:06:49 PDT
To: Andy Brown <asb@nexor.co.uk>
Subject: Re: Encrypting block driver for Linux...need some advice
In-Reply-To: <Pine.SOL.3.91.950727104038.17605B-100000@eagle.nexor.co.uk>
Message-ID: <Pine.LNX.3.91.950727085755.104A-100000@comet.aeinet.com>
MIME-Version: 1.0
Content-Type: text/plain
-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 27 Jul 1995, Andy Brown wrote:
> Your scheme should be OK. If you'd chosen the same IV for each sector
> then identical sectors would encrypt the same. If I remember rightly
> then having a known IV only affects the security of the first block,
> after that the ciphertext chaining comes into effect.
I suspected as much. I don't see how a known IV affects the security of the
first block even (and perhaps I'm exposing some real crypto-ignorance here
:).
Someone pointed out in private mail that the SFS docs have a good section on
IV selection techniques...I'll go off and read those.
==
Johnathan Corgan "For the first time in history, it is possible to
jcorgan@aeinet.com have absolute privacy over arbitrary distances."
PGP Key Fingerprint: 4F 28 69 B8 76 2E 42 3E 8B 4C 12 BB 3A 43 D4 07
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQEUAwUBMBfGZelPfVlQ1n99AQFcswf470WxqWkne0OPdCeKcc8Gaei7AIeKUg//
CzrgD6ATPLrpMZcmNCMtv0cY4jo3tUnbJI50plyuda8v8Hlyc5l1ejSO0YoOBZrs
ICFhQfXp6bpPxV8ZFKozKo1N3RlcpgtArMZqoKZ4jfg3kMCTtBU2bc7Kh793sk3d
EXS2GcPpXYUiTMJ53IJyBXcl2KX1MnCUkWVeal8D9kGY4/8pfJFLWuqBpsUDCQsW
yamvhcDiltCD6ukRwQ7Vpu3dWCn0ZxjWg0emg/toqNNdKB950Bh+dlgd5z/LabTn
4eSPdqeWQW/W96cShm1y73AbGM8hJWWAuMKrFuaoyR1ilIis03eT
=sheZ
-----END PGP SIGNATURE-----
Return to July 1995
Return to “Johnathan Corgan <jcorgan@aeinet.com>”