Changes in Makefile

dc2136341be9835e70ba7c6b36904cf3683fd029 - s390/crypto: Enable CONTEXT_ANALYSIS

Mon, 31 Aug 2026 10:38:38 +0200

s390/crypto: Enable CONTEXT_ANALYSISEnable CONTEXT_ANALYSIS since s390's crypto code compiles now withoutwarnings.Reviewed-by: Harald Freudenberger Signed-off-by: Heiko Carstens Signed-off-by: Vasily Gorbik List of files: /linux/arch/s390/crypto/Makefile

aec2f682d47c54ef434b2d440992626d80b1ebdc - Merge tag 'v7.1-p1' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6

Thu, 16 Apr 2026 00:22:26 +0200

Merge tag 'v7.1-p1' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6Pull crypto update from Herbert Xu: "API: - Replace crypto_get_default_rng with crypto_stdrng_get_bytes - Remove simd skcipher support - Allow algorithm types to be disabled when CRYPTO_SELFTESTS is off Algorithms: - Remove CPU-based des/3des acceleration - Add test vectors for authenc(hmac(md5),cbc({aes,des})) and authenc(hmac({md5,sha1,sha224,sha256,sha384,sha512}),rfc3686(ctr(aes))) - Replace spin lock with mutex in jitterentropy Drivers: - Add authenc algorithms to safexcel - Add support for zstd in qat - Add wireless mode support for QAT GEN6 - Add anti-rollback support for QAT GEN6 - Add support for ctr(aes), gcm(aes), and ccm(aes) in dthev2"* tag 'v7.1-p1' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6: (129 commits) crypto: af_alg - use sock_kmemdup in alg_setkey_by_key_serial crypto: vmx - remove CRYPTO_DEV_VMX from Kconfig crypto: omap - convert reqctx buffer to fixed-size array crypto: atmel-sha204a - add Thorsten Blum as maintainer crypto: atmel-ecc - add Thorsten Blum as maintainer crypto: qat - fix IRQ cleanup on 6xxx probe failure crypto: geniv - Remove unused spinlock from struct aead_geniv_ctx crypto: qce - simplify qce_xts_swapiv() crypto: hisilicon - Fix dma_unmap_single() direction crypto: talitos - rename first/last to first_desc/last_desc crypto: talitos - fix SEC1 32k ahash request limitation crypto: jitterentropy - replace long-held spinlock with mutex crypto: hisilicon - remove unused and non-public APIs for qm and sec crypto: hisilicon/qm - drop redundant variable initialization crypto: hisilicon/qm - remove else after return crypto: hisilicon/qm - add const qualifier to info_name in struct qm_cmd_dump_item crypto: hisilicon - fix the format string type error crypto: ccree - fix a memory leak in cc_mac_digest() crypto: qat - add support for zstd crypto: qat - use swab32 macro ... List of files: /linux/arch/s390/crypto/Makefile

622d42ef977adeae3d5a5d0eb893e4aaf1d5330c - crypto: s390 - Remove des and des3_ede code

Thu, 26 Mar 2026 21:12:43 +0100

crypto: s390 - Remove des and des3_ede codeSince DES and Triple DES are obsolete, there is very little point inmaintining architecture-optimized code for them. Remove it.Signed-off-by: Eric Biggers Signed-off-by: Herbert Xu List of files: /linux/arch/s390/crypto/Makefile

efd1d2c8f3c073c43d5616d0c2d698cbe8a3ecde - lib/crypto: s390/ghash: Migrate optimized code into library

Thu, 19 Mar 2026 07:17:14 +0100

lib/crypto: s390/ghash: Migrate optimized code into libraryRemove the "ghash-s390" crypto_shash algorithm, and replace it with animplementation of ghash_blocks_arch() for the GHASH library.This makes the GHASH library be optimized with CPACF. It also greatlyreduces the amount of s390-specific glue code that is needed, and itfixes the issue where this GHASH optimization was disabled by default.Acked-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20260319061723.1140720-14-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux/arch/s390/crypto/Makefile

496df7cd649dcb0437d3dbde5231bd5dcd77d2ec - crypto: s390/sha3 - Remove superseded SHA-3 code

Sun, 26 Oct 2025 06:50:32 +0100

