summaryrefslogtreecommitdiffstats
path: root/lib/libskey/shlib_version (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Add skeychallenge2() which is like skeychallenge() but takes anmillert2004-08-051-1/+1
| | | | | | already open fd. Will be used to make separate challenge/response invocations of login_skey keep the record locked. Also properly escape minus signs in man page. OK henning@ jmc@
* errno changes, lib major version bumps, and general flag daymarc2004-07-131-1/+1
| | | | | | | To build you must: cd /usr/src && make obj && make includes cd lib/libc && make depend && make && NOMAN=1 sudo make install cd /usr/src && make build
* Crank all library major numbers. Needed due to the fact that wemillert2002-12-031-1/+1
| | | | | | | | now build libraries with propolice enabled. Without this, existing binaries (such as ports/packages) that link with any system library other than libc will fail with an undefined symbol of "___guard" (__guard on ELF). Pointed out by markus@ and discussed with deraadt@
* Change S/Key stuff from using a flat file (/etc/skeykeys) to a directorymillert2002-05-161-1/+1
| | | | | | | | | where each user gets their own file, which is owned by that user. An old S/Key database may be converted by running "skeyinit -C" as root. Programs that need to access the S/Key database no longer need to be setuid root. They must now be setgid auth instead.
* major number bumpmillert2001-06-201-1/+1
|
* This case of version number update is a little special and was not well-knownniklas1997-07-291-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | before. A new general rule has been formed: When you change a library to *use* a new API of another library (which may there only have given need to a minor number crank), you must crank the *major*. The specific scenario that was seen this time was: I libc 16 started without the SHA interface II libskey 0 did obviously not use it III installation of libc 16 and libskey 0 IV software installed that uses libskey V libc 16 got SHA added, minor number update VI libskey 0 was changed to use it VII libc was cranked to 17 for other reasons VIII installation of libc 17 and newer libskey 0 IX use of the software installed in IV fails! This is due to the fact that the libskey using software searches for the most current libskey 0, which uses the SHA interface, and the most current libc 16 which was the old one installed in III, which does not provide SHA, and thus gets two incompatible libraries linked with it. Crash! One could argue that people should install all library versions that is made available, but that is really not feasible. One have to recognize that people may build their systems at arbitrary points in time and then go on to install software they know work at their lib revision levels. A later build should not break this software, that may only be available in binary versions.
* bump minormillert1997-07-271-1/+1
|
* _PATH_SKEYKEYS now lives in <paths.h>millert1997-07-231-1/+1
| | | | Add skeygetnext() for iterating over the key file.
* Mode 0600 /etc/skeykeysmillert1997-07-231-1/+1
|
* Add RIPEMD-160 (rmd160) support to OTP (s/key).millert1997-07-171-1/+1
|
* Use new SHA1* functions.millert1997-07-101-1/+1
|
* Towards RFC 1938 compliance. Also, now supports SHA (secure hash algorithm).millert1996-09-291-1/+1
|
* Deal with both MD4 and MD5 s/key'smillert1996-09-271-1/+1
|
* initial import of NetBSD treederaadt1995-10-181-0/+2
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.