[39] in pc-kerberos
[Fwd: Kerberos library naming conventions?]
daemon@ATHENA.MIT.EDU (Chris Shabsin)
Mon Aug 1 14:22:15 1994
To: pc-kerberos@MIT.EDU
Date: Mon, 01 Aug 1994 14:15:50 EDT
From: Chris Shabsin <shabby@MIT.EDU>
------- Forwarded Message
Received: from ATHENA-AS-WELL.MIT.EDU by po5.MIT.EDU (5.61/4.7) id AA17339;
Mon, 1 Aug 94 08:11:12 EDT
Received: from W20-575-98.MIT.EDU by MIT.EDU with SMTP
id AA06412; Mon, 1 Aug 94 08:11:11 EDT
From: pshuang@MIT.EDU
Received: by w20-575-98.MIT.EDU (AIX 3.2/UCB 5.64/4.7) id AA19067; Mon, 1 Aug
1994 08:11:10 -0400
Date: Mon, 1 Aug 1994 08:11:10 -0400
Message-Id: <9408011211.AA19067@w20-575-98.MIT.EDU>
To: shabby@MIT.EDU
In-Reply-To: Chris Shabsin's message of Sat, 30 Jul 1994 15:58:52 EDT
<9407301959.AA12897@terak-nor.MIT.EDU>
Subject: Kerberos library naming conventions?
Doesn't seem unreasonable. I might suggest that DESLIB.* and DESOS2.*
be renamed to KDESLIB.* and KDESOS2.* ("K" prefix for Kerberos) if
they are not general-purpose DES implementations. If they are
general-purpose, then the current names should stand.
Thought should also be given to naming for Kerberos 4 vs. 5, now that
I think about it. Perhaps use the following?
k4deslib.lib
k4desos2.lib
krb4lib.lib
krb4dll.lib
krb4dll.dll
krb4os2.lib
krb4os2.dll
== Ping Huang
------- End of Forwarded Message