<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test2/lib/libcrypt/crypt-md5.c, branch release/4.2.0_cvs</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F4.2.0_cvs</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F4.2.0_cvs'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/'/>
<updated>2000-11-20T04:41:45Z</updated>
<entry>
<title>This commit was manufactured by cvs2svn to create tag</title>
<updated>2000-11-20T04:41:45Z</updated>
<author>
<name>cvs2svn</name>
<email>cvs2svn@FreeBSD.org</email>
</author>
<published>2000-11-20T04:41:45Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=0d497cf6e989f7498cf5036a29fe7003a89abf83'/>
<id>urn:sha1:0d497cf6e989f7498cf5036a29fe7003a89abf83</id>
<content type='text'>
'RELENG_4_2_0_RELEASE'.

This commit was manufactured to restore the state of the 4.2-RELEASE image.
Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.
</content>
</entry>
<entry>
<title>Make a dlopen failure consistant with dlsym().  "Shouldn't happen."</title>
<updated>1999-12-17T20:21:45Z</updated>
<author>
<name>Peter Wemm</name>
<email>peter@FreeBSD.org</email>
</author>
<published>1999-12-17T20:21:45Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=e67c7c99ef624c47f638a8ea00ec0c881ebe7327'/>
<id>urn:sha1:e67c7c99ef624c47f638a8ea00ec0c881ebe7327</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove -lmd.  Use dlopen() and dlsym() instead for calls to the MD5* and</title>
<updated>1999-12-17T20:04:01Z</updated>
<author>
<name>Peter Wemm</name>
<email>peter@FreeBSD.org</email>
</author>
<published>1999-12-17T20:04:01Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=1f4aad4d1c613bd7ecdddf758e7beeda53b1b57a'/>
<id>urn:sha1:1f4aad4d1c613bd7ecdddf758e7beeda53b1b57a</id>
<content type='text'>
SHA* routines so that callers of libcrypt are not exposed to the internal
implementation.
</content>
</entry>
<entry>
<title>Big code cleanup. (Inspired by Brandon Gillespie). Also move as</title>
<updated>1999-09-20T12:45:49Z</updated>
<author>
<name>Mark Murray</name>
<email>markm@FreeBSD.org</email>
</author>
<published>1999-09-20T12:45:49Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=e9a56ad5ca9a9ce91608f6a0b6e1c0f9c71598db'/>
<id>urn:sha1:e9a56ad5ca9a9ce91608f6a0b6e1c0f9c71598db</id>
<content type='text'>
much as possible away from secure/ to make extending easier.
</content>
</entry>
<entry>
<title>The new crypt code broke "make world". Back it out.</title>
<updated>1999-01-23T08:27:46Z</updated>
<author>
<name>Mark Murray</name>
<email>markm@FreeBSD.org</email>
</author>
<published>1999-01-23T08:27:46Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=4fdd3d5417cca703ca0339d0aee33cc17e0ded9d'/>
<id>urn:sha1:4fdd3d5417cca703ca0339d0aee33cc17e0ded9d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rewrite of crypt library to be more modular, and addition of the</title>
<updated>1999-01-21T13:50:09Z</updated>
<author>
<name>Brandon Gillespie</name>
<email>brandon@FreeBSD.org</email>
</author>
<published>1999-01-21T13:50:09Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=da5c7089a3df3e8c3ca125316cb03ec7f26b82c8'/>
<id>urn:sha1:da5c7089a3df3e8c3ca125316cb03ec7f26b82c8</id>
<content type='text'>
Secure Hashing Algorithm - 1 (SHA-1), along with the further
refinement of what $x$salt$hash means.  With this new crypt the
following are all acceptable:

    $1$
    $MD5$
    $SHA1$

Note: $2$ is used by OpenBSD's Blowfish, which I considered adding
as $BF$, but there is no actual need for it with SHA-1.  However,
somebody wishing to add OpenBSD password support could easilly add
it in now.

There is also a malloc_crypt() available in the library now, which
behaves exactly the same as crypt(), but it uses a malloced buffer
instead of a static buffer.  However, this is not standard so will
likely not be used much (at all).

Also, for those interested I did a brief speed test Pentium 166/MMX,
which shows the DES crypt to do approximately 2640 crypts a CPU second,
MD5 to do about 62 crypts a CPU second and SHA1 to do about 18 crypts
a CPU second.

Reviewed by:	Mark Murray
</content>
</entry>
</feed>