crypto: s390/sha3 - Remove superseded SHA-3 codeThe SHA-3 library now utilizes the same s390 SHA-3 accelerationcapabilities as the arch/s390/crypto/ SHA-3 crypto_shash algorithms.Moreover, crypto/sha3.c now uses the SHA-3 library. The result is thatall SHA-3 APIs are now s390-accelerated without any need for the oldSHA-3 code in arch/s390/crypto/. Remove this superseded code.Also update the s390 defconfig and debug_defconfig files to enableCONFIG_CRYPTO_SHA3 instead of CONFIG_CRYPTO_SHA3_256_S390 andCONFIG_CRYPTO_SHA3_512_S390. This makes it so that the s390-optimizedSHA-3 continues to be built when either of these defconfigs is used.Tested-by: Harald Freudenberger Reviewed-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20251026055032.1413733-16-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux/arch/s390/crypto/Makefile

44a8c96edd0ee9320a1ad87afc7b10f38e55d5ec - Merge tag 'v6.17-p1' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6

Thu, 31 Jul 2025 18:45:28 +0200

Merge tag 'v6.17-p1' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6Pull crypto update from Herbert Xu: "API: - Allow hash drivers without fallbacks (e.g., hardware key) Algorithms: - Add hmac hardware key support (phmac) on s390 - Re-enable sha384 in FIPS mode - Disable sha1 in FIPS mode - Convert zstd to acomp Drivers: - Lower priority of qat skcipher and aead - Convert aspeed to partial block API - Add iMX8QXP support in caam - Add rate limiting support for GEN6 devices in qat - Enable telemetry for GEN6 devices in qat - Implement full backlog mode for hisilicon/sec2"* tag 'v6.17-p1' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6: (116 commits) crypto: keembay - Use min() to simplify ocs_create_linked_list_from_sg() crypto: hisilicon/hpre - fix dma unmap sequence crypto: qat - make adf_dev_autoreset() static crypto: ccp - reduce stack usage in ccp_run_aes_gcm_cmd crypto: qat - refactor ring-related debug functions crypto: qat - fix seq_file position update in adf_ring_next() crypto: qat - fix DMA direction for compression on GEN2 devices crypto: jitter - replace ARRAY_SIZE definition with header include crypto: engine - remove {prepare,unprepare}_crypt_hardware callbacks crypto: engine - remove request batching support crypto: qat - flush misc workqueue during device shutdown crypto: qat - enable rate limiting feature for GEN6 devices crypto: qat - add compression slice count for rate limiting crypto: qat - add get_svc_slice_cnt() in device data structure crypto: qat - add adf_rl_get_num_svc_aes() in rate limiting crypto: qat - relocate service related functions crypto: qat - consolidate service enums crypto: qat - add decompression service for rate limiting crypto: qat - validate service in rate limiting sysfs api crypto: hisilicon/sec2 - implement full backlog mode for sec ... List of files: /linux/arch/s390/crypto/Makefile

377982d5618a7b80bf2ad3eed9aa62691e984d50 - lib/crypto: s390/sha1: Migrate optimized code into library

Sun, 13 Jul 2025 01:23:02 +0200

lib/crypto: s390/sha1: Migrate optimized code into libraryInstead of exposing the s390-optimized SHA-1 code via s390-specificcrypto_shash algorithms, instead just implement the sha1_blocks()library function. This is much simpler, it makes the SHA-1 libraryfunctions be s390-optimized, and it fixes the longstanding issue wherethe s390-optimized SHA-1 code was disabled by default. SHA-1 stillremains available through crypto_shash, but individual architectures nolonger need to handle it.Reviewed-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20250712232329.818226-12-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux/arch/s390/crypto/Makefile

b7b366087e0f1645f867077a14bab617516d0f57 - lib/crypto: s390/sha512: Migrate optimized SHA-512 code to library

Mon, 30 Jun 2025 18:03:16 +0200

lib/crypto: s390/sha512: Migrate optimized SHA-512 code to libraryInstead of exposing the s390-optimized SHA-512 code via s390-specificcrypto_shash algorithms, instead just implement the sha512_blocks()library function. This is much simpler, it makes the SHA-512 (andSHA-384) library functions be s390-optimized, and it fixes thelongstanding issue where the s390-optimized SHA-512 code was disabled bydefault. SHA-512 still remains available through crypto_shash, butindividual architectures no longer need to handle it.Acked-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20250630160320.2888-13-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux/arch/s390/crypto/Makefile

cbbc675506cc4cd93e6f895e7c1f693156f9a95c - crypto: s390 - New s390 specific protected key hash phmac

Tue, 17 Jun 2025 15:44:37 +0200

crypto: s390 - New s390 specific protected key hash phmacAdd support for protected key hmac ("phmac") for s390 arch.With the latest machine generation there is now support forprotected key (that is a key wrapped by a master key storedin firmware) hmac for sha2 (sha224, sha256, sha384 and sha512)for the s390 specific CPACF instruction kmac.This patch adds support via 4 new ahashes registered asphmac(sha224), phmac(sha256), phmac(sha384) and phmac(sha512).Co-developed-by: Holger Dengler Signed-off-by: Harald Freudenberger Reviewed-by: Holger Dengler Signed-off-by: Holger Dengler Signed-off-by: Herbert Xu List of files: /linux/arch/s390/crypto/Makefile

