<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/lib/libcrypt/crypt.h, branch releng/14.4</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=releng%2F14.4</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=releng%2F14.4'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2023-08-16T17:54:16Z</updated>
<entry>
<title>Remove $FreeBSD$: two-line .h pattern</title>
<updated>2023-08-16T17:54:16Z</updated>
<author>
<name>Warner Losh</name>
<email>imp@FreeBSD.org</email>
</author>
<published>2023-08-16T17:54:16Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=b3e7694832e81d7a904a10f525f8797b753bf0d3'/>
<id>urn:sha1:b3e7694832e81d7a904a10f525f8797b753bf0d3</id>
<content type='text'>
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
</content>
</entry>
<entry>
<title>spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD</title>
<updated>2023-05-12T16:44:03Z</updated>
<author>
<name>Warner Losh</name>
<email>imp@FreeBSD.org</email>
</author>
<published>2023-05-10T15:40:58Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=4d846d260e2b9a3d4d0a701462568268cbfe7a5b'/>
<id>urn:sha1:4d846d260e2b9a3d4d0a701462568268cbfe7a5b</id>
<content type='text'>
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.

Discussed with:		pfg
MFC After:		3 days
Sponsored by:		Netflix
</content>
</entry>
<entry>
<title>lib: further adoption of SPDX licensing ID tags.</title>
<updated>2017-11-26T02:00:33Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2017-11-26T02:00:33Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=5e53a4f90f82c4345f277dd87cc9292f26e04a29'/>
<id>urn:sha1:5e53a4f90f82c4345f277dd87cc9292f26e04a29</id>
<content type='text'>
Mainly focus on files that use BSD 2-Clause license, however the tool I
was using mis-identified many licenses so this was mostly a manual - error
prone - task.

The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.
</content>
</entry>
<entry>
<title>Make libcrypt thread-safe. Add crypt_r(3).</title>
<updated>2016-08-10T15:16:28Z</updated>
<author>
<name>Ed Schouten</name>
<email>ed@FreeBSD.org</email>
</author>
<published>2016-08-10T15:16:28Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=5f521d7ba72145092ea23ff6081d8791ad6c1f9d'/>
<id>urn:sha1:5f521d7ba72145092ea23ff6081d8791ad6c1f9d</id>
<content type='text'>
glibc has a pretty nice function called crypt_r(3), which is nothing
more than crypt(3), but thread-safe. It accomplishes this by introducing
a 'struct crypt_data' structure that contains a buffer that is large
enough to hold the resulting string.

Let's go ahead and also add this function. It would be a shame if a
useful function like this wouldn't be usable in multithreaded apps.
Refactor crypt.c and all of the backends to no longer declare static
arrays, but write their output in a provided buffer.

There is no need to do any buffer length computation here, as we'll just
need to ensure that 'struct crypt_data' is large enough, which it is.
_PASSWORD_LEN is defined to 128 bytes, but in this case I'm picking 256,
as this is going to be part of the actual ABI.

Differential Revision:	https://reviews.freebsd.org/D7306
</content>
</entry>
<entry>
<title>s/shaN_crypt/crypt_shaN/g to be a more consistent with the existing naming.</title>
<updated>2011-05-05T01:09:42Z</updated>
<author>
<name>David E. O'Brien</name>
<email>obrien@FreeBSD.org</email>
</author>
<published>2011-05-05T01:09:42Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=ad45dd41748d63079ca410ef09cd2eb9a924fd89'/>
<id>urn:sha1:ad45dd41748d63079ca410ef09cd2eb9a924fd89</id>
<content type='text'>
Reviewed by:	markm
</content>
</entry>
<entry>
<title>Add SHA256/512 ($5$ and $6$) to crypt(3). Used in linux-world, doesn't</title>
<updated>2011-04-09T14:02:04Z</updated>
<author>
<name>Mark Murray</name>
<email>markm@FreeBSD.org</email>
</author>
<published>2011-04-09T14:02:04Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=3d6f63c0467cf7f15000cf5ca347cabd5f51afa7'/>
<id>urn:sha1:3d6f63c0467cf7f15000cf5ca347cabd5f51afa7</id>
<content type='text'>
hurt us.

PR:		misc/124164
Submitted by:	KIMURA Yasuhiro &lt; yasu utahime org &gt;
MFC after:	1 month
</content>
</entry>
<entry>
<title>Add a new hash type. This "NT-hash" is compatible with the password</title>
<updated>2003-06-02T19:29:27Z</updated>
<author>
<name>Mark Murray</name>
<email>markm@FreeBSD.org</email>
</author>
<published>2003-06-02T19:29:27Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=bf513f6958487aaec98db331959674dd4db398d5'/>
<id>urn:sha1:bf513f6958487aaec98db331959674dd4db398d5</id>
<content type='text'>
hashing scheme used in Microsoft's NT machines. IT IS NOT SECURE!
DON'T USE IT! This is for the use of competent sysadmins only!

Submitted by:	Michael Bretterklieber
</content>
</entry>
<entry>
<title>No functional change, but big code cleanup. WARNS, lint(1) and style(9).</title>
<updated>2002-03-06T17:18:09Z</updated>
<author>
<name>Mark Murray</name>
<email>markm@FreeBSD.org</email>
</author>
<published>2002-03-06T17:18:09Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=f2ac424af7b980ba4d858ecfd1644ce197d6869d'/>
<id>urn:sha1:f2ac424af7b980ba4d858ecfd1644ce197d6869d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add OpenBSD-style blowfish password hashing. This makes one less</title>
<updated>2001-03-11T16:05:43Z</updated>
<author>
<name>Mark Murray</name>
<email>markm@FreeBSD.org</email>
</author>
<published>2001-03-11T16:05:43Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=5c1296168babf97c51ff030872cddb7f9857474f'/>
<id>urn:sha1:5c1296168babf97c51ff030872cddb7f9857474f</id>
<content type='text'>
gratuitous difference between us and our sister project.

This was given to me _ages_ ago. May apologies to Paul for the length
of time its taken me to commit.

Obtained from:	Niels Provos &lt;provos@physnet.uni-hamburg.de&gt;/OpenBSD
Submitted by:	Paul Herman &lt;pherman@frenchfries.net&gt;
</content>
</entry>
<entry>
<title>Add working and easy crypt(3)-switching.  Yes, we need a whole new API</title>
<updated>2000-08-22T02:15:54Z</updated>
<author>
<name>Brian Feldman</name>
<email>green@FreeBSD.org</email>
</author>
<published>2000-08-22T02:15:54Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=04c9749ff0148ec8f73b150cec8bc2c094a5d31a'/>
<id>urn:sha1:04c9749ff0148ec8f73b150cec8bc2c094a5d31a</id>
<content type='text'>
for crypt(3) by now.  In any case:

Add crypt_set_format(3) + documentation to -lcrypt.
Add login_setcryptfmt(3) + documentation to -lutil.
Support for switching crypt formats in passwd(8).
Support for switching crypt formats in pw(8).

The simple synopsis is:
edit login.conf; add a passwd_format field set to "des" or "md5"; go nuts :)

Reviewed by:	peter
</content>
</entry>
</feed>
