aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/linden/indra/libgcrypt/libgcrypt-1.2.2/README
diff options
context:
space:
mode:
authorJay Threeth2011-04-04 11:48:26 -0700
committerJay Threeth2011-04-04 11:48:26 -0700
commit3c9cc506f741b980565ff5b3b001cd8b6ee36b12 (patch)
treecb862c57b3d5f74177cde3bd962a53fc377166f6 /linden/indra/libgcrypt/libgcrypt-1.2.2/README
parentbuild fixes, might build on linux now (diff)
downloadmeta-impy-3c9cc506f741b980565ff5b3b001cd8b6ee36b12.zip
meta-impy-3c9cc506f741b980565ff5b3b001cd8b6ee36b12.tar.gz
meta-impy-3c9cc506f741b980565ff5b3b001cd8b6ee36b12.tar.bz2
meta-impy-3c9cc506f741b980565ff5b3b001cd8b6ee36b12.tar.xz
add source to libraries, and cruft for building under windows
Diffstat (limited to '')
-rwxr-xr-xlinden/indra/libgcrypt/libgcrypt-1.2.2/README116
-rwxr-xr-xlinden/indra/libgcrypt/libgcrypt-1.2.2/README.SVN51
-rwxr-xr-xlinden/indra/libgcrypt/libgcrypt-1.2.2/README.apichanges113
3 files changed, 280 insertions, 0 deletions
diff --git a/linden/indra/libgcrypt/libgcrypt-1.2.2/README b/linden/indra/libgcrypt/libgcrypt-1.2.2/README
new file mode 100755
index 0000000..a821f13
--- /dev/null
+++ b/linden/indra/libgcrypt/libgcrypt-1.2.2/README
@@ -0,0 +1,116 @@
1 libgcrypt - The GNU crypto library
2 ------------------------------------
3 Version 1.2.1
4
5 Copyright 2000, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
6
7 This file is free software; as a special exception the author gives
8 unlimited permission to copy and/or distribute it, with or without
9 modifications, as long as this notice is preserved.
10
11 This file is distributed in the hope that it will be useful, but
12 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
13 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
14
15
16
17 Overview
18 --------
19
20 Libgcrypt is a general purpose crypto library based on the code
21 used in GnuPG. We can't start with a new version number because
22 libgcrypt was part of gnupg 1.1 and some applications already used
23 it and tested for the version number. We believe that the API can
24 stay as it is, except that new functions may be added in the
25 future.
26
27 Libgcrypt depends on the library `libgpg-error', which must be
28 installed correctly before Libgcrypt is to be built.
29
30
31 Mailing List
32 ------------
33
34 You may want to join the developer's mailing list
35 gcrypt-devel@gnupg.org by sending mail with a subject of
36 "subscribe" to gcrypt-devel-request@gnupg.org. An archive of this
37 list is available at http://lists.gnupg.org .
38
39
40 License
41 -------
42
43 Most of this library is distributed under the terms of the GNU
44 Lesser General Public License (LGPL); see the file COPYING.LIB for
45 the actual terms. However some parts are distributed under the
46 GNU General Public License (GPL) so if you configure Libgcrypt to
47 include these modules, you have to comply with the conditions of
48 the GPL as found in the file COPYING. The modules under the GPL
49 are:
50
51 rndunix - Entropy gatherer for Unices without a /dev/random
52 rndw32 - Entropy gatherer for MS Windows
53
54 The documentation is available under the terms of the GNU Free
55 Documentation License; see the file COPYING.DOC for the terms.
56
57 This library used to be available under the GPL - this was changed
58 with version 1.1.7 with the rationale that there are now many free
59 crypto libraries available and many of them come with capabilities
60 similar to Libcrypt. We decided that to foster the use of
61 cryptography in Free Software an LGPLed library would make more
62 sense because it avoids problems due to license incompatibilities
63 between some Free Software licenses and the GPL.
64
65 Please note that in many cases it is better for a library to be
66 licensed under the GPL, so that it provides an advantage for free
67 software projects. The Lesser GPL is so named because it does
68 less to protect the freedom of the users of the code that it
69 covers. See http://www.gnu.org/philosophy/why-not-lgpl.html for
70 more explanation.
71
72
73 Configure options
74 -----------------
75 Here is a list of configure options which are sometimes useful
76 for installation.
77
78 --enable-m-guard
79 Enable the integrated malloc checking code. Please
80 note that this feature does not work on all CPUs
81 (e.g. SunOS 5.7 on UltraSparc-2) and might give
82 you a bus error.
83
84 --disable-asm
85 Do not use assembler modules. It is not possible
86 to use this on some CPU types.
87
88 --enable-ld-version-script
89 Libgcrypt tries to build a library where internal
90 symbols are not exported. This requires support
91 from ld and is currently enabled for a few OSes.
92 If you know that your ld supports the so called
93 ELF version scripts, you can use this option to
94 force its use. OTOH, if you get error message
95 from the linker, you probably want to use this
96 option to disable the use of version scripts.
97 Note, that you should never ever use an
98 undocumented symbol or one which is prefixed with
99 an underscore.
100
101 --enable-ciphers=list
102 --enable-pubkey-ciphers=list
103 --enable-digests=list
104 If not otherwise specified, all algorithms
105 included in the libgcrypt source tree are built.
106 An exception are algorithms, which depend on
107 features not provided by the system, like 64bit
108 data types. With these switches it is possible
109 to select exactly those algorithm modules, which
110 should be built.
111
112 Contact
113 -------
114
115 See the file AUTHORS.
116
diff --git a/linden/indra/libgcrypt/libgcrypt-1.2.2/README.SVN b/linden/indra/libgcrypt/libgcrypt-1.2.2/README.SVN
new file mode 100755
index 0000000..436c7b0
--- /dev/null
+++ b/linden/indra/libgcrypt/libgcrypt-1.2.2/README.SVN
@@ -0,0 +1,51 @@
1If you are building from CVS, run the script
2
3./autogen.sh
4
5first, to make sure that you have all the necessary maintainer tools
6are installed and to build the actual configuration files. Then run
7
8./configure --enable-maintainer-mode
9
10followed by the usual make.
11
12If autogen.sh complains about insufficient versions of the required
13tools, or the tools are not installed, you may use environment
14variables to override the default tool names:
15
16 AUTOMAKE_SUFFIX is used as a suffix for all tools from the automake
17 package. For example
18 AUTOMAKE_SUFFIX="-1.7" ./autogen.sh
19 uses "automake-1.7" and "aclocal-1.7.
20 AUTOMAKE_PREFIX is used as a prefix for all tools from the automake
21 page and may be combined with AUTOMAKE_SUFFIX. e.g.:
22 AUTOMAKE_PREFIX=/usr/foo/bin ./autogen.sh
23 uses "automake" and "aclocal" in the /usr/foo/bin
24 directory.
25 AUTOCONF_SUFFIX is used as a suffix for all tools from the automake
26 package
27 AUTOCONF_PREFIX is used as a prefix for all tools from the automake
28 package
29 GETTEXT_SUFFIX is used as a suffix for all tools from the gettext
30 package
31 GETTEXT_PREFIX is used as a prefix for all tools from the gettext
32 package
33
34It is also possible to use the variable name AUTOMAKE, AUTOCONF,
35ACLOCAL, AUTOHEADER, GETTEXT and MSGMERGE to directly specify the name
36of the programs to run. It is however better to use the suffix and
37prefix forms as described above because that does not require
38knowledge about the actual tools used by autgen.sh.
39
40
41Please don't use autopoint, libtoolize or autoreconf unless you are
42the current maintainer and want to update the standard configuration
43files. All those files should be in the CVS and only updated manually
44if the maintainer decides that newer versions are required. The
45maintainer should also make sure that the required version of automake
46et al. are properly indicated at the top of configure.ac and take care
47to copy the files and not merely use symlinks.
48
49
50
51
diff --git a/linden/indra/libgcrypt/libgcrypt-1.2.2/README.apichanges b/linden/indra/libgcrypt/libgcrypt-1.2.2/README.apichanges
new file mode 100755
index 0000000..c95050f
--- /dev/null
+++ b/linden/indra/libgcrypt/libgcrypt-1.2.2/README.apichanges
@@ -0,0 +1,113 @@
1README.apichanges 2003-07-28
2
3
4We decided to change a couple of annoying things in Libgcrypt and to
5cleanup the API. The new API better fits into a multi-threaded
6environment and is more consistent. One import change is that all
7functions return error codes from a set of error codes shared between
8GnuPG, GPGME and Libgcrypt.
9
10This file contains some hints on how to port your application from
11libgcrypt <= 1.1.12 to the current API as of 1.1.42. We hope that
12there won't be another need for such a major change.
13
14
15* Types
16
17 All types definitions changed to a foo_t scheme; for some time we
18 will support the old names but you better start to rename them:
19
20 s/GCRY_MPI/gcry_mpi_t/
21 s/GcryMPI/gcry_mpi_t/
22 s/GCRY_SEXP/gcry_sexp_t/
23 s/GcrySexp/gcry_sexp_t/
24 s/GCRY_CIPHER_HD/gcry_cipher_hd_t/
25 s/GcryCipherHd/gcry_cipher_hd_t/
26 s/GCRY_MD_HD/gcry_md_hd_t/
27 s/GcryMDHd/gcry_md_hd_t/
28
29* Initialization
30
31 For proper initialization of the library, you must call
32 gcry_check_version() before calling any other function except for
33 these gcry_control operations:
34 GCRYCTL_SUSPEND_SECMEM_WARN
35 GCRYCTL_DISABLE_INTERNAL_LOCKING
36 GCRYCTL_ANY_INITIALIZATION_P
37 GCRYCTL_INITIALIZATION_FINISHED_P
38
39
40* Handles
41
42 gcry_cipher_open and gcry_md_open do now return an error code
43 instead of a NULL handle; the handle is now returned by
44 asigning it to the first argument. Example on how to change your
45 code:
46
47 Old:
48
49 hd = gcry_md_open (algo, flags);
50 if (!hd)
51 {
52 fprintf (stderr, "md_open failed: %s\n", gcry_errno (-1));
53 ....
54
55 New:
56
57 rc = gcry_md_open (&hd, algo, flags);
58 if (rc)
59 {
60 fprintf (stderr, "md_open failed: %s\n", gcry_strerror (rc));
61 ....
62
63 If you are not interested in the error code, you can do it in a
64 simplified way:
65
66 gcry_md_open (&hd, algo, flags);
67 if (!hd)
68 abort ();
69
70 i.e. the function makes sure that HD points to NULL in case of an error.
71 The required change for gcry_cipher_open is similar.
72
73* Message Digests
74
75 The order of the arguments to gcry_md_copy has been changed in order
76 to be more consistent with other functions of this type. This means
77 that the new message digest handle will be a copy of the message
78 handle specified by the second argument and stored at the address
79 pointed to by the first argument.
80
81* Error codes
82
83 gcry_errno () has been removed because it is hard to use in
84 multi-threaded environment. You need to save the error code
85 returned by the functions and use it either numerical or passing it
86 to gcry_strerror (since gcry_strerror is a wrapper function for
87 gpg_strerror, the latter function can also be used).
88
89 Instead of using the error codes GCRYERR_*, you have to use the
90 GPG_ERR_* names.
91
92* S-expressions
93
94 gcry_sexp_canon_len used to return a `historical' error code in
95 `errcode', this is not the case anymore; the value returned in
96 `errcode' is now a standard Libgcrypt (i.e. gpg-error) error code.
97
98* MPI
99
100 gcry_mpi_scan and gcry_mpi_print need the size of a provided buffer
101 as input and return the number of bytes actually scanned/printed to
102 the user. The old API used a single size_t Pointer for both tasks,
103 the new API distinguishes between the input and the output values.
104
105* Public Key cryptography
106
107 gcry_pk_decrypt used to return a `simple S-expression part' that
108 contains a single MPI value. In case the `data' S-expression
109 contains a `flags' element, the result S-expression is filled with a
110 complete S-expression of the following format:
111
112 (value PLAINTEXT)
113
generated by cgit v1.1 at 2025-01-25 18:19:47 +0000