Changes in Makefile

d0b2dbfa - Remove $FreeBSD$: one-line sh pattern

Wed, 16 Aug 2023 17:55:03 +0000

Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/ List of files: /freebsd-14.2/tests/sys/opencrypto/Makefile

7cc42f6d - Do a sweep and remove most WARNS=6 settings

Thu, 01 Oct 2020 01:10:51 +0000

Do a sweep and remove most WARNS=6 settingsRepeating the default WARNS here makes it slightly more difficult toexperiment with default WARNS changes, e.g. if we did something absolutelybananas and introduced a WARNS=7 and wanted to try lifting the default tothat.Drop most of them; there is one in the blake2 kernel module, but I suspectit should be dropped -- the default WARNS in the rest of the build doesn'tcurrently apply to kernel modules, and I haven't put too much thought intowhether it makes sense to make it so. List of files: /freebsd-14.2/tests/sys/opencrypto/Makefile

2a7a4b19 - tests/sys/opencrypto: use python3

Mon, 20 Jul 2020 12:47:15 +0000

tests/sys/opencrypto: use python3python2 will be EOL soonReviewed by: lwhsu, jmgMFC after: 2 weeksSponsored by: AxcientDifferential Revision: https://reviews.freebsd.org/D25682 List of files: /freebsd-14.2/tests/sys/opencrypto/Makefile

16f35864 - Refactor tests/sys/opencrypto/runtests

Fri, 10 May 2019 00:03:32 +0000

Refactor tests/sys/opencrypto/runtests* Convert from plain to TAP for slightly improved introspection when skipping the tests due to requirements not being met.* Test for the net/py-dpkt (origin) package being required when running the tests, instead of relying on a copy of the dpkt.py module from 2014. This enables the tests to work with py3. Subsequently, remove `tests/sys/opencrypto/dpkt.py(c)?` via `make delete-old`.* Parameterize out `python2` as `$PYTHON`.PR: 237403MFC after: 1 week List of files: /freebsd-14.2/tests/sys/opencrypto/Makefile

369ee090 - Specify using Python2, these .py files have not been converted to use Python3

Sat, 20 Apr 2019 07:32:29 +0000

Specify using Python2, these .py files have not been converted to use Python3yet, but the default Python version in ports has been switched to 3.Sponsored by: The FreeBSD Foundation List of files: /freebsd-14.2/tests/sys/opencrypto/Makefile

1e7bbbc5 - Add test cases for Poly1305 from RFC 7539

Fri, 17 Aug 2018 00:32:00 +0000

Add test cases for Poly1305 from RFC 7539 List of files: /freebsd-14.2/tests/sys/opencrypto/Makefile

0e33efe4 - Import Blake2 algorithms (blake2b, blake2s) from libb2

Wed, 21 Mar 2018 16:18:14 +0000

Import Blake2 algorithms (blake2b, blake2s) from libb2The upstream repository is on github BLAKE2/libb2. Files landed insys/contrib/libb2 are the unmodified upstream files, except for onedifference: secure_zero_memory's contents have been replaced withexplicit_bzero() only because the previous implementation broke powerpclink. Preferential use of explicit_bzero() is in progress upstream, soit is anticipated we will be able to drop this diff in the future.sys/crypto/blake2 contains the source files needed to port libb2 to ourbuild system, a wrapped (limited) variant of the algorithm to match the APIof our auth_transform softcrypto abstraction, incorporation into the OpenCrypto Framework (OCF) cryptosoft(4) driver, as well as an x86 SSE/AVXaccelerated OCF driver, blake2(4).Optimized variants of blake2 are compiled for a number of x86 machines(anything from SSE2 to AVX + XOP). On those machines, FPU context will needto be explicitly saved before using blake2(4)-provided algorithms directly.Use via cryptodev / OCF saves FPU state automatically, and use via theauth_transform softcrypto abstraction does not use FPU.The intent of the OCF driver is mostly to enable testing in userspace via/dev/crypto. ATF tests are added with published KAT test vectors tovalidate correctness.Reviewed by: jhb, markjObtained from: github BLAKE2/libb2Differential Revision: https://reviews.freebsd.org/D14662 List of files: /freebsd-14.2/tests/sys/opencrypto/Makefile

