Secure Crypto Config
draft-kaimindermann-securecryptoconfig-01

Document Type Expired Internet-Draft (individual)
Authors Kai Mindermann  , Lisa Teis 
Last updated 2021-10-20 (latest revision 2021-04-18)
Stream (None)
Formats
Expired & archived
plain text html xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-kaimindermann-securecryptoconfig-01.txt

Abstract

Choosing secure cryptography algorithms and their corresponding parameters is difficult. Also, current cryptography APIs cannot change their default configuration which renders them inherently insecure. The Secure Crypto Config provides a method that allows cryptography libraries to change the default cryptography algorithms over time and at the same time stay compatible with previous cryptography operations. This is achieved by combining three things standardized by the Secure Crypto Config: (1) A process that is repeated every two years, where a new set of default configurations for standardized cryptography primitives is published in a specific format. (2) A Secure Crypto Config Interface that describes a common API to use cryptography primitives in software (3) using COSE to derive the parameters from output of cryptography primitives, otherwise future changes of the default configuration would change existing applications behavior.

Authors

Kai Mindermann (kai.mindermann@ic-consult.com)
Lisa Teis (lisateis102@gmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)