| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
decryption. Currently only used for counter mode. Doesn't offer much
advantage as-is (though might help slightly, in terms of cache effects),
but allows for SIMD implementations to process multiple blocks in parallel
when possible. Particularly thinking here of Serpent; TEA/XTEA also seem
promising in this sense, as is Threefish once that is implemented as a
standalone block cipher.
|
| |
|
|
|
| |
files. Were missed by the automated script that added them to the cpp/h
files, it appears.
|
| |
|
|
|
| |
Serpent seems very nicely suited to a SSE2 SIMD implementation, and CTR
mode can handle multiple blocks in parallel. Input lens 1 to 128 bytes.
|
| |
|
|
| |
Add a comment nothing that Python <= 2.3 is not supported
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
systems. This was something that for whatever reason that I have
long since forogotten was a good idea on IRIX running MIPS circa
a decade ago, but was reported to cause problems on the Debian
builds.
Add mipsel as an alias for the mips32 architecture for Debian.
The mips32 submodel names were badly typoed and did not work
correctly.
Remove the leading mips32- and mips64- from MIPS submodel names.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
what is there
|
| |
|
|
|
|
|
| |
based on the SGI Pro64 and Pathscale EKOpath compilers. Only tested on an
x86-64 system running Linux (v4.2.1). Miscompiles a few of the block ciphers
(segvs, didn't bother to diagnose further; recompile with -O1 to fix), other
than that seems OK.
|
| | |
|
| |
|
|
|
|
| |
32-bit machines (for the version check if -fpermissive is needed)
and then fail with an uncaught exception when subprocess.Popen signaled the
problem. Instead note the failure and carry on.
|
| | |
|
| |
|
|
| |
used on Visual C++
|
| | |
|
| |
|
|
| |
Contributed by Patrick Georgi
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't read any file that is not world-readable. This avoids trouble when
running as root, since on Linux various special files can cause odd
interactions and/or blocking behavior when read (for instance /proc/kmsg).
ssumption is that no such files are world-readable. This also avoids any
issue of reading data that is potentially sensitive.
Instead of reading the first 1 KB of each file, only read the first 128
bytes. This prevents large files (like /proc/config.gz or /proc/kallsyms)
from swamping the input buffer; these inputs are pretty static and
shouldn't count for much. Reducing to 128 bytes causes a poll to read
about 400 different files, rather than ~30.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the phrase 'for any use' - implied by the conditions.
Add 'All rights reserved.' after the (C) notice.
Remove the name+URL in the text and lead off with a statement that
Botan is distributed under the following terms: <blah>
Combine the two all-CAPS sentences disclaiming warranty into a single
paragraph.
The main reasoning behind this is to make the actual license text
totally equivalent to the FreeBSD/NetBSD licenses, which is an offical
Open Source(tm) license as declared by the OSI.
|
| | |
|
| |
|
|
|
| |
Python configure scripts. Previously Python version would give up, and
the Perl one would guess i686 (!)
|
| |
|
|
|
| |
in this header, instead use the macro version BOTAN_MP_WORD_BITS. Only
affected 64-bit SPARC builds.
|
| |
|
|
|
|
|
|
|
| |
TARGET_CPU_IS macro. This would otherwise cause problems on HP-PA, as
it would generate invalid macros like TARGET_CPU_IS_HPPA2.0
Also in configure.py, replace hyphens with underscores in the submodel name
for generating the macro (configure.pl already did this). Otherwise using
the sparc64-ultraX submodels would also generate an invalid macro in build.h
|
| | |
|
| |
|
|
|
| |
patches fixing grammatical problems in api.tex as well as adding/fixing
various Doxygen comments and so forth.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Previous behavior was that if a module was explicitly disabled, the
libraries that module used would still be linked in. So for instance
configure.pl --disable-modules=pthreads --without-openssl
would cause libpthread and libcrypto to be included in the final link!
This bug only affected the Perl configure
|
| |
|
|
|
|
|
|
|
| |
implementation. This had been the case since at least 1.8.0. Remove it, since
implementing this signature would require having the library create an
AutoSeeded_RNG, which seems like it might be quite surprising to an unsuspecting
user.
Problem reported by M. Braun in ticket 44
|
| |
|
|
| |
in ticket #38
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Fix --enable-asm (had same effect as --disable-asm)
Fix mp_bits calculation; took into account both modules which were enabled
and ones that were explicitly disabled, for instance
./configure.pl --disable-modules=mp_amd64 -> mp_bits == 64
|
| | |
|
| |
|
|
|
| |
when faced with the full set of module interdependencies. Use a new
algorithm that handles it OK.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
the info.txt files with the right module dependencies.
Apply it across the codebase.
|
| |
|
|
|
|
|
| |
just toplevel pubkey). This was a convention I realized made sense sometime
on when I was first doing the modularization changes.
Move pkcs8.* and x509_key.* to pk_codecs
|
| |
|
|
|
|
|
|
|
| |
Useful for tracking where the big balls of mud are.
Fix dependencies in gost_3411 (depends on the gost block cipher), and
the TLS PRF (depends on HMAC). Also hide TLS_PRF::P_hash in an anonymous
namespace instead of making it a private static function. I don't think
this will affect binary compat, since it was statically linked.
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| | |
and 'e6d5e12d439e2f149f547f1afe47fea14e7863c2'
|
