GSP/Panel
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added Cyg-Win

Browse source
This commit is contained in:
Frank Harris 2026-06-06 18:46:40 -04:00
parent 82cbc206eb
commit 413c315806
10586 changed files with 3806249 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

38
Agent-Windows/OGP64/usr/share/doc/libxcrypt/AUTHORS Normal file
View file

@ -0,0 +1,38 @@
The yescrypt code comes from yescrypt by Solar Designer <solar at
openwall.com>. It builds upon Colin Percival's scrypt.
See: http://openwall.com/yescrypt/ for reference.
The bcrypt hash module comes from crypt_blowfish, originally written
by Solar Designer <solar at openwall.com> and based on algorithms and
ideas by Niels Provos <provos at citi.umich.edu> and David Mazieres
<dm at lcs.mit.edu>.
The MD5, SHA256, and SHA512 hash modules, and the underlying
secure-hash primitives, were originally written by Ulrich Drepper
<drepper at cygnus.com> as part of the GNU C Library. Other people
may also have contributed to them; our records are incomplete.
The DES hash module was originally FreeSec, written by David Burren
<davidb at werj.com.au> for the NetBSD project, and since extensively
modified by Geoffrey M. Rehmet, Mark R V Murray, and Zack Weinberg.
The NTHASH module comes from FreeBSD, originally written by Michael
Bretterklieber and based on the password hashing algorithm used by
the Windows NT LAN Manager (NTLM) from Microsoft Corporation to
provide easier compatibility with NT accounts.
The SUNMD5 hash module is a clean-room reimplementation by Zack Weinberg,
based on a specification written by Eli Collins for the Passlib project,
of an algorithm originally developed by Alec Muffett for use in Solaris 9.
The crypt and gensalt backends for yescrypt and gost-yescrypt are by
Vitaly Chikunov.
The implementation of the public interface (crypt, crypt_r, etc) is a
mashup of code from the GNU C Library with code from crypt_blowfish,
originally put together by Thorsten Kukuk and since completely
rewritten by Björn Esser and Zack Weinberg.
The above components were assembled into this library by Thorsten Kukuk
<kukuk at suse.de>, Björn Esser <besser82 at fedoraproject.org>, and
Zack Weinberg <zackw at panix.com>.

502
Agent-Windows/OGP64/usr/share/doc/libxcrypt/COPYING.LIB Normal file
View file

@ -0,0 +1,502 @@
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the Lesser GPL. It also counts
as the successor of the GNU Library Public License, version 2, hence
the version number 2.1.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.
When we speak of free software, we are referring to freedom of use,
not price. Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.
To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights. These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.
To protect each distributor, we want to make it very clear that
there is no warranty for the free library. Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.
Finally, software patents pose a constant threat to the existence of
any free program. We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder. Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.
Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License. This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License. We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.
When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library. The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom. The Lesser General
Public License permits more lax criteria for linking other code with
the library.
We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License. It also provides other free software developers Less
of an advantage over competing non-free programs. These disadvantages
are the reason we use the ordinary General Public License for many
libraries. However, the Lesser license provides advantages in certain
special circumstances.
For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it becomes
a de-facto standard. To achieve this, non-free programs must be
allowed to use the library. A more frequent case is that a free
library does the same job as widely used non-free libraries. In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software. For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.
Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.
GNU LESSER GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time a
copy of the library already present on the user's computer system,
rather than copying library functions into the executable, and (2)
will operate properly with a modified version of the library, if
the user installs one, as long as the modified version is
interface-compatible with the version that the work was made with.
c) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
d) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
e) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with
this License.
11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Lesser General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!

239
Agent-Windows/OGP64/usr/share/doc/libxcrypt/ChangeLog Normal file
View file

