| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
As long as we support DSS ciphersuites, we should test them,
even if they're deprecated.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
The parameter comments were misleading because they did not take
into account that input_length must be rounded up to a multiple of
3 and 4 for encode and decode respectively. Two new functions were
added to calculate the correct maximum output length.
|
|\ \ |
|
| |/
| |
| |
| |
| |
| | |
Also reflect anything in ABI flags into pkg-config Libs field.
GH #863
|
|\ \
| |/
|/| |
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
Failed to consider need for ISA flags (none required on x86-64 or
aarch64 which are my primary test targets) but handling this correctly
requires splitting up speed.cpp which requires a lot more refactoring
work than I want to take on. Anyway the additional complexity just for
this microbenchmark is not worth it so hide it behind a macro check.
Also add an ECC scalar perf test.
|
|
|
|
| |
Tests both short and full size exponents
|
|
|
|
| |
Add SIMD perf test
|
|
|
|
| |
Equivalent to an 8 byte all-zero IV, same handling as Salsa.
|
|\
| |
| |
| | |
OS::get_high_resolution_clock
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now let it return 0 if we have no hardware timestamp, and add
OS::get_high_resolution_clock for best available clock.
This is mainly because it's confusing for get_processor_timestamp to return
something that is not a processor timestamp and because it simplifies adding
cycles/byte output if we know that something is or is not a cycle counter.
Also adds Windows SEH version of run_cpu_instruction_probe. Untested, uncompiled.
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | | |
Different intrinsics API
|
| | |
| | |
| | |
| | | |
configure.py already supports this arch-specific ISA flag syntax.
|
| | | |
|
| | |
| | |
| | |
| | | |
Return NEON from CPUID::has_simd_32
|
|/ /
| |
| |
| | |
Tested on qemu-aarch64
|
| |
| |
| |
| |
| |
| | |
It was bogus and so potentially confusing
[ci skip]
|
| |
| |
| |
| | |
[ci skip]
|
| | |
|
|/
|
|
| |
Sun CC for whatever reason becomes very confused by this.
|
|
|
|
|
|
|
| |
This inhibits default creation of C++11 move operators which we
do not want.
GH #849
|
|
|
|
|
|
| |
If all (say) stream ciphers are disabled, avoid unused arg warning.
[ci skip]
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Fixes #767 and #19
Main purpose is to support external libs like OpenSSL on Windows.
|
|\ \ |
|
| |/ |
|
|/
|
|
|
|
| |
Values take from the NESSIE submission package.
[ci skip]
|
|
|
|
| |
It assumed if ECC was included then ECDH and ECDSA was also
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on build output sent by @noloader.
If RLIMIT_MEMLOCK is not defined, assume regular user is not able to
call mlock. This probably also affected Clang/GCC on Solaris.
Work around resolution issue in SIMD_4x32 where it finds ambiguity
between arg taking uint32_t and __m128i. This is probably some
artifact of how SunCC represents vector types, and seems highly bogus
in general but is easy to work around here. Change constructor taking
a single value to instead be `SIMD_4x32::splat` function. The SIMD
class is internal, so no API implications.
Fix various warnings about lambda functions that were missing return
types and which were not a single return statement. AIUI C++11 doesn't
guarantee that lambda return type will be deduced in that situation,
though in practice every compiler including SunCC seems to handle it.
Disable AVX2 usage, since SunCC's intrinsics seem to be broken - its
_mm_loadu_si256 takes non-const pointer.
Rename a few variables in the tests to avoid shadowed var warnings.
|
|
|
|
| |
Where referenced in CI scripts, docs and such
|
|
|
|
|
|
|
| |
Makes it easier to support side by side installs. And for the programmer
it is easier if `import botan2` can always be used to refer to a specific version.
GH #847
|
|
|
|
| |
Install anything found in the python dir instead of assuming botan.py
|
|
|
|
| |
[ci skip]
|
|
|
|
|
|
| |
Doesn't seem to be a problem with the asm, code works fine on physical
hardware (POWER8) but on qemu (on CI) both instructions return zero
and the test fails.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Seen with rarely tested compilers (Sun Studio, Intel, ...) that we are missing
info for. Previously this led to a hard error which is pointless. Instead just
disable the relevant module and warn the user that something was disabled, if
they want to go look into why.
Remove bogus clmul entry in x86_64 - actually we lump both AES and CLMUL flags
under the same ISA ("aesni") since all known CPUs support either both or
neither. Caught by new configure warning.
Add Sun Studio ISA flags from GH #846
|
| |
|
|
|
|
| |
Instead just let the individual tests that need the RNG fail.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Deprecates CPUID::print, mainly to avoid use of ostream in utils.
Main reasoning is some platforms do not have streams at all. If all uses of
streams are for operator<< and operator>> overloads, these can be guarded by a
future BOTAN_HAS_CPP_STREAMS system-feature flag. But when ostreams are
required to use the API (as here), that is not possible.
|
|
|
|
|
| |
Mainly driven by missing test for OS::run_cpu_instruction_probe.
Currently only works on x86 and ARM. Tested on x86-64 native and aarch64 qemu.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of refering to security.rst for how to report a security bug,
just say so in the readme.
Mention the botan-announce list.
Drop mention of gitter.im as place for reporting issues, it is not
good for that. GitHub issues and mailing list are both part of our
infrastructure and have a large audience, gitter.im is kind of
peripheral and not monitored so much.
[ci skip]
|