[144776] in cryptography@c2.net mail archive
Re: SHA-1 and Git (was Re: [tahoe-dev] Tahoe-LAFS key management,
daemon@ATHENA.MIT.EDU (James A. Donald)
Tue Aug 25 17:10:14 2009
Date: Wed, 26 Aug 2009 06:41:12 +1000
From: "James A. Donald" <jamesd@echeque.com>
Reply-To: jamesd@echeque.com
To: Ben Laurie <ben@links.org>
CC: "Perry E. Metzger" <perry@piermont.com>,
Cryptography List <cryptography@metzdowd.com>
In-Reply-To: <4A93CEB9.4010206@links.org>
> Perry E. Metzger wrote:
>> Yet another reason why you always should make the crypto algorithms you
>> use pluggable in any system -- you *will* have to replace them some day.
Ben Laurie wrote:
> In order to roll out a new crypto algorithm, you have to roll out new
> software. So, why is anything needed for "pluggability" beyond versioning?
New software has to work with new and old data files and communicate
with new and old software.
Thus full protocol negotiation has to be built in to everything from the
beginning - which was the insight behind COM and the cure to DLL hell.
---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@metzdowd.com
