Search results

Create the page "Projects/Crypto Modularity" on this wiki! See also the search results found.

Page title matches

Projects/Crypto modularity

...Additional directories will be added as part of the adaptation of vendor's crypto-systems (such as NSS, OpenSSL, BSAFE, PKCS#11, etc,) ...nd will provide the implementation dependent cryptographic primitives. The crypto provider should be chosen with a designated flag during configure process.

4 KB (551 words) - 00:12, 16 February 2010

Roadmap

...hensive [[Projects | list of projects]] is also available; some individual projects have links below. * Developer experience (including modularity)

5 KB (580 words) - 18:06, 3 January 2017
Release Meeting Minutes/2009-12-15

...non-extractable keys in PKCS#11, etc. An attacker who gains control of a crypto module could get the module to produce the derived keys by encrypting chose How much modularity to provide for PRNG? Zhanna says our use of AES256 for Yarrow is overkill

2 KB (243 words) - 23:54, 3 January 2011
Release 1.8

== Modularity == * [[Projects/Crypto_modularity|Crypto modularity]]

2 KB (190 words) - 16:48, 3 March 2010
Projects/Encryption performance

This project follows after [[Projects/Crypto modularity]] and intends to improve encryption performance by allowing cached informat ...e functions do not define a new and complete crypto layer; there are other crypto functions which refer to keyblocks, such as krb5_c_prf and krb5_c_string_to

9 KB (1,332 words) - 00:12, 16 February 2010
Release 1.9

* [[Projects/Database Access Layer cleanup | DAL cleanup]] [Greg Hudson] * NSS crypto back end? [Bob Relyea]

2 KB (191 words) - 18:38, 1 November 2010
Roadmap (completed items)

* [[Projects/Remove krb4|Remove krb4]] (1.7) * Crypto modularity (1.8)

3 KB (300 words) - 16:21, 31 August 2015