@ -0,0 +1,239 @@
2018-01-27 Zack Weinberg <zackw@panix.com>
* Version 4.0.0 released.
* This project no longer maintains a GNU-style ChangeLog file.
See the Git commit history for detailed changes since 3.1.1.
2015-05-13 Björn Esser <besser82@fedoraproject.org>
* release version 3.1.1
* README.bcrypt: whitespace clean-up
* src/crypt-private.h
* configure.ac: add '--enable-Wno-cast-align' to silence 'cast
increases required alignment'
2015-05-12 Björn Esser <besser82@fedoraproject.org>
* release version 3.1.0
* configure.ac: update upstream-contact
* configure.ac: add './configure --enable-bootstrap' to skip some
tests on initial build
* src/Makefile.am
* bootstrap.sh: add bootstrap-script
* LICENSE.bcrypt: add LICENSE for bcrypt
* Makefile.am
* plugins/blowfish/Makefile.am: update crypt_blowfish to v1.3
* plugins/blowfish/blowfish-test.c
* plugins/blowfish/crypt_blowfish.c
* plugins/blowfish/crypt_blowfish.h
* plugins/blowfish/ow-crypt.h
* configure.ac: add '-Wextra' to CFLAGS
* plugins/md5/md5.c: fix '-Werror=strict-aliasing'
* plugins/sha256/sha256.c
* plugins/sha512/sha512.c
* src/cert.c: fix '-Werror=unused-result'
* configure.in --> configure.ac: update Autotools
* Makefile.am
* m4/
* plugins/blowfish/Makefile.am
* plugins/md5/Makefile.am
* plugins/sha256/Makefile.am
* plugins/sha512/Makefile.am
* src/Makefile.am
2011-05-10 Thorsten Kukuk <kukuk@suse.de>
* release version 3.0.4
* src/cert.c (get8): Don't save return value we never use.
2009-10-29 Thorsten Kukuk <kukuk@suse.de>
* release version 3.0.3
* src/xcrypt.c (__xcrypt_gensalt_r): Fix memory leak [bnc#547893].
2008-11-04 Thorsten Kukuk <kukuk@suse.de>
* plugins/blowfish/blowfish-test.c (run): Fix compiler
warnings [bnc#440134].
2008-09-28 Thorsten Kukuk <kukuk@suse.de>
* src/xcrypt-private.h: Add prototype for _xcrypt_gensalt_sha256_rn
and _xcrypt_gensalt_sha512_rn.
* src/crypt_gensalt.c: Add new gensalt functions.
* src/xcrypt.c: Use gensalt functions for sha512 and sha256.
* src/gensalt-test.c: Enable test cases for sha256 and sha512.
2008-07-16 Thorsten Kukuk <kukuk@suse.de>
* release version 3.0.2
* src/xcrypt.c (__xcrypt_gensalt_r): Handle special
MD5 case.
* src/gensalt-test.c: New test case.
* src/Makefile.am: Add gensalt-test as new test case.
2008-06-24 Thorsten Kukuk <kukuk@suse.de>
* release version 3.0.1
* plugins/md5/md5.c: Fix undefined macros.
* plugins/sha256/sha256.c: Likewise.
* plugins/sha512/sha512.c: Likewise.
2008-02-15 Thorsten Kukuk <kukuk@suse.de>
* release version 3.0
* plugins/*: Move all crypt related code into plugins.
* plugins/sha256: New, $5$ aka sha256 hash.
* plugins/sha512: New, $6$ aka sha512 hash.
* src/sha.c: Removed.
* src/sha-crypt.c: Likewise.
* src/xcrypt.h: Add __nonnull.
* src/crypt_util.c: Sync with glibc 2.7.
* src/xcrypt.c: Load all hashes except DES dynamic.
* src/Makefile.am: increase version of shared library.
2006-01-06 Thorsten Kukuk <kukuk@suse.de>
* release version 2.4
* src/Makefile.am: Bump minor version number
* src/crypt_gensalt.c: Sync with crypt_blowfish 1.0.
2005-09-18 Thorsten Kukuk <kukuk@suse.de>
* release version 2.3
* src/x86.S: Remove.
* src/crypt_blowfish.c: Don't use ASM on x86.
2004-06-18 Thorsten Kukuk <kukuk@suse.de>
* release version 2.2
* src/md5-crypt.c (__md5_crypt): Check if realloc
runs out of memory (from glibc CVS).
* configure.in: Remove --noexecstack flag (compiler
can do it better itself).
2003-11-14 Thorsten Kukuk <kukuk@suse.de>
* configure.in: Check for --noexecstack support
2003-10-16 Thorsten Kukuk <kukuk@suse.de>
* release version 2.1
* COPYING: Add all different copyrights.
* src/x86.S: Added, optimized, thread safe version for ix86.
* src/crypt_blowfish.c: Use optimized assembler functions on ix86.
* libxcrypt.spec: New.
2003-07-28 Thorsten Kukuk <kukuk@suse.de>
* release version 2.0
* src/crypt_util.c: Include xcrypt-private.h only, add weak aliases.
* src/wrapper.c: Likewise.
* src/crypt_gensalt.c: Rename _crypt_* to _xcrypt_*
* src/crypt_blowfish.c: Likewise.
* src/crypt-entry.c: Include xcrypt-private.h.
* src/crypt.c: Only include xcrypt-private.h.
* src/xcrypt-private.h: Include xcrypt.h, undef xcrypt defines
* src/xcrypt.h: Rename prototypes from crypt* to xcrypt* and
add compat defines.
2003-01-16 Thorsten Kukuk <kukuk@suse.de>
* release version 1.4
* src/blowfish-test.c: Add test with threads.
* src/Makefile.am: Use AM_CFLAGS instead of CFLAGS,
(blowfish_test_LDFLAGS): Add libpthread,
(blowfish_test_CFLAGS): Define number of threads for test.
* src/crypt_util.c: Don't define _LIBC for libc-lock.h,
redefine __libc_lock_t with pthread_mutex_t.
* src/crypt_blowfish.c: Sync with version 0.4.5
2003-01-10 Thorsten Kukuk <kukuk@suse.de>
* release version 1.3
2002-11-04 Thorsten Kukuk <kukuk@suse.de>
* src/crypt_util.c (__init_des_r): Sync with current glibc CVS
(fix initialisation of internal data struct).
* src/md5test.c (main): Sync with current glibc CVS (add test
case for above crypt_util fix).
2002-10-21 Thorsten Kukuk <kukuk@suse.de>
* release version 1.2
* src/crypt_util.c: undef _LIBC after inclusion of libc-lock.h
* src/crypt_blowfish.c: Add support for hppa
* configure.in: bump version number to 1.2
2002-05-27 Thorsten Kukuk <kukuk@suse.de>
* release version 1.1
* src/sha.c: New file.
* src/sha-crypt.c: New file.
* src/md5-private.h: Renamed to ...
* src/xcrypt-private.h: ... to this.
* src/crypt_gensalt.c: Add dummy function for SHA1.
* src/wrapper.c: Call SHA1 functions.
2002-05-14 Thorsten Kukuk <kukuk@suse.de>
* src/xcrypt.h: Add prototpyes for SHA1 functions.
* src/wrapper.c: Don't include md5.h.
* src/md5-crypt.c: Include xcrypt.h instead of md5.h.
* src/md5test.c: Likewise.
* src/md5.c: Likewise.
* src/xcrypt.h: Add prototypes from md5.h.
* src/md5.h: Removed.
2002-04-13 Thorsten Kukuk <kukuk@suse.de>
* release version 1.0

630
Agent-Windows/OGP64/usr/share/doc/libxcrypt/NEWS Normal file
View file

@ -0,0 +1,630 @@
libxcrypt NEWS -- history of user-visible changes.
Please send bug reports, questions and suggestions to
<https://github.com/besser82/libxcrypt/issues>.
Version 4.5.2
* Use a more portable implementation for our fallback implementation
of explicit_bzero(); also get rid of the need for VLA in the new
implementation (issue #212).
* Fix compilation of alg-sha1 with optimization level 3 for GCC v11
and newer (issue #179).
Version 4.5.1
* Do not include undefined symbols in version-script (issue #181, #213).
* Fix build with clang-20+ on macOS (issue #216).
Version 4.5.0
* Implement the sm3crypt ($sm3$) hashing algorithm (issue #188).
* Implement the sm3-yescrypt ($sm3y$) hashing algorithm (issue #206).
* Fix the implementation of the crypt(3) functions and the crypt_gensalt(3)
functions to not overwrite the output buffer too early. (issue #209).
* Fix the strcpy_or_abort() function to call abort() in -DNDEBUG builds.
* Add some more testcases.
* Several fixes for issues found by Coverity.
Version 4.4.38
* Fix several "-Wunterminated-string-initialization", which are seen by
upcoming GCC 15.x (issue #194).
* Fix "-Wmaybe-uninitialized" in crypt.c, which is seen by GCC 13.3.0.
* Skip test/explicit-bzero if compiling with ASAN.
* Drop hard requirement for the pkg-config binary (issue #198).
Version 4.4.37
* Several fixes to the manpages (issue #185).
* Add binary compatibility for x86_64 GNU/Hurd (issue #189).
* Only test the needed makecontext signature during configure (issue #178).
* Fix -Werror=strict-overflow in lib/crypt-bcrypt.c, which is seen
by GCC 4.8.5 (issue #197).
Version 4.4.36
* Fix left over bits failing with Perl v5.38.0 (issue #173).
Version 4.4.35
* Fix build with Perl v5.38.0 (issue #170).
* Fix build with MinGW-w(32|64).
Version 4.4.34
* Update build-aux/m4/ax_valgrind_check.m4 to v23.
* Optimize some cast operation for performance in
lib/alg-yescrypt-platform.c.
* Add SHA-2 Maj() optimization proposed by Wei Dai in lib/alg-sha512.c.
* Explicitly clean the stack and context state after computation in
lib/alg-gost3411-2012-hmac.c, lib/alg-hmac-sha1.c, and lib/alg-sha256.c
(issue #168).
Version 4.4.33
* Fix -Werror=sign-conversion in lib/alg-yescrypt-platform.c.
With commit 894aee75433b4dc8d9724b126da6e79fa5f6814b we introduced some
changes to huge page handling, that show this error when building with
GCC v12.2.1, and thus need a small fix.
Version 4.4.32
* Improvements to huge page handling in lib/alg-yescrypt-platform.c.
When explicitly using huge pages, request the 2 MiB page size.
This should fix the issue where on a system configured to use 1 GiB
huge pages we'd fail on munmap() as we're only rounding the size up
to a multiple of 2 MiB. With the fix, we wouldn't use huge pages on
such a system. Unfortunately, now we also wouldn't use huge pages on
Linux kernels too old to have MAP_HUGE_2MB (issue #152).
Version 4.4.31
* Fix -Werror=conversion in lib/alg-yescrypt-opt.c
(issues #161 and #162).
* Add some SHA-2 Maj() optimization in lib/alg-sha256.c.
* Fix issues found by Covscan in test/getrandom-fallback.c.
* Fix -Werror=strict-overflow in lib/crypt-des.c, which is seen
by GCC 12.x (issues #155 and #163).
Version 4.4.30
* configure: Restore ucontext api functionality check.
In c3f01c72b303cbbb0cc8983120677edee2f3fa4b the use of the ucontext api
in the main program was removed, and with it the configure check for it.
However, the ucontext api is still used in the "explicit_bzero" test and
thus this test still needs to be in place.
See also: https://bugs.gentoo.org/838172
* configure: Restore the functionality of the '--disable-symvers' switch.
Without this fix the build was simply broken, if symbol versioning was
disabled for any reason, e.g. whether the compiler nor the linker
supporting it, or if disabled on purpose by the user (issue #142).
* Fix variable name in crypt(3) for a datamember of 'struct crypt_data'
(issue #153).
Version 4.4.29
* Add glibc-on-loongarch-lp64 (Loongson LA464 / LA664) entry to
libcrypt.minver. This was added in GNU libc 2.36.
Version 4.4.28
* Add glibc-on-or1k (OpenRISC 1000) entry to libcrypt.minver.
This was added in GNU libc 2.35.
Version 4.4.27
* Limit the maximum amount of rbytes to 64 bytes (512 bits) for
yescrypt, gost-yescrypt, and scrypt. Also reflect this limit
in the documentation (issue #145).
Version 4.4.26
* Fix compilation on systems with GCC >= 10, that do not support
declarations with __attribute__((symver)).
Version 4.4.25
* Add support for Python 3.11 in the configure script.
* Stricter checking of invalid salt characters (issue #135).
Hashed passphrases are always entirely printable ASCII, and do
not contain any whitespace or the characters ':', ';', '*', '!',
or '\'. (These characters are used as delimiters and special
markers in the passwd(5) and shadow(5) files.)
Version 4.4.24
* Add hash group for Debian in lib/hashes.conf.
Debian has switched to use the yescrypt hashing algorithm as
the default for new user passwords, so we should add a group
for this distribution.
* Overhaul the badsalt test.
Test patterns are now mostly generated rather than manually coded
into a big table. Not reading past the end of the “setting” part
of the string is tested more thoroughly (this would have caught the
sunmd5 $$ bug if it had been available at the time).
Test logs are tidier.
* Add ‘test-programs’ utility target to Makefile.
It is sometimes useful to compile all the test programs but not run
them. Add a Makefile target that does this.
* Fix incorrect bcrypt-related ifdeffage in test/badsalt.c.
The four variants of bcrypt are independently configurable, but the
badsalt tests for them were all being toggled by INCLUDE_bcrypt,
which is only the macro for the $2b$ variant.
* Fix bigcrypt-related test cases in test/badsalt.c.
The test spec was only correct when both or neither of bigcrypt and
descrypt were enabled.
* Detect ASan in configure and disable incompatible tests.
ASan’s “interceptors” for crypt and crypt_r have a semantic conflict
with libxcrypt, requiring a few tests to be disabled for builds with
-fsanitize-address. See commentary in test/crypt-badargs.c for an
explanation of the conflict, and the commentary in
build-aux/m4/zw_detect_asan.m4 for why a configure test is required.
* Fix several issues found by Covscan in the testsuite. These include:
- CWE-170: String not null terminated (STRING_NULL)
- CWE-188: Reliance on integer endianness (INCOMPATIBLE_CAST)
- CWE-190: Unintentional integer overflow (OVERFLOW_BEFORE_WIDEN)
- CWE-569: Wrong sizeof argument (SIZEOF_MISMATCH)
- CWE-573: Missing varargs init or cleanup (VARARGS)
- CWE-687: Argument cannot be negative (NEGATIVE_RETURNS)
Version 4.4.23
* Fix output calculation for gensalt_yescrypt_rn().
* Fix -Werror=conversion in lib/crypt-des-obsolete.c,
test/des-obsolete.c, and test/des-obsolete_r.c.
Version 4.4.22
* The crypt_checksalt() function has been fixed to correctly return
with 'CRYPT_SALT_INVALID', in case the setting, that is passed
to be checked, represents an empty passphrase or an uncomputed
setting for descrypt without any salt characters.
Version 4.4.21
* The crypt_checksalt() function will now return the value
'CRYPT_SALT_METHOD_LEGACY' in case the setting, that is passed
to be checked, uses a hashing method, which is considered to be
too weak for use with new passphrases.
Version 4.4.20
* Fix build when the CFLAGS variable, that is passed into the
configure script, has a leading whitespace character in it
(issue #123).
Version 4.4.19
* Improve fallback implementation of explicit_bzero.
* Add glibc-on-CSKY, ARC, and RISCV-32 entries to libcrypt.minver.
These were added in GNU libc 2.29, 2.32, and 2.33 respectively
(issue #122).
* Do not build xcrypt.h if we’re not going to install it.
* Do not apply --enable-obsolete-api-enosys mode to fcrypt.
* Compilation fix for NetBSD. NetBSD’s <unistd.h> declares encrypt
and setkey to return int, contrary to POSIX (which says they return
void). Rename those declarations out of the way with macros.
* Compilation fixes for building with GCC 11.
Basically fixes for explicit type-casting.
* Force update of existing symlinks during installation (issue #120).
Version 4.4.18
* Fix compilation errors on (Free)BSD (issue #110).
* Fix conversion error in lib/alg-gost3411-core.c, which is seen by
some sensitive compilers.
* Convert build scripts to Perl.
The minimum version of Perl required is 5.14.
Version 4.4.17
* Fix compilation error in 'alignas (type)' with older versions
of glibc and/or gcc (issue #107).
* Salt string compatibility with generic implementations (issue #105).
All other existing implementations of the md5crypt, sha256crypt,
and sha512crypt hashing methods allow any ASCII character to be
present in the salt string.
We changed our implementation of these hash methods to be compliant
with the general behaviour, except for the colon ':' character,
which serves a special purpose in the Unix shadow file, and the
newline '\n' character, since all parameters of the user data must
be on the same line within the Unix shadow file.
* Fix for GCC 10.2 on s390x.
Version 4.4.16
* Add support for the e2k architecture.
Version 4.4.15
* The compatibility symbols crypt_gensalt_r, xcrypt, xcrypt_r,
xcrypt_gensalt, and xcrypt_gensalt_r are deprecated further.
(These are alternative names for crypt_gensalt_rn, crypt, crypt_r,
crypt_gensalt, and crypt_gensalt_rn, respectively; there is no
difference in behavior.)
In an --enable-xcrypt-compat-files configuration, newly compiled
programs can still use functions with these names if they include
xcrypt.h, but a program that attempts to use one of these functions
*without* including xcrypt.h will fail to link. In particular, this
means AC_CHECK_FUNCS([xcrypt]) will not detect xcrypt, because the
test program generated by AC_CHECK_FUNCS does not include xcrypt.h.
In a --disable-xcrypt-compat-files --enable-obsolete-api
configuration, xcrypt.h is not installed and newly compiled programs
cannot use functions with these names, but existing binaries that
expect to find these symbols in a shared libcrypt.so.1 will still
work.
In a --disable-obsolete-api configuration, these symbols are not
defined at all; moreover, --disable-obsolete-api now implies
--disable-xcrypt-compat-files (which means xcrypt.h isn't installed).
Version 4.4.14
* Renamed bootstrap script: 'bootstrap' -> 'autogen.sh'.
If building from a Git checkout instead of a tarball release,
use './autogen.sh' to create the configure script.
Version 4.4.13
* libxcrypt now builds (including working tests) on Mac OSX.
* Speed up ka-sunmd5 by skipping most of the test phrases.
ka-sunmd5 is slower than the entire rest of the testsuite put
together, because the sunmd5 hash is Just That Slow and we have to do
extra tests for it to ensure bug-compatibility. No easy optimizations
are possible and the difficult optimizations are not worth the
engineering effort for this obsolete hash. Instead, skip most of the
test phrases. See comments in test/ka-table-gen.py!h_sunmd5 for
further explanation.
Version 4.4.12
* Another fix for GCC v10.x, which occurs on s390 architectures only.
Version 4.4.11
* Fixes for GCC v10.x (issue #95).
* Change how the known-answer tests are parallelized.
Version 4.4.10
* Fix ordering of hash methods in crypt-hashes.h when generated
using gawk < 4.1.0.
Version 4.4.9
* Fix false positive finding from CovScan.
Version 4.4.8
* Add binary compatibility for GNU/Hurd and GNU/kFreeBSD.
Version 4.4.7
* LICENSING: Add missing files and update license information.
* Fix -Wformat in test/crypt-kat.c.
Version 4.4.6
* Make unalignment test really unaligned.
Version 4.4.5
* Fix alignment problem for GOST 34.11 (Streebog) in gost-yestcrypt.
Some architectures in some circumstances do not allow unaligned
memory access (such as ARM, MIPS, SPARC) triggering SIGBUS. This
patch very crudely fixes this issue.
Being unfixed this would trigger SIGBUS when password buffer is
unaligned. Crash and fix are tested on UltraSparc T5 on GCC Compile
farm.
Version 4.4.4
* The crypt_* functions will now all fail and set errno to ERANGE if
their 'phrase' argument is longer than CRYPT_MAX_PASSPHRASE_SIZE
characters (this is currently 512). Formerly, longer passphrases
would either be silently accepted, silently truncated, or the
library would crash, depending on the hashing method.
* The NT hashing method no longer truncates passphrases at 128
characters; Windows does not do this. (The Windows login dialog
_limits_ interactively entered passphrases to 127 characters.
Passphrases set via the low-level API can be longer.)
Version 4.4.3
* Fix the value of SUNMD5_MAX_ROUNDS.
* Add generated C++-guards to <xcrypt.h>.
* Add --enable-obsolete-api-enosys configure option.
If enabled, this option replaces the obsolete APIs (fcrypt,
encrypt{,_r}, and setkey{,_r}) with stubs that set errno to
ENOSYS and return without performing any real operations.
This allows one to disable DEScrypt support while preserving
POSIX compliance.
For security reasons, the encrypt{,r} functions will also
overwrite their data-block argument with random bits.
The fcrypt function will always produce a failure token
(*0 or *1), unless the library was also configured with
--disable-failure-tokens, in which case it will always
return NULL.
Version 4.4.2
* Add test-alg-yescrypt for improved coverage.
* Add x32 specific inline asm.
Version 4.4.1
* Change the output of the gensalt function for the NT hashing method
($3$) to output just its prefix ($3$) instead of a fake salt.
The output buffer for the returned string must be at least 4 bytes
long.
* Decrase the minimum required amount of random bytes for the NT
hashing method to 1 byte, which is actually not used.
* The default linker flags now generate binaries with full read-only
relocations (including full read-only re-mapping of the GOT), if
supported by the linker and the system's native binary format.
Version 4.4.0
* Implement the crypt_preferred_method function.
This function can be used as a convenience function to get the prefix
of the preferred hash method.
Version 4.3.4
* --enable-hashes now supports 'fedora' as a group of hashing methods.
* Add aliases for xcrypt{,_r} and xcrypt_gensalt{,_r}.
They were added for code compatibility with libxcrypt v3.1.1
and earlier.
* Install the <xcrypt.h> header file, declaring the previously named
aliases, and a symlink from libxcrypt.so to libcrypt.so, if a shared
library is build. For static libraries a corresponding symlink for
the archive file will be installed.
The installation of the compatibility files can be disabled by
passing the '--disable-xcrypt-compat-files' flag to the configure
script.
* Replace the prototype for the crypt_gensalt_r function with a
declaration through a macro, so new compiled applications link
against the identical crypt_gensalt_rn function directly.
Version 4.3.3
* Add an alias for crypt_gensalt_r.
The function was available in older versions (v3.1.1 and earlier)
of libxcrypt. It has the same semantics and the same prototype as
the crypt_gensalt_rn function.
Version 4.3.2
* Fix the gensalt function for the NT hashing method ($3$) to
properly terminate its output string. The output buffer for the
returned string must be at least 30 bytes long.
* Remove the gensalt function for the bcrypt x variant ($2x$).
This prefix was never intended for use when hashing new passphrases.
The only use case originally intended was to manually edit '$2a$' to
'$2x$' in passphrase hashes to knowingly take the risk yet enable
users to continue to log in when upgrading systems with buggy bcrypt
implementations to fixed versions.
Version 4.3.1
* Reduce the number of methods that can be the default for new hashes.
We don’t want to accidentally encourage use of gost-yescrypt,
scrypt, or the bug-compatibility bcrypt variants by people who do
not have a specific need for them.
* sha256crypt ($5$) is not considered to be strong anymore. Thus
it was dropped from the STRONG and DEFAULT sets.
* The four variants of bcrypt ($2b$, $2a$, $2y$, $2x$) are now
independently selectable at configure time. The $2x$ variant has
been dropped from the STRONG set, because it has a severe bug
causing it to be easy to find collisions for some passwords. The
$2x$ and $2y$ variants have been dropped from the FreeBSD, NetBSD,
OpenBSD, and Solaris compatibility sets, because those operating
systems never supported those variants.
Version 4.3.0
* Implement the gost-yescrypt ($gy$) hashing algorithm.
* Remove all of the nonnull annotations, which are a questionable
optimization that have caused problems in the past and may cause
future problems on some systems.
* Rename all hash methods to match naming in John the Ripper.
* Make the configure switches --enable-obsolete-api and
--enable-hashes process their arguments case-insensitively; for
instance, "--enable-hashes=OpenBSD" and "--enable-hashes=openbsd"
are now understood as synonymous.
* Fix gensalt for bigcrypt if descrypt hash method is not selected
at compile time.
* Fix the bigcrypt hash method to reject too short settings and/or
descrypt hashes with a truncated phrase. Hashes with a setting
shorter than 13 characters and phrases shorter than 8 characters
are valid bigcrypt hashes, although they are identical with the
output generated by descrypt under the same conditions.
This only applies when the descrypt hash method is not selected
at compile time.
* Implement crypt_checksalt, which can be used by portable users of
libxcrypt to check whether the desired hash method is supported.
* Make a default prefix available whenever at least one strong hash
is enabled.
* Fix the definition of 'CRYPT_GENSALT_IMPLEMENTS_DEFAULT_PREFIX'
to reflect whether the default prefix is available or not.
Version 4.2.3
* Add bootstrap script. If building from a Git checkout instead of a
tarball release, use './bootstrap' to create the configure script.
* Use sha512 implementation from Colin Percival. Thus we now have a
sha512 implementation under the BSD license.
* Use md5 implementation from Alexander Peslyak. Thus we now have a
md5 implementation in the public domain.
* 'make dist' now generates bzip2 and xz compressed tarballs along
with the default gzip compressed tarball.
* The group 'altlinux' has been renamed to 'alt' in --enable-hashes,
as the ALTLINUX distribution has been rebranded to ALT some time ago.
* New tagged versions are automatically submitted for Coverity Scan:
https://scan.coverity.com/projects/besser82-libxcrypt
Version 4.2.2
* Convert existing manpages to BSD mdoc format.
Version 4.2.1
* Fix tests for yescrypt and scrypt, when failure-tokens have been
disabled.
Version 4.2.0
* Implement yescrypt ($y$) and scrypt ($7$) hashing algorithms.
* For scrypt the implemented gensalt function ensures every new hash
is computed using at least 32 MiBytes of RAM.
* yescrypt is the new default method used for new hashes.
* --enable-hashes now supports additional groups of hashing methods:
'altlinux', 'owl', and 'suse', which select the methods historically
supported on those operating systems.
* Added 'XCRYPT_VERSION_*' macros.
Version 4.1.2
* Add optional 'check-valgrind' target to the Makefile.
* Replace crypt-sha{256,512}.c with an implementation in the Public
Domain.
* Add alias man-pages for other crypt functions.
* Add configure option --disable-failure-tokens, which causes crypt
and crypt_r to return NULL on failure, as crypt_rn and crypt_ra do,
instead of a special "failure token". Using this option improves
compatibility with programs written on the assumption that, like
most C library functions, crypt and crypt_r will return NULL on
failure; but it breaks compatibility with programs that assume these
functions never return NULL. We're not sure which type of program
is more common. Please let us know if you encounter either.
* Improved handling of out-of-range cost parameters in gensalt.
The behavior is now:
- for hashes with a fixed cost parameter (DES/trad, DES/big, NTHASH,
MD5/bsd), crypt_gensalt only accepts 0 as the rounds argument.
- for hashes with a linear cost parameter (DES/bsdi, MD5/sun, SHA1,
SHA256, SHA512), crypt_gensalt accepts 0 or any value in the range
[1, ULONG_MAX] and clips it to the actual valid range for the hash
function, if necessary. In the case of DES/bsdi, even numbers
become odd, as well.
- for hashes with an exponential cost parameter (bcrypt),
crypt_gensalt only accepts 0 or a value in the actual valid range.
- the documented valid range for SHA1 is now [4, 4294967295] instead
of [1, 4294967295].
- all of this is tested.
Version 4.1.1
* --enable-hashes now supports additional groups of hashing methods:
'freebsd', 'netbsd', 'openbsd', 'osx', and 'solaris', which select
the hashes historically supported on those operating systems.
* Predictable behavior when arguments to crypt() are NULL or invalid
(issue #15).
* Hash formats $5, $6, and $md5 once again allow an explicit rounds
parameter specifying the default number of rounds (issue #16).
* The library no longer uses swapcontext(), for ease of debugging and
better compatibility with hardening mechanisms like Intel CET
(issue #18).
* Can now be built with versions of GNU ld older than 2.26.2.
* crypt_gensalt_ra no longer leaks memory on failure.
Version 4.1.0
* Fix spelling of SUSE.
* Lower the minimum required automake version to 1.14.
* Fix build with USE_SWAPCONTEXT turned off.
* Extend --enable-weak-hashes configure option to accept optional
"glibc" parameter. When specified, it enables only those of
weak hashes that are supported by historic versions of the
GNU libc.
* Fix the leak of obtained random bytes.
* Check expected output strings for deterministic methods.
* Fix memory leak in crypt_sha1crypt_rn.
* Fix read of random bytes out of bounds in gensalt_sha1crypt_rn.
* Make it possible to disable individual hashes at configure time.
The default is --enable-hashes=all. --enable-hashes=strong is the
equivalent of the old --disable-weak-hashes. You could even do
--enable-hashes=bcrypt,des to get a binary-compatible libcrypt.so.1
that still supports almost nothing other than bcrypt.
* Make salt validation pickier.
* Replace crypt-sunmd5.c with BSD-licensed cleanroom reimplementation.
* Make crypt_gensalt for $sha1 deterministic.
* Fix incorrect output-size computation in crypt_sha1crypt_rn.
* Add docs for SHA1, MD5/Sun, NTHASH.
* Introduce CRYPT_GENSALT_IMPLEMENTS_* feature test macros.
* Install libcrypt.pc symlink along with libxcrypt.pc.
* Extend --enable-obsolete-api configure option.
Make vendor specific parts of compatibility ABI that are enabled by
--enable-obsolete-api option configurable.
This allows vendors to enable only those parts of compatibility ABI
that are relevant to them.
* Extend overall test coverage.
Version 4.0.1
* Fixes for GCC v8.x
* Add symbol version for riscv64
* Fixed an uninitialized value in test-crypt-badsalt
Version 4.0.0
* Full binary backward compatibility with glibc libcrypt; all programs
compiled with glibc libcrypt, including vendor-patched versions that
include the Openwall extensions, should work with this libcrypt
(however, programs compiled against this libcrypt will NOT work with
glibc libcrypt).
* struct crypt_data is now only 32kB (from 128kB), and divided into a
public-API section and a properly opaque internal section.
* New feature: supplying a null pointer as the "prefix" argument to
any of the crypt_gencrypt functions will cause it to select the best
available hash function (in this release, bcrypt in mode 'a').
CAUTION: it must be a null pointer, not an empty string. If you
supply an empty string, that selects DES, which is the *worst*
available hash function.
* New feature: supplying a null pointer as the "rbytes" argument to
any of the crypt_gencrypt functions will cause it to acquire random
bytes from the operating system.
* The legacy functions bigcrypt, fcrypt, encrypt, encrypt_r,
setkey, and setkey_r are no longer available for use by new programs.
All of these (except fcrypt, which was just another name for crypt)
force the use of DES, which is no longer safe for any application.
* New configure option --disable-obsolete-api removes the above
functions from the library. Since this breaks compatibility with
glibc's libcrypt, when this option is used the shared library will
be libcrypt.so.2 instead of libcrypt.so.1, and all of the
compatibility symbol versions for the crypt* functions will be
omitted. This option is the default on all operating systems where
there is no GNU C Library to be compatible with.
* New configure option --disable-weak-hashes removes all support for
DES and MD5 hashes from the library. This option implies
--disable-obsolete-api, and will prevent DES and MD5 password hashes
from being *verified* -- accounts with such hashes are effectively
locked. It is intended for use in high-security new installations.
* Sensitive intermediate data is now thoroughly scrubbed from the
stack and CPU registers before the crypt functions return to their
callers.
* UFC-crypt has been replaced with FreeSec; this enables the reduction in
size of crypt_data, and adds full support for BSD extended DES hashes.
* Extensive code cleanup and portability work. The static library
should now be buildable with any C99 compiler, although some
features may not be available (notably acquiring random bytes from
the operating system and scrubbing the stack). The shared library
does still require some GNU extensions for symbol versioning.
* The configure options --enable-Wno-cast-align and --enable-bootstrap
are no longer necessary and have been removed.
* If building from a Git checkout instead of a tarball release, use
'autoreconf -i' to create the configure script; autogen.sh has been
removed.
* More thoroughly tested.
Version 3.1.1
* Add '--enable-Wno-cast-align' to silence 'cast increases required alignment'
* Whitespace clean-up
Version 3.1.0
* Update upstream-contact
* Add './configure --enable-bootstrap' to skip some tests on initial build
* Add bootstrap-script for Autotools
* Add LICENSE for bcrypt
* Update crypt_blowfish to v1.3
* Add '-Wextra' to CFLAGS
* Fix warnings generated by gcc 5.1.1
* Update Autotools
Version 3.0.4
* Fix warnings generated by gcc 4.6
Version 3.0.3
* Fix memory leak
* Fix compiler warnings
Version 3.0.2
* Fix generating salts for MD5
Version 3.0.1
* Fix build failures
Version 3.0
* Add sha256 and sha512 hashes
* Move all hashes into plugins
Version 2.4
* Sync with crypt_blowfish 1.0
Version 2.3
* Fix problems with gcc > 4.0
Version 2.2
* Fix realloc call in md5-crypt
Version 2.1
* Enable x86.S for i386 again
Version 2.0
* Rename all crypt* functions to xcrypt* to avoid clash with normal
libcrypt from glibc
Version 1.4
* Fix compiling with glibc > 2.3.1
* Sync with crypt_blowfish 0.4.5
Version 1.3
* Sync with current glibc CVS (fix for not correct initialication of
internal data structs)
Version 1.2
* Fix building with glibc 2.3.x
* Add support for HPPA
Version 1.1
* merge md5.h with xcrypt.h
* Add SHA1 functions and crypt
Version 1.0
* First release

179
Agent-Windows/OGP64/usr/share/doc/libxcrypt/README Normal file
View file

@ -0,0 +1,179 @@
[![Build matrix](https://github.com/besser82/libxcrypt/actions/workflows/config-matrix.yml/badge.svg)](https://github.com/besser82/libxcrypt/actions/workflows/config-matrix.yml)
[![Memcheck](https://github.com/besser82/libxcrypt/actions/workflows/memcheck.yml/badge.svg)](https://github.com/besser82/libxcrypt/actions/workflows/memcheck.yml)
[![Distcheck](https://github.com/besser82/libxcrypt/actions/workflows/distcheck.yml/badge.svg)](https://github.com/besser82/libxcrypt/actions/workflows/distcheck.yml)
[![COPR Build Status](https://copr.fedorainfracloud.org/coprs/besser82/libxcrypt_CI/package/libxcrypt/status_image/last_build.png)](https://copr.fedorainfracloud.org/coprs/besser82/libxcrypt_CI)
[![codecov](https://codecov.io/gh/besser82/libxcrypt/branch/develop/graph/badge.svg)](https://codecov.io/gh/besser82/libxcrypt)
[![Coverity Scan Build Status](https://scan.coverity.com/projects/17073/badge.svg)](https://scan.coverity.com/projects/besser82-libxcrypt)
[![Codacy Badge](https://api.codacy.com/project/badge/Grade/1ebaa2314aca4bab92e14130906d5096)](https://www.codacy.com/manual/besser82/libxcrypt?utm_source=github.com&amp;utm_medium=referral&amp;utm_content=besser82/libxcrypt&amp;utm_campaign=Badge_Grade)
README for libxcrypt
====================
libxcrypt is a modern library for one-way hashing of passwords. It
supports a wide variety of both modern and historical hashing methods:
yescrypt, gost-yescrypt, sm3-yescrypt, scrypt, bcrypt, sha512crypt,
sha256crypt, sm3crypt, md5crypt, SunMD5, sha1crypt, NT, bsdicrypt,
bigcrypt, and descrypt.
It provides the traditional Unix `crypt` and `crypt_r` interfaces, as
well as a set of extended interfaces pioneered by Openwall Linux,
`crypt_rn`, `crypt_ra`, `crypt_gensalt`, `crypt_gensalt_rn`, and
`crypt_gensalt_ra`.
libxcrypt is intended to be used by `login(1)`, `passwd(1)`, and other
similar programs; that is, to hash a small number of passwords during
an interactive authentication dialogue with a human. It is not
suitable for use in bulk password-cracking applications, or in any
other situation where speed is more important than careful handling of
sensitive data. However, it *is* intended to be fast and lightweight
enough for use in servers that must field thousands of login attempts
per minute.
Authorship and Licensing
------------------------
libxcrypt is currently maintained by Björn Esser and Zack Weinberg.
Many people have contributed to the code making up libxcrypt, often
under the aegis of a different project. Please see the AUTHORS and
THANKS files for a full set of credits.
libxcrypt as a whole is licensed under the GNU Lesser General Public
License (version 2.1, or at your option, any later version). However,
many individual files may be reused under more permissive licenses if
separated from the library. Please see the LICENSING file for a
comprehensive inventory of licenses, and COPYING.LIB for the terms of
the LGPL.
Bug Reports, Feature Requests, Contributions, Etc.
--------------------------------------------------
libxcrypt is currently maintained at Github: the canonical repository
URL is <https://github.com/besser82/libxcrypt>. Please file bug
reports at <https://github.com/besser82/libxcrypt/issues>. This is
also the appropriate place to suggest new features, offer patches,
etc. All your feedback is welcome and will eventually receive a
response, but this is a spare-time project for all of the present
maintainers, so please be patient.
Build Requirements and Instructions
-----------------------------------
To build from a tarball release, the tools required are the standard
Unix shell environment, a C compiler, and Perl (version 5.14 or
later). Follow the generic build and installation instructions in the
file `INSTALL`. There are several package-specific configure options;
run `./configure --help` for more detail on these options.
Run `man -l crypt.5` for more detail on the hashing algorithms that
can be enabled or disabled by `--enable-hashes`. You can do both of
these things before building the software.
Building from a Git checkout additionally requires the Autotools
suite: `autoconf`, `automake`, `libtool`, and `pkg-config`.
Run `./autogen.sh` at the top level of the source tree, and then
follow the instructions in `INSTALL` (which is created by that command).
The oldest versions of Autotools components that are known to work
are: autoconf 2.69, automake 1.14, libtool 2.4.6, pkg-config 0.29.
If you test with an older version of one of these and find that it
works, please let us know. We are not deliberately requiring newer
versions; we just can’t conveniently test older versions ourselves.
Portability Notes
-----------------
libxcrypt should be buildable with any ISO C1999-compliant C compiler,
with one critical exception: the symbol versioning macros in
`crypt-port.h` only work with compilers that implement certain GCC and
GNU Binutils extensions (`__attribute__((alias))`, GCC-style `asm`,
and `.symver`).
A few C2011 features are used; the intention is not to use any of them
without a fallback, but we do not currently test this. A few POSIX
and nonstandard-but-widespread Unix APIs are also used; again, the
intention is not to use any of them without a fallback, but we do not
currently test this. In particular, the crypt_gensalt functions may
not always be able to retrieve cryptographically-sound random numbers
from the operating system; if you call these functions with a null
pointer for the “rbytes” argument, be prepared for them to fail.
As of mid-2018, GCC and LLVM don’t support link-time optimization of
libraries that use symbol versioning. If you build libxcrypt with
either of these compilers, do not use `-flto`. See [GCC bug 48200][1]
for specifics; the problem is very similar for LLVM. Because this is,
at its root, a set of missing compiler features, we expect link-time
optimization won’t work in other C compilers either, but we haven’t
tested it ourselves.
[1]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48200
Compatibility Notes
-------------------
On Linux-based systems, by default libxcrypt will be binary backward
compatible with the libcrypt.so.1 shipped as part of the GNU C
Library. This means that all existing binary executables linked
against glibc’s libcrypt should work unmodified with this library’s
libcrypt.so.1. We have taken pains to provide exactly the same symbol
versions as were used by glibc on various CPU architectures, and to
account for the variety of ways in which the Openwall extensions were
patched into glibc’s libcrypt by some Linux distributions. (For
instance, compatibility symlinks for SUSE’s “libowcrypt” are provided.)
However, the converse is not true: programs linked against libxcrypt
will not work with glibc’s libcrypt. Also, programs that use certain
legacy APIs supplied by glibc’s libcrypt (`encrypt`, `encrypt_r`,
`setkey`, `setkey_r`, and `fcrypt`) cannot be *compiled* against
libxcrypt.
Binary backward compatibility can be disabled by supplying the
`--disable-obsolete-api` switch to `configure`, in which case libxcrypt
will install libcrypt.so.2 instead of libcrypt.so.1. This
configuration is always used on all operating systems other than
Linux. We are willing to consider adding binary backward
compatibility for other operating systems’ existing libcrypts, but we
don’t currently plan to do that work ourselves.
Individual hash functions may be enabled or disabled by use of the
`--enable-hashes` switch to `configure`. The default is to enable all
supported hashes. Disabling the traditional ‘des’ hash algorithm
implies `--disable-obsolete-api`. Security-conscious environments
without backward compatibility constraints are encouraged to use
`--enable-hashes=strong`, which enables only the hash functions that
are strong enough to be safe for newly hashed passwords.
The original implementation of the SunMD5 hashing algorithm has a bug,
which is mimicked by libxcrypt to be fully compatible with hashes
generated on (Open)Solaris. According to the only existing
[documentation of this algorithm][2], its hashes were supposed to have
the format `$md5[,rounds=%u]$<salt>$<checksum>`, and include only the
bare string `$md5[,rounds=%u]$<salt>` in the salt digest
step. However, almost all hashes encountered in production
environments have the format `$md5[,rounds=%u]$<salt>$$<checksum>`
(note the double $$). Unfortunately, it is not merely a cosmetic
difference: hashes of this format incorporate the first $ after the
salt within the salt digest step, so the resulting checksum is
different. The documentation hints that this stems from a bug within
the production implementation’s parser. This bug causes the
implementation to return `$$`-format hashes when passed a
configuration string that ends with `$`. It returns the intended
original format and checksum only if there is at least one letter
after the `$`, e.g. `$md5[,rounds=%u]$<salt>$x`.
The NT algorithm, in its original implementation, never came with any
`gensalt` function, because the algorithm does not use any. libxcrypt
ships a bogus `gensalt` function for the NT algorithm, which simply
returns `$3$`.
glibc’s libcrypt could optionally be configured to use Mozilla’s NSS
library’s implementations of the cryptographic primitives md5crypt,
sha256crypt, and sha512crypt. This option is not available in
libxcrypt, because we do not currently believe it is a desirable
option. The stated rationale for the option was to source all
cryptographic primitives from a library that has undergone FIPS
certification, but we believe FIPS certification would need to cover
all of libxcrypt itself to have any meaningful value. Moreover, the
strongest hashing methods, yescrypt and bcrypt, use cryptographic
primitives that are not available from NSS, so the certification
would not cover any part of what will hopefully be the most used code
paths.
[2]: https://dropsafe.crypticide.com/article/1389

13
Agent-Windows/OGP64/usr/share/doc/libxcrypt/THANKS Normal file
View file

@ -0,0 +1,13 @@
As mentioned in the README, many people have contributed to the code
making up libxcrypt, often under the aegis of a different project. Of
the past contributors, we particularly wish to credit David Burren,
Ulrich Drepper, Alec Muffett, Colin Percival, Alexey Degtyarev, and
Thorsten Kukuk.
As well as the present maintainers, active contributors to the library
include Solar Designer, Dmitry V. Levin, and <vt at altlinux dot org>.
We would also like to extend our thanks in advance to everyone who
will, in the future, send us bug reports, suggestions, and contributions.
-- The Authors.

100
Agent-Windows/OGP64/usr/share/doc/libxcrypt/TODO Normal file
View file

@ -0,0 +1,100 @@
to-do list for libxcrypt
------------------------
This list is categorized but not in any kind of priority order.
It was last updated 20 October 2018.
* Code cleanliness
* Find and remove any code that still does dodgy things with type punning
* Factor out all of the repetitive base64 code
* Factor out the multiple implementations of HMAC and PBKDF
* Testsuite improvements
* Investigate branch coverage
* Do some API fuzz testing and add missing cases to the testsuite
* Many of the `test-crypt-*.c` files repeat more or less the same
code with different data, consider merging them
* Portability
* Make sure the symbol versioning macros work with all of the
compilers that anyone needs (they use GCC extensions that clang
also supports).
* Hardening
* bcrypt-like selftest/memory scribble for all hashing methods
* how do we know the memory scribble is doing its job?
* build out of the box with compiler hardening features turned on
* something bespoke for not having to write serialization and
deserialization logic for hash strings by hand, as this is
probably the most error-prone part of writing a hashing method
* the most sensitive piece of data handled by this library is a
cleartext passphrase. OS may have trusted-path facilities for
prompting the user for a passphrase and feeding it to a KDF
without its ever being accessible in normal memory. investigate
whether we can use these.
* Additional hashing methods
* Argon2 <https://password-hashing.net/>
* ...?
* Runtime configurability (in progress on the [crypt.conf branch][])
* allow installations to enable or disable specific hash methods
without rebuilding the library
* make the default cost parameter used by `crypt_gensalt_*` for new
hashes configurable
* update the compiled-in defaults used by `crypt_gensalt_*` (not the
defaults used when no explicit cost parameter is present in a
hash; those can’t be changed without breaking existing stored hashes)
* relevant benchmarking at
<https://pthree.org/2016/06/28/lets-talk-password-hashing/>
* offer a way to tune cost parameters for a specific installation
* N.B. Solaris 11 has all of these features but our implementation will
probably not match them (they have a `crypt.conf` but it’s not the
same, and their `crypt_gensalt` is API-incompatible anyway).
[crypt.conf branch]: https://github.com/besser82/libxcrypt/tree/zack/crypt.conf
* Potential API enhancements:
* Support for "pepper" (an additional piece of information, _not_
stored in the password file, that you need to check a password)
* Reading passphrases from the terminal is finicky and there are
several competing, poorly portable, questionably sound library
functions to do it (`getpass`, `readpassphrase`, etc) -- should we
incorporate one?
* If we do, should it know how to trigger the trusted-path
password prompt in modern GUI environments? (probably)
* Make the crypt and crypt_gensalt static state thread-specific?
* Solaris 11 may have done this (its `crypt(3)` manpage describes
it as MT-Safe and I don’t see any other way they could have
accomplished that).
* if allocated on first use, this would also shave 32kB of
data segment off the shared library
* alternatively, add a global lock and *crash the program* if we
detect concurrent calls
* Allow access to more of yescrypt’s tunable parameters and ROM
feature, in a way that’s generic enough that we could also use it
for e.g. Argon2’s tunable parameters
* Other yescrypt-inspired features relevant to using this library to
back a “dedicated authentication service,” e.g. preallocation of
large blocks of scratch memory
* the main obstacles here are that `struct crypt_data` has a fixed
size which is either too big or too small depending how you look
at it, and no destructor function
* Permissive relicensing, to encourage use beyond the GNU ecosystem?
* Replace crypt-md5.c with original md5crypt from FreeBSD?
* Other files subject to the (L)GPL are crypt.c, crypt-static.c,
crypt-gensalt-static.c, crypt-obsolete.h, crypt-port.h,
test-badsalt.c. It is not clear to me how much material originally
assigned to the FSF remains in these files.
Several of them are API definitions and trivial wrappers that
could not be meaningfully changed without breaking them (so are
arguably uncopyrightable).
* Most of the test suite lacks any license or even authorship
information. We would have to track down the original authors.