| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
for things like this, and the User_Interface class is going to die
as soon as I can manage it, anyway.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Switch from ???? datss to the phrase 'Not Yet Released' which is perhaps
less ambigious.
|
|
|
|
| |
doesn't actually care. Move it to examples/socket.h
|
| |
|
| |
|
|
|
|
|
| |
Lots of cleanups in the certificate documentation, which was still
just the raw output of my hacked up LaTeX to RST script.
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
adding back the keylength query functions.
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
it is.
|
| |
|
|
|
|
| |
for 1.10.0
|
| |
|
|\
| |
| |
| | |
and '51e8d8cc3eb1c29e097bdc77e2773b0fe6d342af'
|
| | |
|
| |
| |
| |
| | |
an i7-860 goes from 197 MiB/s to 256 - a 30% improvement!
|
|/
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
used in OpenBSD. Tested as compatible with a common Java
implementation (http://www.mindrot.org/projects/jBCrypt/)
|
|
|
|
| |
http://csrc.nist.gov/groups/ST/toolkit/documents/kms/key-wrap.pdf
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Only change is the padding rule. It 'simplifies' the padding by making
it less flexible and harder to implement efficiently. :(
|
| |
|
| |
|
|
|
|
| |
proposed SHA-3 parameter sets are supported.
|
|
|
|
| |
even keep around the prime products table anymore.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|