<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>747ae818 - certs: Add ECDSA signature verification self-test</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#747ae818</link>
        <description>certs: Add ECDSA signature verification self-testCommit c27b2d2012e1 (&quot;crypto: testmgr - allow ecdsa-nist-p256 and -p384in FIPS mode&quot;) enabled support for ECDSA in crypto/testmgr.c. ThePKCS#7 signature verification API builds upon the KCAPI primitives toperform its high-level operations. Therefore, this change in testmgr.calso allows ECDSA to be used by the PKCS#7 signature verification API(in FIPS mode).However, from a FIPS perspective, the PKCS#7 signature verification APIis a distinct &quot;service&quot; from the KCAPI primitives. This is because thePKCS#7 API performs a &quot;full&quot; signature verification, which consists ofboth hashing the data to be verified, and the public key operation.On the other hand, the KCAPI primitive does not perform this hashingstep - it accepts pre-hashed data from the caller and only performs thepublic key operation.For this reason, the ECDSA self-tests in crypto/testmgr.c are notsufficient to cover ECDSA signature verification offered by the PKCS#7API. This is reflected by the self-test already present in this filefor RSA PKCS#1 v1.5 signature verification.The solution is simply to add a second self-test here for ECDSA. P-256with SHA-256 hashing was chosen as those parameters should remainFIPS-approved for the foreseeable future, while keeping the performanceimpact to a minimum. The ECDSA certificate and PKCS#7 signed data wasgenerated using OpenSSL. The input data is identical to the input datafor the existing RSA self-test.Signed-off-by: Joachim Vandersmissen &lt;git@jvdsn.com&gt;Reviewed-by: Jarkko Sakkinen &lt;jarkko@kernel.org&gt;Acked-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;Signed-off-by: Jarkko Sakkinen &lt;jarkko@kernel.org&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Mon, 13 May 2024 04:55:07 +0000</pubDate>
        <dc:creator>Joachim Vandersmissen &lt;git@jvdsn.com&gt;</dc:creator>
    </item>
<item>
        <title>8cd9f234 - certs: Move RSA self-test data to separate file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#8cd9f234</link>
        <description>certs: Move RSA self-test data to separate fileIn preparation of adding new ECDSA self-tests, the existing data forthe RSA self-tests is moved to a separate file. This file is onlycompiled if the new CONFIG_FIPS_SIGNATURE_SELFTEST_RSA configurationoption is set, which ensures that the required dependencies (RSA,SHA-256) are present. Otherwise, the kernel would panic when trying toexecute the self-test.The introduction of this new option, rather than adding thedependencies to the existing CONFIG_FIPS_SIGNATURE_SELFTEST option,allows for additional self-tests to be added for different algorithms.The kernel can then be configured to only execute the self-tests forthose algorithms that are included.Signed-off-by: Joachim Vandersmissen &lt;git@jvdsn.com&gt;Reviewed-by: Jarkko Sakkinen &lt;jarkko@kernel.org&gt;Acked-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;Signed-off-by: Jarkko Sakkinen &lt;jarkko@kernel.org&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Mon, 13 May 2024 04:55:06 +0000</pubDate>
        <dc:creator>Joachim Vandersmissen &lt;git@jvdsn.com&gt;</dc:creator>
    </item>
<item>
        <title>04a93202 - certs: Break circular dependency when selftest is modular</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#04a93202</link>
        <description>certs: Break circular dependency when selftest is modularThe modular build fails because the self-test code depends on pkcs7which in turn depends on x509 which contains the self-test.Split the self-test out into its own module to break the cycle.Fixes: 3cde3174eb91 (&quot;certs: Add FIPS selftests&quot;)Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;Reviewed-by: Jarkko Sakkinen &lt;jarkko@kernel.org&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Mon, 16 Oct 2023 05:21:44 +0000</pubDate>
        <dc:creator>Herbert Xu &lt;herbert@gondor.apana.org.au&gt;</dc:creator>
    </item>
