[30764] in Kerberos
FIPS certification
daemon@ATHENA.MIT.EDU (Randy Turner)
Sat Feb 28 00:31:00 2009
Message-Id: <4B9CCCB7-39A7-4783-8C2F-64DFCE1E36E0@amalfisystems.com>
From: Randy Turner <rturner@amalfisystems.com>
To: Kerberos@mit.edu
In-Reply-To: <alpine.BSF.1.10.0901302258240.14730@brillig.security.berkeley.edu>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 27 Feb 2009 21:29:15 -0800
Content-Type: multipart/mixed; boundary="===============0173088524=="
Errors-To: kerberos-bounces@mit.edu
--===============0173088524==
Content-Type: multipart/signed; boundary=Apple-Mail-1--206281912; micalg=sha1;
protocol="application/pkcs7-signature"
--Apple-Mail-1--206281912
Content-Type: text/plain;
charset=US-ASCII;
format=flowed;
delsp=yes
Content-Transfer-Encoding: 7bit
Hello List,
I am working on a project that combines a number of different open-
source libraries, all of which utilize some form of the same
cryptographic operations, most notably symmetric ciphers, hashes, and
public key cryptography. The core of this project uses a FIPS-
certified OpenSSL codebase.
The problem with combining open-source projects is that they seem to
all come with their own implementation of crypto algorithms.
I haven't completely analyzed MIT Kerberos, but I was wondering if it
would be possible to get the MIT Kerberos subsystem to use the OpenSSL
crypto API for any cryptographic support needed for Kerberos?
I'm assuming that MIT Kerberos has not been FIPS certified.
Thanks!
Randy
--Apple-Mail-1--206281912--
--===============0173088524==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
--===============0173088524==--
