[2819] in Kerberos-V5-bugs
krb5-build/498: db2 really old
daemon@ATHENA.MIT.EDU (evanc@synapse.net)
Thu Nov 13 14:57:27 1997
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management)
Resent-To: tlyu@MIT.EDU
Resent-Reply-To: krb5-bugs@MIT.EDU, evanc@synapse.net
Date: 13 Nov 1997 19:47:36 -0000
From: evanc@synapse.net
To: krb5-bugs@MIT.EDU
Cc: evanc@synapse.net
>Number: 498
>Category: krb5-build
>Synopsis: update db2 release
>Confidential: no
>Severity: non-critical
>Priority: high
>Responsible: tlyu
>State: open
>Class: change-request
>Submitter-Id: unknown
>Arrival-Date: Thu Nov 13 14:57:01 EST 1997
>Last-Modified:
>Originator: Evan Champion
>Organization:
>Release: krb5-1.0.2
>Environment:
System: FreeBSD cello.synapse.net 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Tue Nov 11 00:36:42 EST 1997 evanc@cello.synapse.net:/usr/src/sys/compile/CELLO i386
>Description:
Quote from the db2 readme:
This is version 2.0-ALPHA of the Berkeley DB code.
THIS IS A PRELIMINARY RELEASE.
This does not exactly inspire confidence in something that is
supposed to be my central authentication service.
>How-To-Repeat:
>Fix:
Please upgrade to the latest db2 distribution. Currently, it is
2.3.12, available from:
<http://www.sleepycat.com/packages/db-2.3.12.tar.gz>
Even better, I'd prefer it if you just removed the db2 distribution
from krb5, and require the user to provide it (ie: just link against
-ldb). Since you don't release fixes very often, I think that is
the best way to handle the problem.
>Audit-Trail:
>Unformatted:
