src/lib/libcrypt/crypt-sha256.c, branch release/13.1.0 FreeBSD source tree libcrypt: There is no need to clear message digest context after they 2018-07-20T07:16:28+00:00 Xin LI delphij@FreeBSD.org 2018-07-20T07:16:28+00:00 c721d4192ee8ba9c1ac1646e414f9e495642b38e are finialized after r336539, so do not do it. Submitted by: David CARLIER <devnexen gmail com> MFC after: 1 month (after r336539) Differential Revision: https://reviews.freebsd.org/D16059 
are finialized after r336539, so do not do it.

Submitted by:	David CARLIER <devnexen gmail com>
MFC after:	1 month (after r336539)
Differential Revision:	https://reviews.freebsd.org/D16059
Get rid of unused variables. 2018-07-20T07:07:27+00:00 Xin LI delphij@FreeBSD.org 2018-07-20T07:07:27+00:00 a7e92a77da0fb320e096973088dcf616961bddb8 copied_key and copied_salt are assigned with NULL and never used otherwise. Remove the two variables and related code. Reviewed by: pfg MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D16314 
copied_key and copied_salt are assigned with NULL and never used
otherwise. Remove the two variables and related code.

Reviewed by:	pfg
MFC after:	2 weeks
Differential Revision:	https://reviews.freebsd.org/D16314
lib: further adoption of SPDX licensing ID tags. 2017-11-26T02:00:33+00:00 Pedro F. Giffuni pfg@FreeBSD.org 2017-11-26T02:00:33+00:00 5e53a4f90f82c4345f277dd87cc9292f26e04a29 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. 
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.
Make libcrypt thread-safe. Add crypt_r(3). 2016-08-10T15:16:28+00:00 Ed Schouten ed@FreeBSD.org 2016-08-10T15:16:28+00:00 5f521d7ba72145092ea23ff6081d8791ad6c1f9d 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 
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
s/shaN_crypt/crypt_shaN/g to be a more consistent with the existing naming. 2011-05-05T01:09:42+00:00 David E. O'Brien obrien@FreeBSD.org 2011-05-05T01:09:42+00:00 ad45dd41748d63079ca410ef09cd2eb9a924fd89 Reviewed by: markm 
Reviewed by:	markm
Add SHA256/512 ($5$ and $6$) to crypt(3). Used in linux-world, doesn't 2011-04-09T14:02:04+00:00 Mark Murray markm@FreeBSD.org 2011-04-09T14:02:04+00:00 3d6f63c0467cf7f15000cf5ca347cabd5f51afa7 hurt us. PR: misc/124164 Submitted by: KIMURA Yasuhiro < yasu utahime org > MFC after: 1 month 
hurt us.

PR:		misc/124164
Submitted by:	KIMURA Yasuhiro < yasu utahime org >
MFC after:	1 month