[32574] in Kerberos
Re: Info regarding MIT 1.8 Crypto modularity feature.
daemon@ATHENA.MIT.EDU (Use Nas)
Mon Aug 16 05:49:26 2010
MIME-Version: 1.0
In-Reply-To: <AAADBCBF-B4F3-4283-B588-5AF01E26489D@mit.edu>
Date: Mon, 16 Aug 2010 15:19:13 +0530
Message-ID: <AANLkTikYELWO82nP+D1R8zEL-hnxzBywC0-GWuBYo5=Q@mail.gmail.com>
From: Use Nas <usenas@gmail.com>
To: Zhanna Tsitkova <tsitkova@mit.edu>
Cc: "krbdev@mit.edu" <krbdev@mit.edu>, "kerberos@mit.edu" <kerberos@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
Thanks Zhanna for the information.
Please help me clarify a few things.
- Is it possible to Kerberos to use openssl encryption interfaces and go
away with builtin encryption mechanism ?
- From a user's perspective, how will he configure MIT kerberos to use
openssl interfaces ?
- In general, in future, when MIT starts supporting multiple encryption
implementation, how can a user configure the client/server to use specific
type of implementation?
Please correct me if i am wrong in my understanding.
Thanks
On Fri, Aug 13, 2010 at 6:04 PM, Zhanna Tsitkova <tsitkova@mit.edu> wrote:
> http://k5wiki.kerberos.org/wiki/Projects/Crypto_modularity
>
> Also, NSS crypto backend is expected to be added in 1.9 release timeframe.
>
> Zhanna
>
>>
>>
> Zhanna Tsitkova
> tsitkova@mit.edu
>
>
>
>
>
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
