aboutsummaryrefslogtreecommitdiffstats
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* Tick version numbers to 1.10.0lloyd2011-04-144-107/+78
| | | | | | | | | | | | | | More documentation updates. The clean target wasn't removing one of the symlinks. In the self-test application, warn if the version we are linked against does not match the version we were built against. This always indicates a problem. Someone who had an older version installed on their system got very confused when the test app was linked against it at runtime; this warning would have saved a couple hours of puzzling by me. This would also have helped avoid the nasty bug in 1.8.3
* Spelling fixeslloyd2011-04-123-8/+8
|
* Example updates1.9.16lloyd2011-04-113-21/+22
|
* Update docslloyd2011-04-117-37/+318
|
* Two more files from the planelloyd2011-04-112-0/+190
|
* More docslloyd2011-04-085-7/+13
|
* More doc updateslloyd2011-04-0812-276/+84
|
* ECC private keys had two different constructors, one taking a grouplloyd2011-04-0820-425/+160
| | | | | | | | | | | | | | | | and a random number generator, and the other taking a group and a preset private key value. The DL private keys instead have on constructor for this; if the x value is zero, then a new random key is created. For consistency, do this with ECC as well. ECDH actually didn't have one of these constructors, forcing you to either load from PKCS #8 or else use a random key. Rename EC_Domain_Params to EC_Group, with a typedef for compatability. More doc updates. Update mtn ignores for Sphinx output
* Drop the GTK example; it probably makes more sense to use threadslloyd2011-04-085-708/+0
| | | | | for things like this, and the User_Interface class is going to die as soon as I can manage it, anyway.
* More pubkey doc updateslloyd2011-04-0868-71/+6916
|
* Pile more doc updateslloyd2011-04-089-406/+634
|
* Fix syntax highlightinglloyd2011-04-063-13/+15
|
* s/Release/Version/lloyd2011-04-061-152/+161
| | | | | Switch from ???? datss to the phrase 'Not Yet Released' which is perhaps less ambigious.
* Remove the socket wrapper code, as the SSL interface itselflloyd2011-04-051-2/+8
| | | | doesn't actually care. Move it to examples/socket.h
* A bit more BigInt documentationlloyd2011-04-041-25/+64
|
* Avoid pyc file from running Sphinxlloyd2011-04-041-0/+4
|
* Refer the user to the Doxygen output as well.lloyd2011-04-042-148/+133
| | | | | Lots of cleanups in the certificate documentation, which was still just the raw output of my hacked up LaTeX to RST script.
* Put 'Release' in front of every version. This causes Sphinx tolloyd2011-04-041-150/+150
| | | | | | generate nice permalink ids like #release-1-9-15-2011-03-21, rather than #id3 (especially useless since those will change as new versions are added, making them transient permalinks)
* Convert most of the documentation to reStructured Text, addinglloyd2011-04-0494-12326/+5443
| | | | | | | | | | | | | | | | | | | a makefile to build it with Sphinx (http://sphinx.pocoo.org/). Previously credits.txt listed public domain code sources; instead directly credit the authors in the relevant files and delete that file. Drop the draft FIPS 140 security policy; I can't imagine FIPS 140 validation will ever happen, and if it does, I don't want anything to do with it. Also drop the internals doc, which was so out of date (and incomplete) as to be worthless. Move the tutorials and InSiTo pdfs into old/ for the time being, until anything relevant from them can be filtered out and converted into RST.
* Remove some old scripts. Move the PGP key to a txt file. Documentlloyd2011-03-247-338/+39
| | | | adding back the keylength query functions.
* Disable the by default strong key checking on loading a privatelloyd2011-03-211-0/+3
| | | | | | key. This slowed down loading private keys somewhat dramatically. Most people don't care, but both groups using botan for DNSSEC has performance problems due to it.
* Just use the plain textlloyd2011-03-211-1/+2
|
* At this point the 'old' one is still much more useful, out of date aslloyd2011-03-213-932/+932
| | | | it is.
* Tick to 1.9.16-devlloyd2011-03-211-1/+3
|
* Update notes, version, and readme for 1.9.15, first release candidate1.9.151.10.0-rc1lloyd2011-03-211-6/+12
| | | | for 1.10.0
* Joel really was the driver behind Win32 DLLs in general, credit as suchlloyd2011-03-181-1/+1
|
* merge of '1bf20e797477a87c044a8fd74af47d872f630831'lloyd2011-03-141-2/+4
|\ | | | | | | and '51e8d8cc3eb1c29e097bdc77e2773b0fe6d342af'
| * More noteslloyd2011-03-091-0/+4
| |
* | Use the same mesasge expansion trick in SHA-512. Performance onlloyd2011-03-131-2/+3
| | | | | | | | an i7-860 goes from 197 MiB/s to 256 - a 30% improvement!
* | Modify SHA-224/SHA-256 so that it does the message expansion inlloyd2011-03-121-0/+4
|/ | | | | | registers as needed (16 turns before the value is used), with indexes fully precomputed. On a Core i7-860 with GCC 4.5.2, performance went from 152 MiB/s to 167 MiB/s.
* Tick to 1.9.15-devlloyd2011-03-071-0/+4
|
* Tick version numbers for 1.9.14 release1.9.14lloyd2011-03-011-1/+1
|
* Add bcrypt and keywrap exampleslloyd2011-02-232-0/+83
|
* Fix PR 142: the zlib filters were not updated in 1.9.11 to use zeroiselloyd2011-02-181-0/+1
| | | | | | | | instead of clear, so the buffer ended up having size zero, which meant the compression library could never actually do anything, and we would infinite loop. Also add buffer clearing to bzip2, which was missing it entirely.
* Add support for bcrypt, the Blowfish-based password hashing schemelloyd2011-02-161-0/+1
| | | | | used in OpenBSD. Tested as compatible with a common Java implementation (http://www.mindrot.org/projects/jBCrypt/)
* Add the NIST AES key wrap algorithm, as specified in RFC 3394 andlloyd2011-02-151-0/+1
| | | | http://csrc.nist.gov/groups/ST/toolkit/documents/kms/key-wrap.pdf
* Tick version to 1.9.14-devlloyd2011-02-101-0/+2
|
* Tick to 1.9.13 release1.9.13lloyd2011-02-091-1/+5
|
* Add a new configure.py option --distribution-info which sets a macrolloyd2011-02-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | in build.h named BOTAN_DISTRIBUTION_INFO. The default value is 'unspecified'. People packaging botan could set this to another value, for instance 'Gentoo 1.9.13-r3' or 'Debian 1.9.13-1', or 'pristine' to indicate a completely unmodified/stock version. This was suggested by Zooko for Crypto++ in http://sourceforge.net/apps/trac/cryptopp/ticket/11 and seemed like an idea worth stealing. Don't default the version datestmap to the current day if unset, instead set to zero. This allows applications to detect unreleased versions. Document that version_datestamp will return zero for unreleased versions. Change the version_string function to return more information about the current version, including the release date and distribution information. It will now return strings like: Botan 1.9.13 (released 20110207, distribution Gentoo 1.9.13-r3) or for an unreleased version: Botan 1.9.13 (unreleased version, distribution unspecified)
* Fix the ordering of the GOST 34.10 signature values. Add a testlloyd2011-02-071-0/+1
| | | | | | | | | derived from a DNSSEC RFC. Bug reported by Bert Hubert to the mailing list. According to Bert, this ordering is compatible with the version included in OpenSSL. Also, benchmark GOST 34.10 using the GOST 34.11 hash since that is always what it is used with.
* Update Keccak to the round 3 variant announced 2011-01-17lloyd2011-01-201-0/+1
| | | | | Only change is the padding rule. It 'simplifies' the padding by making it less flexible and harder to implement efficiently. :(
* Tick to 1.9.13-devlloyd2010-12-151-0/+2
|
* Update versions for 1.9.12 release1.9.12lloyd2010-12-131-1/+2
|
* Add a simple but functioning implementation of Keccak. Only thelloyd2010-12-101-0/+1
| | | | proposed SHA-3 parameter sets are supported.
* Drop this script, not really useful to anyone, especially as we don'tlloyd2010-12-101-63/+0
| | | | even keep around the prime products table anymore.
* Fix OpenSSL engine compile :/lloyd2010-12-011-0/+1
|
* Add LDFLAGS to Python link linelloyd2010-12-011-0/+1
|
* Now 1.9.12-devlloyd2010-11-301-0/+2
|
* Fix tls_server example compilationlloyd2010-11-301-2/+8
|
* Syntax fix1.9.11lloyd2010-11-291-1/+1
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-26 06:37:33 +0000