b9eac03edcf83e25cd2c21be18e7733249fd75c1 - crypto: s390/sha256 - implement library instead of shash

Mon, 28 Apr 2025 19:00:33 +0200

crypto: s390/sha256 - implement library instead of shashInstead of providing crypto_shash algorithms for the arch-optimizedSHA-256 code, instead implement the SHA-256 library. This is muchsimpler, it makes the SHA-256 library functions be arch-optimized, andit fixes the longstanding issue where the arch-optimized SHA-256 wasdisabled by default. SHA-256 still remains available throughcrypto_shash, but individual architectures no longer need to handle it.Signed-off-by: Eric Biggers Signed-off-by: Herbert Xu List of files: /linux/arch/s390/crypto/Makefile

3ea91323fe32011092fc75575d9a074ab374d673 - crypto: s390 - move library functions to arch/s390/lib/crypto/

Tue, 22 Apr 2025 17:27:13 +0200

crypto: s390 - move library functions to arch/s390/lib/crypto/Continue disentangling the crypto library functions from the genericcrypto infrastructure by moving the s390 ChaCha library functions into anew directory arch/s390/lib/crypto/ that does not depend on CRYPTO.This mirrors the distinction between crypto/ and lib/crypto/.Acked-by: Heiko Carstens Signed-off-by: Eric Biggers Signed-off-by: Herbert Xu List of files: /linux/arch/s390/crypto/Makefile

008071917dfccffe6637d264e255553af15c99f9 - s390/crc32: expose CRC32 functions through lib

Mon, 02 Dec 2024 02:08:34 +0100

s390/crc32: expose CRC32 functions through libMove the s390 CRC32 assembly code into the lib directory and wire it upto the library interface. This allows it to be used without goingthrough the crypto API. It remains usable via the crypto API too viathe shash algorithms that use the library interface. Thus all thearch-specific "shash" code becomes unnecessary and is removed.Note: to see the diff from arch/s390/crypto/crc32-vx.c toarch/s390/lib/crc32-glue.c, view this commit with 'git show -M10'.Reviewed-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20241202010844.144356-10-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux/arch/s390/crypto/Makefile

c3dcb058b110d07e56cc8129273e1342905b611c - s390/crypto: Add hardware acceleration for HMAC modes

Wed, 07 Aug 2024 18:06:29 +0200

s390/crypto: Add hardware acceleration for HMAC modesAdd new shash exploiting the HMAC hardware accelerations for SHA224,SHA256, SHA384 and SHA512 introduced with message-security assistextension 11.Reviewed-by: Harald Freudenberger Signed-off-by: Holger Dengler Signed-off-by: Vasily Gorbik List of files: /linux/arch/s390/crypto/Makefile

9592eef7c16ec5fb9f36c4d9abe8eeffc2e1d2f3 - random: remove CONFIG_ARCH_RANDOM

Tue, 05 Jul 2022 20:48:41 +0200

random: remove CONFIG_ARCH_RANDOMWhen RDRAND was introduced, there was much discussion on whether itshould be trusted and how the kernel should handle that. Initially, twomechanisms cropped up, CONFIG_ARCH_RANDOM, a compile time switch, and"nordrand", a boot-time switch.Later the thinking evolved. With a properly designed RNG, using RDRANDvalues alone won't harm anything, even if the outputs are malicious.Rather, the issue is whether those values are being *trusted* to be goodor not. And so a new set of options were introduced as the realones that people use -- CONFIG_RANDOM_TRUST_CPU and "random.trust_cpu".With these options, RDRAND is used, but it's not always credited. So inthe worst case, it does nothing, and in the best case, maybe it helps.Along the way, CONFIG_ARCH_RANDOM's meaning got sort of pulled into thecenter and became something certain platforms force-select.The old options don't really help with much, and it's a bit odd to havespecial handling for these instructions when the kernel can deal finewith the existence or untrusted existence or broken existence ornon-existence of that CPU capability.Simplify the situation by removing CONFIG_ARCH_RANDOM and using theordinary asm-generic fallback pattern instead, keeping the two optionsthat are actually used. For now it leaves "nordrand" for now, as theremoval of that will take a different route.Acked-by: Michael Ellerman Acked-by: Catalin Marinas Acked-by: Borislav Petkov Acked-by: Heiko Carstens Acked-by: Greg Kroah-Hartman Signed-off-by: Jason A. Donenfeld List of files: /linux/arch/s390/crypto/Makefile

