| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
It complains it cannot pass the __m128i without loss of alignment.
(Why, I have no idea.)
|
|
|
|
| |
Bit over 2x faster on my desktop
|
|
|
|
| |
256 bit ARX block cipher with hardware support, what's not to love.
|
|
|
|
|
|
|
|
|
|
|
|
| |
For whatever reason GCC 7 on i386 miscompiles this loop under -O3. I was
not able to reduce the bug to a small testcase - extracting the problem
section of the code to its own file, it behaves correctly.
Also oddly, I was never able to repro this using Arch's gcc-multilib
i386 compiler. But when compiled with the 'native' i386 compiler in
a chroot it immediately fails.
See GH #1148 and GH #882
|
|\ |
|
| |
| |
| |
| |
| |
| | |
If compiled with OpenSSL, clang emitted the warning "using the
result of an assignment as a condition without parentheses". Putting
parentheses around the assignment fixes this.
|
|\ \
| |/
|/| |
|
|/
|
|
|
|
|
| |
The Test::data_file() method adds the current data dir prefix to
the test data path so that it can be overwritten with the --data-dir
option. This was missing in the ffi test and could result in a
botan_x509_cert_load_file exception.
|
| |
|
|\ |
|
|/
|
|
|
|
| |
http_util is required by the x509 module to perform
online OCSP checks, which should be defaulted to ON.
Without being part of the policy, it would be disabled.
|
|\ |
|
| |
| |
| |
| |
| | |
The tests were generated by Botan but I was able to verify the
resulting signatures using Golang's ecdsa module.
|
|/ |
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
Eg previously ./botan keygen --algo=GOST-34.10 would create a GOST-34.10
curve over P-256, probably not useful in most cases.
|
| |
| |
| |
| | |
Also add hooks for keygen, etc
|
| |
| |
| |
| | |
This is a contribution from Ribose Inc (@riboseinc)
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
- only / file systems supported
- only absolute prefixes are supported
- result must not escape DESTDIR
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
The path tests can only work on UNIX-like OSs because Python's path
joining is required to use / as the path separator
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit b6b575d961b15d59f9382086fd59d1e5062a3cdb.
In order to disallow prepend_prefix for relative paths, we do not need
to disallow a relativ --refix for users that do not use DESTDIR
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
supersedes #997
This commit removes the (broken) --destdir command line option and introduces
the DESTDIR environment variable for the 'make install' target. When it's set,
the installation will take place in the DESTDIR directory, under the prefix set
by --prefix, with all of the internal references (pkgconfig file, etc)
containing only the prefix. This behavior is more standard (as in autotools and
co.), so makes packaging easier.
Based on work of danimo and zgyarmati
|
|\ \ \
| | | |
| | | |
| | | | |
line utils
|
| | | | |
|
| | | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
Based on the work by @slicer4ever, adds support for
Windows sockets to http_util. As a bonus, we get Windows support
for tls_client and tls_server CLI.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
(Missed hunk in previous commit)
|
| | | | |
|
| |/ / |
|
| |/
|/|
| |
| | |
[ci skip]
|
|\ \
| |/
|/|
| |
| | |
For whatever reason only the first commit in that branch got
merged to master. Not sure what happened.
|
| |
| |
| |
| |
| | |
This is not necessary for setup, but we want to zero the key out
in the event someone calls clear explicitly.
|
| | |
|
| |
| |
| |
| | |
Instead of giving subclasses access to the variable directly.
|
| | |
|
| | |
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This var is only used when encoding so was never read from, but
leaving it uninitialized is bad news. Flagged by Coverity.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is kind of an artificial change to appease Coverity but maybe
a bit cleaner in any case.
The issue is Coverity detects the throw in the case of PDP endian
being found at runtime, and assumes it might happen. And since
OS::get_processor_timestamp calls CPUID on x86 (to check for RDTSC),
it might throw. And so on up the call chain until it detect a throw
escaping from ~Timer_Scope in speed.cpp, which would crash.
However I do not have a PDP-endian x86 around to confirm this ... :)
|
| | |
| | |
| | |
| | |
| | |
| | | |
As we do inherit from it, and delete through the base pointer.
Found by Coverity scanner.
|
| | | |
|