<item>
        <title>3cde3174 - certs: Add FIPS selftests</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#3cde3174</link>
        <description>certs: Add FIPS selftestsAdd some selftests for signature checking when FIPS mode is enabled.  Theseneed to be done before we start actually using the signature checking forthings and must panic the kernel upon failure.Note that the tests must not check the blacklist lest this provide a way toprevent a kernel from booting by installing a hash of a test key in theappropriate UEFI table.Reported-by: Simo Sorce &lt;simo@redhat.com&gt;Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;Reviewed-by: Simo Sorce &lt;simo@redhat.com&gt;Reviewed-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;cc: keyrings@vger.kernel.orgcc: linux-crypto@vger.kernel.orgLink: https://lore.kernel.org/r/165515742832.1554877.2073456606206090838.stgit@warthog.procyon.org.uk/

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Wed, 18 May 2022 16:15:34 +0000</pubDate>
        <dc:creator>David Howells &lt;dhowells@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>60050ffe - certs: Move load_certificate_list() to be with the asymmetric keys code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#60050ffe</link>
        <description>certs: Move load_certificate_list() to be with the asymmetric keys codeMove load_certificate_list(), which loads a series of binary X.509certificates from a blob and inserts them as keys into a keyring, to bewith the asymmetric keys code that it drives.This makes it easier to add FIPS selftest code in which we need to load upa private keyring for the tests to use.Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;Reviewed-by: Simo Sorce &lt;simo@redhat.com&gt;Reviewed-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;cc: keyrings@vger.kernel.orgcc: linux-crypto@vger.kernel.orgLink: https://lore.kernel.org/r/165515742145.1554877.13488098107542537203.stgit@warthog.procyon.org.uk/

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Wed, 18 May 2022 22:48:09 +0000</pubDate>
        <dc:creator>David Howells &lt;dhowells@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>d3cff4a9 - KEYS: remove support for asym_tpm keys</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#d3cff4a9</link>
        <description>KEYS: remove support for asym_tpm keysasym_tpm keys are tied to TPM v1.2, which uses outdated crypto and hasbeen deprecated in favor of TPM v2.0 for over 7 years.  A very quicklook at this code also immediately found some memory safety bugs(https://lore.kernel.org/r/20220113235440.90439-2-ebiggers@kernel.org).Note that this code is reachable by unprivileged users.According to Jarkko (one of the keyrings subsystem maintainers), thiscode has no practical use cases, and he isn&apos;t willing to maintain it(https://lore.kernel.org/r/YfFZPbKkgYJGWu1Q@iki.fi).Therefore, let&apos;s remove it.Note that this feature didn&apos;t have any documentation or tests, so wedon&apos;t need to worry about removing those.Cc: David Howells &lt;dhowells@redhat.com&gt;Cc: Denis Kenzior &lt;denkenz@gmail.com&gt;Cc: James Morris &lt;jmorris@namei.org&gt;Cc: Jarkko Sakkinen &lt;jarkko@kernel.org&gt;Cc: Marcel Holtmann &lt;marcel@holtmann.org&gt;Signed-off-by: Eric Biggers &lt;ebiggers@google.com&gt;Reviewed-by: Jarkko Sakkinen &lt;jarkko@kernel.org&gt;Acked-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;Signed-off-by: Jarkko Sakkinen &lt;jarkko@kernel.org&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Fri, 28 Jan 2022 19:56:55 +0000</pubDate>
        <dc:creator>Eric Biggers &lt;ebiggers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>3093e7c1 - X.509: Fix modular build of public_key_sm2</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#3093e7c1</link>
        <description>X.509: Fix modular build of public_key_sm2The sm2 code was split out of public_key.c in a way that breaksmodular builds.  This patch moves the code back into the same fileas the original motivation was to minimise ifdefs and that hasnothing to do with splitting the code out.Fixes: 215525639631 (&quot;X.509: support OSCCA SM2-with-SM3...&quot;)Reported-by: kernel test robot &lt;lkp@intel.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Wed, 07 Oct 2020 06:05:45 +0000</pubDate>
        <dc:creator>Herbert Xu &lt;herbert@gondor.apana.org.au&gt;</dc:creator>
    </item>
<item>
        <title>21552563 - X.509: support OSCCA SM2-with-SM3 certificate verification</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#21552563</link>
        <description>X.509: support OSCCA SM2-with-SM3 certificate verificationThe digital certificate format based on SM2 crypto algorithm asspecified in GM/T 0015-2012. It was published by State EncryptionManagement Bureau, China.The method of generating Other User Information is defined asZA=H256(ENTLA || IDA || a || b || xG || yG || xA || yA), it alsospecified in https://tools.ietf.org/html/draft-shen-sm2-ecdsa-02.The x509 certificate supports SM2-with-SM3 type certificateverification.  Because certificate verification requires ZAin addition to tbs data, ZA also depends on elliptic curveparameters and public key data, so you need to access tbs in sigand calculate ZA. Finally calculate the digest of thesignature and complete the verification work. The calculationprocess of ZA is declared in specifications GM/T 0009-2012and GM/T 0003.2-2012.Signed-off-by: Tianjia Zhang &lt;tianjia.zhang@linux.alibaba.com&gt;Tested-by: Xufeng Zhang &lt;yunbo.xufeng@linux.alibaba.com&gt;Reviewed-by: Gilad Ben-Yossef &lt;gilad@benyossef.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Sun, 20 Sep 2020 16:21:02 +0000</pubDate>
        <dc:creator>Tianjia Zhang &lt;tianjia.zhang@linux.alibaba.com&gt;</dc:creator>
    </item>
<item>
        <title>d5e72745 - KEYS: Add parser for TPM-based keys [ver #2]</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#d5e72745</link>
        <description>KEYS: Add parser for TPM-based keys [ver #2]For TPM based keys, the only standard seems to be described here:http://david.woodhou.se/draft-woodhouse-cert-best-practice.html#rfc.section.4.4Quote from the relevant section:&quot;Rather, a common form of storage for &quot;wrapped&quot; keys is to encode thebinary TCPA_KEY structure in a single ASN.1 OCTET-STRING, and store theresult in PEM format with the tag &quot;-----BEGIN TSS KEY BLOB-----&quot;. &quot;This patch implements the above behavior.  It is assumed that the PEMencoding is stripped out by userspace and only the raw DER/BER format isprovided.  This is similar to how PKCS7, PKCS8 and X.509 keys arehandled.Signed-off-by: Denis Kenzior &lt;denkenz@gmail.com&gt;Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;Tested-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;Reviewed-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;Signed-off-by: James Morris &lt;james.morris@microsoft.com&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Tue, 09 Oct 2018 16:48:17 +0000</pubDate>
        <dc:creator>Denis Kenzior &lt;denkenz@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>903be6bb - KEYS: asym_tpm: add skeleton for asym_tpm [ver #2]</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#903be6bb</link>
        <description>KEYS: asym_tpm: add skeleton for asym_tpm [ver #2]This patch adds the basic skeleton for the asym_tpm asymmetric keysubtype.Signed-off-by: Denis Kenzior &lt;denkenz@gmail.com&gt;Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;Tested-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;Reviewed-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;Signed-off-by: James Morris &lt;james.morris@microsoft.com&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Tue, 09 Oct 2018 16:48:02 +0000</pubDate>
        <dc:creator>Denis Kenzior &lt;denkenz@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>3c58b236 - KEYS: Implement PKCS#8 RSA Private Key parser [ver #2]</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#3c58b236</link>
        <description>KEYS: Implement PKCS#8 RSA Private Key parser [ver #2]Implement PKCS#8 RSA Private Key format [RFC 5208] parser for theasymmetric key type.  For the moment, this will only support unencryptedDER blobs.  PEM and decryption can be added later.PKCS#8 keys can be loaded like this:	openssl pkcs8 -in private_key.pem -topk8 -nocrypt -outform DER | \	  keyctl padd asymmetric foo @sSigned-off-by: David Howells &lt;dhowells@redhat.com&gt;Tested-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;Reviewed-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;Reviewed-by: Denis Kenzior &lt;denkenz@gmail.com&gt;Tested-by: Denis Kenzior &lt;denkenz@gmail.com&gt;Signed-off-by: James Morris &lt;james.morris@microsoft.com&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Tue, 09 Oct 2018 16:47:46 +0000</pubDate>
        <dc:creator>David Howells &lt;dhowells@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>4fa8bc94 - kbuild: rename *-asn1.[ch] to *.asn1.[ch]</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#4fa8bc94</link>
        <description>kbuild: rename *-asn1.[ch] to *.asn1.[ch]Our convention is to distinguish file types by suffixes with a periodas a separator.*-asn1.[ch] is a different pattern from other generated sources suchas *.lex.c, *.tab.[ch], *.dtb.S, etc.  More confusing, files with&apos;-asn1.[ch]&apos; are generated files, but &apos;_asn1.[ch]&apos; are checked-infiles:  net/netfilter/nf_conntrack_h323_asn1.c  include/linux/netfilter/nf_conntrack_h323_asn1.h  include/linux/sunrpc/gss_asn1.hRename generated files to *.asn1.[ch] for consistency.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Fri, 23 Mar 2018 13:04:37 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>3ca3273e - kbuild: clean up *-asn1.[ch] patterns from top-level Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#3ca3273e</link>
        <description>kbuild: clean up *-asn1.[ch] patterns from top-level MakefileClean up these patterns from the top Makefile to omit &apos;clean-files&apos;in each Makefile.Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Fri, 23 Mar 2018 13:04:36 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#b2441318</link>
        <description>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 &apos;GPL-2.0&apos;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 &amp; 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 &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;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 &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  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&apos;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 &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>cfb664ff - X.509: Move the trust validation code out to its own file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#cfb664ff</link>
        <description>X.509: Move the trust validation code out to its own fileMove the X.509 trust validation code out to its own file so that it can begeneralised.Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Wed, 06 Apr 2016 15:14:26 +0000</pubDate>
        <dc:creator>David Howells &lt;dhowells@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>d43de6c7 - akcipher: Move the RSA DER encoding check to the crypto layer</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#d43de6c7</link>
        <description>akcipher: Move the RSA DER encoding check to the crypto layerMove the RSA EMSA-PKCS1-v1_5 encoding from the asymmetric-key public_keysubtype to the rsa crypto module&apos;s pkcs1pad template.  This means that thepublic_key subtype no longer has any dependencies on public key type.To make this work, the following changes have been made: (1) The rsa pkcs1pad template is now used for RSA keys.  This strips off the     padding and returns just the message hash. (2) In a previous patch, the pkcs1pad template gained an optional second     parameter that, if given, specifies the hash used.  We now give this,     and pkcs1pad checks the encoded message E(M) for the EMSA-PKCS1-v1_5     encoding and verifies that the correct digest OID is present. (3) The crypto driver in crypto/asymmetric_keys/rsa.c is now reduced to     something that doesn&apos;t care about what the encryption actually does     and and has been merged into public_key.c. (4) CONFIG_PUBLIC_KEY_ALGO_RSA is gone.  Module signing must set     CONFIG_CRYPTO_RSA=y instead.Thoughts: (*) Should the encoding style (eg. raw, EMSA-PKCS1-v1_5) also be passed to     the padding template?  Should there be multiple padding templates     registered that share most of the code?Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;Signed-off-by: Tadeusz Struk &lt;tadeusz.struk@intel.com&gt;Acked-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Thu, 03 Mar 2016 21:49:27 +0000</pubDate>
        <dc:creator>David Howells &lt;dhowells@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>db6c43bd - crypto: KEYS: convert public key and digsig asym to the akcipher api</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#db6c43bd</link>
        <description>crypto: KEYS: convert public key and digsig asym to the akcipher apiThis patch converts the module verification code to the new akcipher API.Signed-off-by: Tadeusz Struk &lt;tadeusz.struk@intel.com&gt;Acked-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Tue, 02 Feb 2016 18:08:53 +0000</pubDate>
        <dc:creator>Tadeusz Struk &lt;tadeusz.struk@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>f75516a8 - crypto: keys - Revert &quot;convert public key to akcipher api&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#f75516a8</link>
        <description>crypto: keys - Revert &quot;convert public key to akcipher api&quot;This needs to go through the security tree so I&apos;m reverting thepatches for now.Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Tue, 09 Feb 2016 08:18:01 +0000</pubDate>
        <dc:creator>Herbert Xu &lt;herbert@gondor.apana.org.au&gt;</dc:creator>
    </item>
<item>
        <title>57f96bba - crypto: asymmetric_keys - convert public key and digsig asym to the akcipher api</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#57f96bba</link>
        <description>crypto: asymmetric_keys - convert public key and digsig asym to the akcipher apiThis patch converts the module verification code to the new akcipher API.Signed-off-by: Tadeusz Struk &lt;tadeusz.struk@intel.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Tue, 02 Feb 2016 18:08:53 +0000</pubDate>
        <dc:creator>Tadeusz Struk &lt;tadeusz.struk@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>b92e6570 - X.509: Extract both parts of the AuthorityKeyIdentifier</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/crypto/asymmetric_keys/Makefile#b92e6570</link>
        <description>X.509: Extract both parts of the AuthorityKeyIdentifierExtract both parts of the AuthorityKeyIdentifier, not just the keyIdentifier,as the second part can be used to match X.509 certificates by issuer andserialNumber.Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;Tested-by: Vivek Goyal &lt;vgoyal@redhat.com&gt;

            List of files:
            /linux-6.15/crypto/asymmetric_keys/Makefile</description>
        <pubDate>Mon, 20 Jul 2015 20:16:26 +0000</pubDate>
        <dc:creator>David Howells &lt;dhowells@redhat.com&gt;</dc:creator>
    </item>
</channel>
</rss>
