Subject: Re: CVS commit: cryptosrc-us
To: Simon Burge <email@example.com>
From: Aidan Cully <firstname.lastname@example.org>
Date: 07/30/1999 11:53:56
On Fri, Jul 30, 1999 at 02:30:47PM, Simon Burge said:
> Aidan Cully wrote:
> > Module Name: cryptosrc-us
> > Committed By: aidan
> > Date: Fri Jul 30 01:52:45 UTC 1999
> > Update of /cvsroot/cryptosrc-us/crypto-us/dist/krb5
> > In directory nb00:/tmp/cvs-serv4730
> > Log Message:
> > Initial import of MIT kerberos5 sources.
> > Status:
> > Vendor Tag: MIT
> > Release Tags: v1_0_6
> > [[ some files deleted ]]
> > N cryptosrc-us/crypto-us/dist/krb5/src/util/db2/Makefile.in
> > N cryptosrc-us/crypto-us/dist/krb5/src/util/db2/CHANGELOG
> > N cryptosrc-us/crypto-us/dist/krb5/src/util/db2/ChangeLog
> > N cryptosrc-us/crypto-us/dist/krb5/src/util/db2/Makefile.inc
> > N cryptosrc-us/crypto-us/dist/krb5/src/util/db2/README
> > [[ .. more deleted ]]
> Is this berkeley DB2 (I can't look :-). If so, do we have licensing
> issues to worry about?
From the README file in that directory:
This is version 2.0-ALPHA of the Berkeley DB code.
THIS IS A PRELIMINARY RELEASE.
I _think_ the DB2 we're worried about is the one from sleepycat? This
is definately not that DB2, and all the source files I've looked at
have the standard BSD license. So I don't believe there's an issue.