non port: security/cryptopp/files/patch-misc.h |
Number of commits found: 5 |
Friday, 16 Sep 2022
|
03:56 Jason E. Hale (jhale)
security/cryptopp: Update to 8.7.0
Drop most of the SIMD logic. The cryptopp Makefile autodetects CPU
features regardless if CPUTYPE is set and it is not possible to disable
specific instruction sets. It is only possible to completely disable
assembly optimizations, which is recommended for package building unless
all consumer machines support the build machine's CPU instruction sets.
Since version 8.1, it is no longer necessary to export
-DCRYPTOPP_DISABLE_ASM to the pkgconfig file. Consumers will now
build without it defined if the SIMD option is disabled. Remove old
workarounds pertaining to this issue.
https://github.com/weidai11/cryptopp/issues/779
Bump PORTREVISION on consumers due to ABI incompatibility.
https://www.cryptopp.com/release870.html
5a19c08 |
Tuesday, 19 Jan 2021
|
04:26 jhale
security/cryptopp: Update to 8.4.0
Bump PORTREVSION on all consumers. ABI-breaking changes were introduced and
recompile of consumers is necessary.
Remove unused cryptopp dependency from devel/xeus. Upstream migrated to OpenSSL
several releases ago. [1]
[1]
https://github.com/jupyter-xeus/xeus/commit/c98c44c174cafcf424f4203dc3c61564118feb3e
Changes: https://www.cryptopp.com/release840.html
|
Friday, 24 Aug 2018
|
17:22 jhale
Update security/cryptopp to 7.0.0
We now install a pkgconfig file which will allow ports to check whether
cryptopp was built with assembly instructions enabled or not. There are
a few functions that will be undefined if built without assembly and
-DCRYPTOPP_DISABLE_ASM needs to be passed to the compiler in that case
to avoid build failures. This is not new, but the pkgconf file should
make it easier to determine if the flag is needed or not.
Fix several ports due to API changes and to use the new pkgconf file
to determine cryptopp location and build flags. Special cases below.
deskutils/cdcat
- Use cryptopp shared library instead of static, detect with pkgconf
devel/xeus
- Fix dependencies and remove header-only libraries from RUN_DEPENDS
- Rework to use the cryptopp pkgconf file
- net/cppzmq CMake files were fixed in r477649, remove hacks for that
as they were seemingly causing devel/xeus-cling to link to cryptopp
unnecessarily
- Remove C++17 code from cryptopp checks for compatibility
devel/xeus-cling
- Fix dependencies
- Remove hacks for previously broken cppzmq CMake files and no longer
needed cryptopp dependency
Changes: https://www.cryptopp.com/#news
PR: 230579 (original patch, not used)
Submitted by: yuri
|
Wednesday, 7 Dec 2016
|
01:00 jhale
- Update security/cryptopp to 5.6.5
- Add LICENSE (BSL)
- Add CPE data
- Remove STATIC option and always install the shared library;
no reason not to.
- Remove GCC option and use USES=compiler framework
- Add FULL_DEBUG option to address CVE-2016-7420 and add a warning if trying
to use it. It will allow the asserts to be enabled which could be a
security risk. The standard DEBUG option is now safe to use.
- Add SIMD option for i386 and amd64 - requires a recent clang or gcc
- Don't install the cryptest binary; it is really only used for regression
testing, so only build it for the TEST_TARGET. It is useless without the
data files anyways.
- Take maintainership
- Bump PORTREVISON on dependent ports due to shared library bump
PR: 215015
Reported by: <fcsk.aim@gmail.com>
MFH: 2016Q4
Security: eab68cff-bc0c-11e6-b2ca-001b3856973b
|
Wednesday, 22 May 2013
|
22:41 delphij
This changeset fixes two issues with crypto++ library:
* patch-misc.h
This fixes a warning triggered by testing an unsigned parameter against
0. The patch solves this by creating a different template for signed
case.
* patch-nbtheory.cpp
This is a workaround for a bug with the current version of libc++ shipped
with FreeBSD 9.x, which causes an infinite loop when generating RSA key,
possibly also other operations.
PR: ports/178827
Submitted by: Michael Gmelin <freebsd grem de>
|
Number of commits found: 5 |