Eric Lee / smarc-fsl-linux-kernel

26 Mar, 2021

2 commits

  • 3877869d1   Merge branch 'ecc' ... Browse Code »

    This pulls in the NIST P384/256/192 x509 changes.

    Herbert Xu
     
  • 703c748d5   crypto: ecc - Add NIST P384 curve parameters ... Browse Code »

    Add the parameters for the NIST P384 curve and define a new curve ID
    for it. Make the curve available in ecc_get_curve.

    Summary of changes:

    * crypto/ecc_curve_defs.h
    - add nist_p384 params

    * include/crypto/ecdh.h
    - add ECC_CURVE_NIST_P384

    * crypto/ecc.c
    - change ecc_get_curve to accept nist_p384

    Signed-off-by: Saulo Alessandre
    Tested-by: Stefan Berger
    Acked-by: Jarkko Sakkinen
    Signed-off-by: Herbert Xu

    Saulo Alessandre
     

12 Mar, 2021

1 commit

  • 8fb9340e1   crypto: ecc - add curve25519 params and expose them ... Browse Code »

    1. Add curve 25519 parameters in 'crypto/ecc_curve_defs.h';
    2. Add curve25519 interface 'ecc_get_curve25519_param' in
    'include/crypto/ecc_curve.h', to make its parameters be
    exposed to everyone in kernel tree.

    Signed-off-by: Meng Yu
    Reviewed-by: Zaibo Xu
    Signed-off-by: Herbert Xu

    Meng Yu
     

18 Apr, 2019

1 commit

  • 4a2289dae   crypto: ecc - make ecc into separate module ... Browse Code »

    ecc.c have algorithms that could be used togeter by ecdh and ecrdsa.
    Make it separate module. Add CRYPTO_ECC into Kconfig. EXPORT_SYMBOL and
    document to what seems appropriate. Move structs ecc_point and ecc_curve
    from ecc_curve_defs.h into ecc.h.

    No code changes.

    Signed-off-by: Vitaly Chikunov
    Signed-off-by: Herbert Xu

    Vitaly Chikunov
     

20 Jul, 2018

1 commit

09 Jul, 2018

1 commit

  • ea169a30a   crypto: ecdh - add public key verification test ... Browse Code »

    According to SP800-56A section 5.6.2.1, the public key to be processed
    for the ECDH operation shall be checked for appropriateness. When the
    public key is considered to be an ephemeral key, the partial validation
    test as defined in SP800-56A section 5.6.2.3.4 can be applied.

    The partial verification test requires the presence of the field
    elements of a and b. For the implemented NIST curves, b is defined in
    FIPS 186-4 appendix D.1.2. The element a is implicitly given with the
    Weierstrass equation given in D.1.2 where a = p - 3.

    Without the test, the NIST ACVP testing fails. After adding this check,
    the NIST ACVP testing passes.

    Signed-off-by: Stephan Mueller
    Signed-off-by: Herbert Xu

    Stephan Mueller
     

02 Nov, 2017

1 commit

  • b24413180   License cleanup: add SPDX GPL-2.0 license identifier to files with no license ... Browse Code »

    Many source files in the tree are missing licensing information, which
    makes it harder for compliance tools to determine the correct license.

    By default all files without license information are under the default
    license 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 binding
    shorthand, which can be used instead of the full boiler plate text.

    This patch is based on work done by Thomas Gleixner and Kate Stewart and
    Philippe Ombredanne.

    How this work was done:

    Patches were generated and checked against linux-4.14-rc6 for a subset of
    the 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 cases
    where non-standard license headers were used, and references to license
    had to be inferred by heuristics based on keywords.

    The analysis to determine which SPDX License Identifier to be applied to
    a file was done in a spreadsheet of side by side results from of the
    output of two independent scanners (ScanCode & Windriver) producing SPDX
    tag:value files created by Philippe Ombredanne. Philippe prepared the
    base 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 files
    assessed. Kate Stewart did a file by file comparison of the scanner
    results in the spreadsheet to determine which SPDX license identifier(s)
    to be applied to the file. She confirmed any determination that was not
    immediately 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
    Reviewed-by: Philippe Ombredanne
    Reviewed-by: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

23 Jun, 2016

1 commit