b087dfab4d3902681550fd1f5ff9c3e942059478 - s390/crypto: add SIMD implementation for ChaCha20

Thu, 04 Nov 2021 15:58:51 +0100

s390/crypto: add SIMD implementation for ChaCha20Add an implementation of the ChaCha20 stream cipher (see e.g. RFC 7539)that makes use of z13's vector instruction set extension.The original implementation is by Andy Polyakov which isadapted for kernel use.Four to six blocks are processed in parallel resulting in a performancegain for inputs >= 256 bytes.chacha20-generic1 operation in 622 cycles (256 bytes)1 operation in 2346 cycles (1024 bytes)chacha20-s3901 operation in 218 cycles (256 bytes)1 operation in 647 cycles (1024 bytes)Cc: Andy Polyakov Reviewed-by: Harald Freudenberger Signed-off-by: Patrick Steuer Signed-off-by: Heiko Carstens List of files: /linux/arch/s390/crypto/Makefile

3c2eb6b76cabb7d90834798d6455f7f3431fc989 - s390/crypto: Support for SHA3 via CPACF (MSA6)

Wed, 14 Aug 2019 14:56:54 +0200

s390/crypto: Support for SHA3 via CPACF (MSA6)This patch introduces sha3 support for s390.- Rework the s390-specific SHA1 and SHA2 related code to provide the basis for SHA3.- Provide two new kernel modules sha3_256_s390 and sha3_512_s390 together with new kernel options.Signed-off-by: Joerg Schmidbauer Reviewed-by: Ingo Franzki Reviewed-by: Harald Freudenberger Signed-off-by: Heiko Carstens List of files: /linux/arch/s390/crypto/Makefile

b24413180f5600bcb3bb70fbed5cf186b60864bd - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 15:07:57 +0100

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux/arch/s390/crypto/Makefile

c4684f98d3453dd07cc7ce67e0e795330eeec9c5 - s390/crypto: fix aes/paes Kconfig dependeny

Thu, 11 May 2017 17:15:54 +0200

s390/crypto: fix aes/paes Kconfig dependenyThe s390_paes and the s390_aes kernel module used just oneconfig symbol CONFIG_CRYPTO_AES. As paes has a dependencyto PKEY and this requires ZCRYPT the aes module also hada dependency to the zcrypt device driver which is not true.Fixed by introducing a new config symbol CONFIG_CRYPTO_PAESwhich has dependencies to PKEY and ZCRYPT. Removed thedependency for the aes module to ZCRYPT.Signed-off-by: Harald Freudenberger Signed-off-by: Martin Schwidefsky List of files: /linux/arch/s390/crypto/Makefile

4c637cd8de43416c1b1eef6113e7aa06abacf18d - s390/crypto: Provide s390 specific arch random functionality.

Fri, 17 Mar 2017 10:46:31 +0100

s390/crypto: Provide s390 specific arch random functionality.This patch introduces s390 specific arch random functionality.There exists a generic kernel API for arch specific randomnumber implementation (see include/linux/random.h). Herecomes the header file and a very small static code partimplementing the arch_random_* API based on the TRNGsubfunction coming with the reworked PRNG instruction.The arch random implementation hooks into the kernelinitialization and checks for availability of the TRNGfunction. In accordance to the arch random API all functionsreturn false if the TRNG is not available. Otherwise the newhigh quality entropy source provides fresh random on eachinvocation.The s390 arch random feature build is controlled viaCONFIG_ARCH_RANDOM. This config option located inarch/s390/Kconfig is enabled by default and appearsas entry "s390 architectural random number generation API"in the submenu "Processor type and features" for s390 builds.Signed-off-by: Harald Freudenberger Signed-off-by: Martin Schwidefsky List of files: /linux/arch/s390/crypto/Makefile

2793784307688a7a72bd322727a2cb11dede875f - s390/crypt: Add protected key AES module

Fri, 04 Nov 2016 11:57:15 +0100

s390/crypt: Add protected key AES moduleThis patch introduces a new in-kernel-crypto blockciphercalled 'paes' which implements AES with protected keys.The paes blockcipher can be used similar to the aesblockcipher but uses secure key material to derive theworking protected key and so offers an encryptionimplementation where never a clear key value is exposedin memory.The paes module is only available for the s390 platformproviding a minimal hardware support of CPACF enabledwith at least MSA level 3. Upon module initializationthese requirements are checked.Includes additional contribution from Harald Freudenberger.Signed-off-by: Martin Schwidefsky List of files: /linux/arch/s390/crypto/Makefile