| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
functions for backwards compatability.
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
unreviewed/untested at this point. Add support for a <comment> tag for
this.
|
| |
|
|
|
|
|
|
| |
GCC 4.3 on ARM converts __builtin_bswap32 into a jump into libgcc
rather than 4 simple instructions, so write it out using inline asm
instead.
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
| |
deque. This allows removing empty queues even if there are earlier
messages with outstanding data; the buffer slot remains so some memory
is still used, but reduced to just the pointer.
|
|
|
|
| |
Make comment clearer on how to enable stlport4 in Sun C++
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Set the upper limit on bcrypt hashing to workfactor 18, which takes
about 25 seconds to run on my desktop machine.
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
RNG. Pretty much required outside of very special cases, and otherwise
someone using --no-autoload will have to know to enable them
specifically or lots of things will break.
|
| |
|
|
|
|
| |
Avoid using auto_ptr in the CVC headers.
|
| |
|
| |
|
| |
|
|
|
|
| |
integer values. Update callers.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
FreeBSD. It is not being installed by Clang, so it appears on my
machine Clang is actually pulling the header in from GCC's private
include directory.
Closes PR 137
|
|
|
|
|
| |
Only change is the padding rule. It 'simplifies' the padding by making
it less flexible and harder to implement efficiently. :(
|
| |
|
| |
|
|
|
|
|
| |
rotate_right for SIMD types as a template specialization to avoid
problems in the amalgamation.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
intrinsics headers in header files. This is particularly useful for
allowing code that will be compiled by nvcc to include loadstor.h,
but might be useful in other situations as well.
|
|
|
|
|
|
|
| |
running 32 bit userspaces on sun4u machines, but it's often difficult
to tell what the compiler does/does not support in that respect, and
this will work for people who are using 64 bit userspace which I
_think_ is more common now. I hope.
|
| |
|
| |
|
| |
|
| |
|
| |
|