[15889] in Kerberos_V5_Development
Re: API proposal: krb5_enctype_to_name
daemon@ATHENA.MIT.EDU (Jeffrey Hutzelman)
Tue Jun 8 22:07:42 2010
Date: Tue, 08 Jun 2010 22:07:38 -0400
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: ghudson@mit.edu, krbdev@mit.edu
Message-ID: <4E22A254E9AB4E1A05B8C866@lysithea.fac.cs.cmu.edu>
In-Reply-To: <201006041635.o54GZnrM029345@outgoing.mit.edu>
MIME-Version: 1.0
Content-Disposition: inline
Cc: jhutz@cmu.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
--On Friday, June 04, 2010 12:35:49 PM -0400 ghudson@MIT.EDU wrote:
> I propose to add:
>
> krb5_error_code KRB5_CALLCONV
> krb5_enctype_to_name(krb5_enctype enctype, krb5_boolean short,
> char *buffer, size_t buflen)
>
> If short is FALSE, we return the enctype's canonical name (like
> "aes128-cts-hmac-sha1-96").
Sounds good.
> If short is TRUE, we return the enctype's
> shortest alias (like "rc4-hmac" or "aes128-cts").
Why would you ever want to return something that purports to be an
identifier but is not canonical?
-- Jeff
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
