Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Tick version to 1.9.14-dev | lloyd | 2011-02-10 | 1 | -0/+2 |
| | |||||
* | Tick to 1.9.13 release1.9.13 | lloyd | 2011-02-09 | 1 | -1/+5 |
| | |||||
* | Add a new configure.py option --distribution-info which sets a macro | lloyd | 2011-02-07 | 1 | -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 test | lloyd | 2011-02-07 | 1 | -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-17 | lloyd | 2011-01-20 | 1 | -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-dev | lloyd | 2010-12-15 | 1 | -0/+2 |
| | |||||
* | Update versions for 1.9.12 release1.9.12 | lloyd | 2010-12-13 | 1 | -1/+2 |
| | |||||
* | Add a simple but functioning implementation of Keccak. Only the | lloyd | 2010-12-10 | 1 | -0/+1 |
| | | | | proposed SHA-3 parameter sets are supported. | ||||
* | Drop this script, not really useful to anyone, especially as we don't | lloyd | 2010-12-10 | 1 | -63/+0 |
| | | | | even keep around the prime products table anymore. | ||||
* | Fix OpenSSL engine compile :/ | lloyd | 2010-12-01 | 1 | -0/+1 |
| | |||||
* | Add LDFLAGS to Python link line | lloyd | 2010-12-01 | 1 | -0/+1 |
| | |||||
* | Now 1.9.12-dev | lloyd | 2010-11-30 | 1 | -0/+2 |
| | |||||
* | Fix tls_server example compilation | lloyd | 2010-11-30 | 1 | -2/+8 |
| | |||||
* | Syntax fix1.9.11 | lloyd | 2010-11-29 | 1 | -1/+1 |
| | |||||
* | Update version numbers for 1.9.11 release | lloyd | 2010-11-29 | 1 | -1/+1 |
| | |||||
* | Remove incorrect comment | lloyd | 2010-11-29 | 1 | -16/+4 |
| | |||||
* | Inherit policy and override check_cert | lloyd | 2010-11-29 | 2 | -2/+33 |
| | |||||
* | Add X509_Certificate::to_string | lloyd | 2010-11-29 | 2 | -122/+3 |
| | | | | The x509info example now just calls that | ||||
* | MemoryRegion::set was removed | lloyd | 2010-11-29 | 1 | -1/+2 |
| | |||||
* | Use the same intro text as the Linux credits file, rather than | lloyd | 2010-11-29 | 1 | -15/+12 |
| | | | | referencing it. | ||||
* | More release notes | lloyd | 2010-11-23 | 1 | -1/+4 |
| | |||||
* | More details in changelog | lloyd | 2010-11-17 | 1 | -5/+10 |
| | |||||
* | Add a Mac OS X tip from Thomas Keller | lloyd | 2010-11-12 | 1 | -0/+13 |
| | |||||
* | Update Skein-512 for the new 1.3 specification, just changes the key | lloyd | 2010-11-03 | 1 | -0/+1 |
| | | | | schedule constant to prevent rotational attacks. | ||||
* | Add 1.8.11 changelog | lloyd | 2010-11-02 | 1 | -0/+8 |
| | |||||
* | Remove BufferedComputation::OUTPUT_LENGTH | lloyd | 2010-10-29 | 1 | -18/+24 |
| | |||||
* | New way of specifying key lengths | lloyd | 2010-10-29 | 1 | -1/+6 |
| | |||||
* | Remove use of lookups | lloyd | 2010-10-29 | 2 | -6/+10 |
| | |||||
* | Document adding base64 standalone encoder | lloyd | 2010-10-28 | 1 | -0/+1 |
| | |||||
* | Make TLS_Client entirely via callbacks, not talking to Socket directly | lloyd | 2010-10-19 | 1 | -1/+3 |
| | |||||
* | Use binary I/O where needed | lloyd | 2010-10-15 | 10 | -11/+11 |
| | |||||
* | Fix examples | lloyd | 2010-10-13 | 4 | -7/+11 |
| | |||||
* | More size_t. Document changes | lloyd | 2010-10-13 | 1 | -2/+5 |
| | |||||
* | Update API doc | lloyd | 2010-10-13 | 1 | -2/+2 |
| | |||||
* | Fix compilation of examples; benchmarking and RNG changes mostly | lloyd | 2010-10-12 | 5 | -35/+13 |
| | |||||
* | Forward port CRL fixes from rev 7bb2001cd554a1acc3d345914ea710ff0e1d3a6b | lloyd | 2010-10-07 | 1 | -0/+1 |
| | |||||
* | s/x.ptr()/&x[0]/ | lloyd | 2010-09-30 | 1 | -5/+5 |
| | |||||
* | Document removing append | lloyd | 2010-09-15 | 1 | -2/+3 |
| | |||||
* | Fix examples for destroy being renamed clear | lloyd | 2010-09-13 | 2 | -2/+2 |
| | |||||
* | Remove more uses of vector to pointer implicit conversions | lloyd | 2010-09-13 | 1 | -1/+5 |
| | |||||
* | Read input as binary | lloyd | 2010-09-08 | 1 | -1/+1 |
| | |||||
* | Wording changes | lloyd | 2010-09-08 | 1 | -3/+3 |
| | |||||
* | Document recent changes | lloyd | 2010-09-08 | 1 | -2/+5 |
| | |||||
* | Specify the target host and port for tls_client on the command line | lloyd | 2010-09-08 | 1 | -3/+18 |
| | |||||
* | Big, invasive but mostly automated change, with a further attempt at | lloyd | 2010-09-07 | 1 | -1/+1 |
| | | | | | | | | | | | | | | harmonising MemoryRegion with std::vector: The MemoryRegion::clear() function would zeroise the buffer, but keep the memory allocated and the size unchanged. This is very different from STL's clear(), which is basically the equivalent to what is called destroy() in MemoryRegion. So to be able to replace MemoryRegion with a std::vector, we have to rename destroy() to clear() and we have to expose the current functionality of clear() in some other way, since vector doesn't support this operation. Do so by adding a global function named zeroise() which takes a MemoryRegion which is zeroed. Remove clear() to ensure all callers are updated. | ||||
* | Oops... renamed this quite a while ago, never updated example | lloyd | 2010-09-07 | 1 | -6/+6 |
| | |||||
* | Realization while thinking about the recently added truncate: in a STL | lloyd | 2010-09-07 | 1 | -1/+0 |
| | | | | | | | | | | | | | | | | | | container like vector, truncate is simply resize, but what MemoryRegion called resize will zap the entire contents, and then what was resize was called grow_to. This is really problematic in terms of the goal of replacing MemoryRegion with a vector with a custom allocator. In this checkin: - Remove MemoryRegion::grow_to and MemoryRegion::truncate - Change the semantics of MemoryRegion::resize to change the size while keeping any current contents intact (up to the new size), zero initializing any new values. Unrelated, just noticed the lack while I was in there, add a version of CryptoBox::decrypt taking a std::string for the input. | ||||
* | Fix dependency update scripts | lloyd | 2010-09-03 | 2 | -2/+2 |
| | |||||
* | Document recent changes | lloyd | 2010-09-03 | 1 | -0/+4 |
| | |||||
* | Add 1.8.10 change notes | lloyd | 2010-08-31 | 1 | -0/+9 |
| |