Message ID | 20181017124937.38052-1-marko.kovacevic@intel.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 28A6A1B10F; Wed, 17 Oct 2018 14:49:44 +0200 (CEST) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 7709A1B0FF for <dev@dpdk.org>; Wed, 17 Oct 2018 14:49:42 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Oct 2018 05:49:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,392,1534834800"; d="scan'208";a="242043490" Received: from silpixa00399502.ir.intel.com (HELO silpixa00399502.ger.corp.intel.com) ([10.237.223.218]) by orsmga004.jf.intel.com with ESMTP; 17 Oct 2018 05:49:39 -0700 From: Marko Kovacevic <marko.kovacevic@intel.com> To: dev@dpdk.org Cc: roy.fan.zhang@intel.com, akhil.goyal@nxp.com, arkadiuszx.kusztal@intel.com, Marko Kovacevic <marko.kovacevic@intel.com> Date: Wed, 17 Oct 2018 13:49:29 +0100 Message-Id: <20181017124937.38052-1-marko.kovacevic@intel.com> X-Mailer: git-send-email 2.9.5 In-Reply-To: <20181012144501.19562-1-marko.kovacevic@intel.com> References: <20181012144501.19562-1-marko.kovacevic@intel.com> Subject: [dpdk-dev] [PATCH v5 0/8] FIPS validation capability X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> |
Series |
FIPS validation capability
|
|
Message
Kovacevic, Marko
Oct. 17, 2018, 12:49 p.m. UTC
This sample application is made for the purpose so that users of DPDK who wish to get FIPS certification for their platforms, this sample app enables users to parse test vectors that is gotten from NIST and be able to get a generated response file which they can then verify and be sure their system will pass FIPS certification. Marko Kovacevic (8): v5: - Changed patch titles - Added MAINTAINERS File - Removed bus_pci Dependency - Updated documentation - Changed app name v4: - Added Limitation - Changed TDES BLOCK SIZE from 16 -> 8 as DES block size is 64bits (main.c) v3: - Fixed a no-testing bug - Fixed some code style issue v2: - Refactor the code. - Move the code from test to sample applcation examples/cryptodev_fips_validate: add fips validation into examples examples/cryptodev_fips_validate: add aes parser and enablement for test types examples/cryptodev_fips_validate: add hmac parser examples/cryptodev_fips_validate: add TDES parser and enablement for test types examples/cryptodev_fips_validate: add gcm parser examples/cryptodev_fips_validate: add cmac parser and enablement for test types examples/cryptodev_fips_validate: add ccm parser and enablement for test types doc/guides/sample_app_ug: add guides for fips validation MAINTAINERS | 4 + doc/guides/rel_notes/release_18_11.rst | 6 + doc/guides/sample_app_ug/fips_validation.rst | 119 ++ doc/guides/sample_app_ug/index.rst | 1 + examples/cryptodev_fips_validate/Makefile | 75 ++ .../cryptodev_fips_parse_3des.c | 259 +++++ .../cryptodev_fips_parse_aes.c | 188 +++ .../cryptodev_fips_parse_ccm.c | 272 +++++ .../cryptodev_fips_parse_cmac.c | 116 ++ .../cryptodev_fips_parse_gcm.c | 125 ++ .../cryptodev_fips_parse_hmac.c | 105 ++ .../cryptodev_fips_parse_validate.c | 593 ++++++++++ .../cryptodev_fips_validate.h | 234 ++++ examples/cryptodev_fips_validate/main.c | 1221 ++++++++++++++++++++ examples/cryptodev_fips_validate/meson.build | 20 + 15 files changed, 3338 insertions(+) create mode 100644 doc/guides/sample_app_ug/fips_validation.rst create mode 100644 examples/cryptodev_fips_validate/Makefile create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_3des.c create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_aes.c create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_ccm.c create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_cmac.c create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_gcm.c create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_hmac.c create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_validate.c create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_validate.h create mode 100644 examples/cryptodev_fips_validate/main.c create mode 100644 examples/cryptodev_fips_validate/meson.build
Comments
Hi Marko, On 10/17/2018 6:19 PM, Marko Kovacevic wrote: > This sample application is made for the purpose so that users of DPDK > who wish to get FIPS certification for their platforms, this sample app enables > users to parse test vectors that is gotten from NIST and be able to get > a generated response file which they can then verify and be sure their > system will pass FIPS certification. > > > Marko Kovacevic (8): > v5: > - Changed patch titles patch titles are still not correct > - Added MAINTAINERS File > - Removed bus_pci Dependency > - Updated documentation > - Changed app name I do not see app name changed? Also there is mismatch in the file name for doc(.rst file and app name). I can see that in fips_validation.rst, cryptodev_fips_validate_app is used. The app name looks pretty long, I suggested for a shorter name like fips_validation > v4: > - Added Limitation > - Changed TDES BLOCK SIZE from 16 -> 8 > as DES block size is 64bits (main.c) > v3: > - Fixed a no-testing bug > - Fixed some code style issue > > v2: > - Refactor the code. > - Move the code from test to sample applcation > > examples/cryptodev_fips_validate: add fips validation into examples examples/fips_validation: add cryptodev fips compliant application > examples/cryptodev_fips_validate: add aes parser and enablement for > test types should not this be only examples/fips_validation: support AES parsing > examples/cryptodev_fips_validate: add hmac parser examples/fips_validation: support HMAC parsing > examples/cryptodev_fips_validate: add TDES parser and enablement for > test types same for this one -- examples/fips_validation: support TDES parsing > examples/cryptodev_fips_validate: add gcm parser examples/cryptodev_fips_validate: support GCM parsing > examples/cryptodev_fips_validate: add cmac parser and enablement for > test types examples/fips_validation: support CMAC parsing > examples/cryptodev_fips_validate: add ccm parser and enablement for > test types examples/fips_validation: support CCM parsing > doc/guides/sample_app_ug: add guides for fips validation doc: add fips validation application guide > > MAINTAINERS | 4 + MAINTAINERS changes shall be split in 2 patches. for examples/fips_validation add in 1/8 and for rst file 8/8 > doc/guides/rel_notes/release_18_11.rst | 6 + > doc/guides/sample_app_ug/fips_validation.rst | 119 ++ > doc/guides/sample_app_ug/index.rst | 1 + > examples/cryptodev_fips_validate/Makefile | 75 ++ > .../cryptodev_fips_parse_3des.c | 259 +++++ > .../cryptodev_fips_parse_aes.c | 188 +++ > .../cryptodev_fips_parse_ccm.c | 272 +++++ > .../cryptodev_fips_parse_cmac.c | 116 ++ > .../cryptodev_fips_parse_gcm.c | 125 ++ > .../cryptodev_fips_parse_hmac.c | 105 ++ > .../cryptodev_fips_parse_validate.c | 593 ++++++++++ > .../cryptodev_fips_validate.h | 234 ++++ > examples/cryptodev_fips_validate/main.c | 1221 ++++++++++++++++++++ > examples/cryptodev_fips_validate/meson.build | 20 + > 15 files changed, 3338 insertions(+) > create mode 100644 doc/guides/sample_app_ug/fips_validation.rst > create mode 100644 examples/cryptodev_fips_validate/Makefile > create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_3des.c > create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_aes.c > create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_ccm.c > create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_cmac.c > create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_gcm.c > create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_hmac.c > create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_parse_validate.c > create mode 100644 examples/cryptodev_fips_validate/cryptodev_fips_validate.h > create mode 100644 examples/cryptodev_fips_validate/main.c > create mode 100644 examples/cryptodev_fips_validate/meson.build >