aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Rickard Bondesson reported on botan-devel about some problems buildinglloyd2008-12-027-27/+17
| | | | | | | | | | | | | | | | | | | | on Solaris 10 with GCC 3.4.3. First, remove the definition of _XOPEN_SOURCE_EXTENDED=1 in mmap_mem.cpp and unix_cmd.cpp, because apparently on Solaris defining this macro breaks C++ compilation entirely with GCC: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6395191 In es_egd.cpp and es_dev.cpp, include <fcntl.h> to get the declaration of open(), which is apparently where open(2) lives on Solaris - this matches the include the *BSD man pages for open(2) show, though AFAIK the BSDs all compiled fine without it (probably due to greater efforts to be source-compatible with Linux systems by *BSD developers). I have not been able to test these changes personally on Solaris but Rickard reports that with these changes everything compiles OK. Update lib version to 1.8.0-pre. ZOMG. Finally.
* Update log file for 1.7.24 release 2008-12-011.7.24lloyd2008-12-011-1/+1
|
* Update readme for 1.7.24. Clean up some of the textlloyd2008-11-301-19/+23
|
* Add some test vectors for EMSA3(Raw) with RSA generated using Crypto++lloyd2008-11-301-0/+58
|
* Consolidate the useful stuff from doc/info.txt into readme.txtlloyd2008-11-303-72/+34
|
* s/modinfo.txt/info.txt/glloyd2008-11-301-2/+2
|
* Fix name of function in exception throwlloyd2008-11-301-1/+1
|
* New paths in dist scriptlloyd2008-11-291-4/+6
|
* In EMSA3_Raw::raw_data, clear message buffer (reset) before returninglloyd2008-11-281-1/+3
|
* Add XLC release date. Mention OpenSSL's AES crashes have unknown causelloyd2008-11-281-2/+2
|
* Change the readme to refer to 1.7.24 as the third release candidate.lloyd2008-11-281-3/+3
| | | | | I think given the number of changes so far it is best to make the next release 1.7.24 / 1.8.0-RC3 instead of 1.8.0 proper.
* Reorg 1.7.24 release notes. Mention adding test vectors.lloyd2008-11-281-5/+6
|
* Add verification tests for RSA/EMSA4 signatures generated by Crypto++ 5.5.2lloyd2008-11-281-0/+136
| | | | using SHA-224, SHA-256, and RIPEMD-160
* Add test vectors for RSA/EMSA2 generated by Crypto++ 5.5.2lloyd2008-11-281-0/+318
| | | | | using hashes SHA-224, SHA-256, SHA-384, SHA-512, RIPEMD-128, RIPEMD-160, and Whirlpool.
* Add test vectors for RSA EMSA3 with RIPEMD-160 and Tiger. Generated bylloyd2008-11-281-0/+153
| | | | Crypto++ 5.5.2 on motoko (x86-64 Gentoo)
* Allow asking for EMSA3(Raw) in get_emsa (returning a new EMSA3_Raw object)lloyd2008-11-281-0/+4
|
* Add a set of test vectors for RSA/EMSA3 with SHA-1, SHA-224, SHA-256,lloyd2008-11-281-0/+337
| | | | SHA-384, and SHA-512 generated using Crypto++ 5.5.2
* Add a variant of EMSA3 called EMSA3_Raw which does not hash the data orlloyd2008-11-283-46/+125
| | | | | | | add a digest identifier. This was a feature requested on the mailing list. Apparently this scheme is called CKM_RSA_PKCS in PKCS #11, and is supported by a number of libraries, including QCA.
* Add SHA-224 hash ids for EMSA2/X9.31 and EMSA3/PKCS #1 v1.5 public keylloyd2008-11-281-3/+14
| | | | signature padding schemes.
* Rickard Bondesson reported on the mailing list that he had noticedlloyd2008-11-283-12/+18
| | | | | | | | | | | | | | a discrepency between OpenSSL and Botan when generating SHA-512/EMSA3 signatures. In fact it turns out that the EMSA3 identifier for SHA-512 contained a typo and was incorrect. Unfortunately this means that SHA-512/EMSA3 signatures generated by Botan up until now will not be accepted by other implementations, and the signatures by other implementations would not be accepted by Botan. Currently I am not making any provision for backwards compatability with the old incorrect hash identifier, since I am assuming/guessing that SHA-512/EMSA3 is not a very common combination.
* Add Doxygen comment for Timer::clock. Fix @return in benchmark.h and x509_ca.hlloyd2008-11-253-2/+6
|
* Add test_es, a program that polls each enabled entropy source (both fastlloyd2008-11-251-0/+101
| | | | and slow) and prints the data it gets back to the screen for inspection.
* If the read succeceed in EGD_EntropySource::slow_poll, the loop wouldlloyd2008-11-252-0/+3
| | | | | just continue on instead of returning the length of the buffer recv'ed from EGD.
* Drop todo.txt - moved to http://botan.randombit.net/todo.htmllloyd2008-11-251-160/+0
|
* Document disabling OpenSSL AESlloyd2008-11-241-0/+1
|
* Disable using OpenSSL's AES - it is causing crashes for an unknown reason.lloyd2008-11-241-0/+6
| | | | | | Backtrace is deep inside EVP. Valgrind says it is writing after the end of the allocated buffer. Other ciphers (all 64-bit blocks) are fine. I do not know if the problem is 64/128 bit or some other reason.
* Fix a roundoff error in the block cipher benchmarkslloyd2008-11-241-16/+17
|
* Rephrase some log entrieslloyd2008-11-241-5/+5
|
* Link to botan-devel mailman pagelloyd2008-11-241-6/+8
|
* Update PGP keyslloyd2008-11-241-88/+80
|
* Mention integer overflow being fixedlloyd2008-11-241-0/+1
|
* In Pooling_Allocator::get_more_core, limit in_bytes to at most 1 MiB tolloyd2008-11-242-3/+4
| | | | avoid a potential integer overflow in the multiplication. Fixes bugid 27
* Add an example taken from the tutoriallloyd2008-11-241-0/+55
|
* Update build instructionslloyd2008-11-241-10/+19
|
* In pkg-config, don't link against a specific version number (eg -lbotan-1.8.0)lloyd2008-11-241-1/+1
| | | | | | | because that totally breaks with static libs. OTOH, not using the version number totally breaks if more than one version is installed. Kind of a tradeoff...
* Update readme and info files to reflect that 1.8.0 will be a (theoretically)lloyd2008-11-242-3/+8
| | | | stable release.
* Document changes since 1.7.23. Bump version number to 1.7.24-pre; I'lllloyd2008-11-243-3/+9
| | | | | decide later on if changes warrant another release candiate or not. If not, 1.7.24 will be remarked as 1.8.0 prior to release.
* Make X509_Store::CRL_Info public for IBM XLC 0.9 for Celllloyd2008-11-241-10/+14
|
* Wrap code and struct definitions internal to sha1_sse2_imp.cpp in anlloyd2008-11-241-0/+4
| | | | | anonymous namespace (in particular this should prevent Doxygen for generating documentation about the v4si union declared there).
* In es_ftw, remove check for if the return value of read() is largerlloyd2008-11-241-1/+1
| | | | | | than the value we gave it. This is pretty unlikely... also caused an annoying warning with some versions of GCC b/c it couldn't figure out the signed/unsigned comparison was safe in this case.
* If configure.pl guesses the CPU using /proc/cpuinfo or uname, it remindslloyd2008-11-241-2/+3
| | | | | | | | the user that it can override via --cpu, however if it was guessed using Config{'archname'} the user was not so reminded. This is actually the worst possible case since Perl's Config setting is probably the least reliable method (which is why it is only used if /proc/cpuinfo and uname are not around).
* Update for 1.7.23 release 2008-11-231.7.23lloyd2008-11-232-5/+5
|
* Modify es_ftw to use xor_into_buflloyd2008-11-231-4/+4
|
* Reduce size of I/O buffer in HMAC_RNG from 128 to 96 bytes. Unlikely that anylloyd2008-11-231-1/+1
| | | | | entropy source will realistically be able to provide even 768 bits of entropy, so this is probably overkill even still.
* Previously es_unix would always try to get 16K, then return. Now itlloyd2008-11-231-4/+3
| | | | | | | tries to get an amount cooresponding with the size of the output buffer, specifically 128 times the output size. So, assuming we have enough working sources, each output byte will be the XOR of (at least) 128 bytes of text from the output programs. (Though RLE may reduce that somewhat)
* Add an Algorithm_Factory& argument to Engine::get_cipher to avoid alloyd2008-11-234-8/+13
| | | | dependency on libstate.h
* Remove openssl/gnump engine dep on libstate, no longer a deplloyd2008-11-232-8/+0
|
* Document new options in release noteslloyd2008-11-231-0/+1
|
* Add handy aliases to configure for controlling the modules using OpenSSL,lloyd2008-11-231-0/+9
| | | | | | | | | | | | | | GNU MP, zlib, and bzip2. --with-{openssl,gnump,bzip2,zlib} --without-{openssl,gnump,bzip2,zlib} They have the exact same effect as --enable-modules=x or --disable-modules=x This turned out to be a much easier way of specifying options for the Gentoo ebuild. It is likely that other distro builds architectures will also prefer this option style as being somewhat more autoconf-like and fitting in with existing command templates.
* Limit the output size of fast polls by the BeOS, Unix, and Win32 entropylloyd2008-11-233-0/+3
| | | | pollers that grab basic statistical data to 32 bytes.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-01 21:10:21 +0000