[19277] in cryptography@c2.net mail archive
Re: crypto for the average programmer
daemon@ATHENA.MIT.EDU (Ben Laurie)
Fri Dec 16 10:37:50 2005
X-Original-To: cryptography@metzdowd.com
X-Original-To: cryptography@metzdowd.com
Date: Thu, 15 Dec 2005 17:50:25 +0000
From: Ben Laurie <ben@algroup.co.uk>
To: leichter_jerrold@emc.com
Cc: demonfighter@gmail.com, cryptography@metzdowd.com
In-Reply-To: <Pine.SOL.4.61.0512121249490.965@mental>
leichter_jerrold@emc.com wrote:
> On Mon, 12 Dec 2005, Steve Furlong wrote:
> | > My question is, what is the layperson supposed to do, if they must use
> | > crypto and can't use an off-the-shelf product?
> |
> | When would that be the case?
> |
> | The only defensible situations I can think of in which a
> | non-crypto-specialist programmer would need to write crypto routines
> | would be an uncommon OS or hardware, or a new or rare programming
> | language which doesn't have libraries available from SourceForge etc.
> | Or maybe implementing an algorithm that's new enough it doesn't have a
> | decent free implementation, but I'm not sure such an algorithm should
> | be used in production code.
> I can tell you a situation that applied in one system I worked on: You
> could
> go with SSL, which gets you into GPL'ed code, not to mention the known
Eh? OpenSSL is BSD, not GPL.
---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@metzdowd.com