1de3fb04 - Fix up `TEST_METADATA`

Thu, 01 Jun 2017 19:46:48 +0000

Fix up `TEST_METADATA`- `TEST_METADATA.foo` should be `TEST_METADATA.run_tests`: this will unbreak trying to run the tests on a system without python installed in $PATH.- The tests require root because they load aesni(4) and/or cryptodev(4) if not already loaded.MFC after: 2 weeksSponsored by: Dell EMC Isilon List of files: /freebsd-14.2/tests/sys/opencrypto/Makefile

430f7286 - Merge ^/user/ngie/release-pkg-fix-tests to unbreak how test files are installed

Wed, 04 May 2016 23:20:53 +0000

Merge ^/user/ngie/release-pkg-fix-tests to unbreak how test files are installedafter r298107Summary of changes:- Replace all instances of FILES/TESTS with ${PACKAGE}FILES. This ensures that namespacing is kept with FILES appropriately, and that this shouldn't need to be repeated if the namespace changes -- only the definition of PACKAGE needs to be changed- Allow PACKAGE to be overridden by callers instead of forcing it to always be `tests`. In the event we get to the point where things can be split up enough in the base system, it would make more sense to group the tests with the blocks they're a part of, e.g. byacc with byacc-tests, etc- Remove PACKAGE definitions where possible, i.e. where FILES wasn't used previously.- Remove unnecessary TESTSPACKAGE definitions; this has been elided into bsd.tests.mk- Remove unnecessary BINDIRs used previously with ${PACKAGE}FILES; ${PACKAGE}FILESDIR is now automatically defined in bsd.test.mk.- Fix installation of files under data/ subdirectories in lib/libc/tests/hash and lib/libc/tests/net/getaddrinfo- Remove unnecessary .include s (some opportunistic cleanup)Document the proposed changes in share/examples/tests/tests/... via examplesso it's clear that ${PACKAGES}FILES is the suggested way forward in terms ofreplacing FILES. share/mk/bsd.README didn't seem like the appropriate methodof communicating that info.MFC after: never probablyX-MFC with: r298107PR: 209114Relnotes: yesTested with: buildworld, installworld, checkworld; buildworld, packageworldSponsored by: EMC / Isilon Storage Division List of files: /freebsd-14.2/tests/sys/opencrypto/Makefile

2aa00a60 - More 'tests' package fixes.

Wed, 03 Feb 2016 00:34:23 +0000

More 'tests' package fixes.Sponsored by: The FreeBSD Foundation List of files: /freebsd-14.2/tests/sys/opencrypto/Makefile

08fca7a5 - Add some new modes to OpenCrypto. These modes are AES-ICM (can be used

Fri, 12 Dec 2014 19:56:36 +0000

Add some new modes to OpenCrypto. These modes are AES-ICM (can be usedfor counter mode), and AES-GCM. Both of these modes have been added tothe aesni module.Included is a set of tests to validate that the software and aesnimodule calculate the correct values. These use the NIST KAT testvectors. To run the test, you will need to install a soon to becommitted port, nist-kat that will install the vectors. Using a portis necessary as the test vectors are around 25MB.All the man pages were updated. I have added a new man page, crypto.7,which includes a description of how to use each mode. All the new modesand some other AES modes are present. It would be good for someoneelse to go through and document the other modes.A new ioctl was added to support AEAD modes which AES-GCM is one of them.Without this ioctl, it is not possible to test AEAD modes from userland.Add a timing safe bcmp for use to compare MACs. Previously we were usingbcmp which could leak timing info and result in the ability to forgemessages.Add a minor optimization to the aesni module so that single segmentmbufs don't get copied and instead are updated in place. The aesnimodule needs to be updated to support blocked IO so segmented mbufsdon't have to be copied.We require that the IV be specified for all calls for both GCM and ICM.This is to ensure proper use of these functions.Obtained from: p4: //depot/projects/opencryptoRelnotes: yesSponsored by: FreeBSD FoundationSponsored by: NetGate List of files: /freebsd-14.2/tests/sys/opencrypto/Makefile