Projects/Crypto modularity - Revision history

TomYu at 04:12, 16 February 2010

2010-02-16T04:12:14Z

Tsitkova at 19:08, 18 December 2009

2009-12-18T19:08:19Z

TomYu: completion

2009-11-30T04:51:52Z

completion

Tsitkova: Updated dir structure and configure flag info.

2009-10-30T19:14:12Z

Updated dir structure and configure flag info.

TomYu: approved

2009-08-05T00:57:04Z

approved

Ghudson: /* Desired Changes */

2009-07-21T20:16:38Z

‎Desired Changes

Ghudson at 15:40, 15 July 2009

2009-07-15T15:40:12Z

Ghudson at 15:38, 15 July 2009

2009-07-15T15:38:17Z

Ghudson at 15:23, 15 July 2009

2009-07-15T15:23:55Z

Tsitkova at 13:34, 19 June 2009

2009-06-19T13:34:54Z

← Older revision		Revision as of 04:12, 16 February 2010
Line 1:		Line 1:
−	{{project-~~completed~~}}	+	{{project-rel\|1.8}}

	== Desired Changes ==		== Desired Changes ==

@@ Line 73: / Line 73: @@
 ===Approvals===
-Greg Hudson, 2008-07-15
+Greg Hudson, 2009-07-15
 ===Discussion===

← Older revision		Revision as of 04:51, 30 November 2009
Line 1:		Line 1:
−	{{project-~~approved~~}}	+	{{project-completed}}

	== Desired Changes ==		== Desired Changes ==

@@ Line 14: / Line 14: @@
 krb - Kerberos specific functionality. Provides front-end into crypto routines.
-Files: checksum, dk, aead, enc_provider, hash_provider, keyhash_provider, nfold, key ops, etype ops, prf, raw, crc32, old [, prng, yarrow]
+Files: checksum, dk, aead, keyhash_provider, nfold, key ops, etype ops, prf, raw, crc32, old , prng, yarrow
 builtin - MIT implementations. Provides back-end of the crypto routines.
-Files: md*, des*, aes, hmac,  sha1, pbkdf2 [, prng, yarrow]
+Files: md*, des*, aes, hmac,  sha1, enc_provider, hash_provider,  pbkdf2
 * Add a new directory to provide a crypto implementation based on OpenSSL or NSS crypto-system. The directory will have the structure similar to builtin.
@@ Line 49: / Line 49: @@
+  }
-* Add new flags to configure to control the use of the desired cryptographic implementation. The lib/crypto make system will be modified to build lib/crypto/krb and lib/crypto/builtin files to construct libk5crypto library in case when builtin cryptography is desired. However, in the cases when the different crypto implementation was chosen, builtin makesystem will direct the build process into the implementation specific directory.
+* Add new flags to configure --with-crypto-impl to control the use of the desired cryptographic implementation. The lib/crypto make system will be modified to build lib/crypto/krb and lib/crypto/builtin files to construct libk5crypto library in case when builtin cryptography is desired. However, in the cases when the different crypto implementation was chosen, builtin makesystem will direct the build process into the implementation specific directory.
 == Tasks/ Milestones ==

← Older revision		Revision as of 00:57, 5 August 2009
Line 1:		Line 1:
−	{{project-~~review\|2008-07-31~~}}	+	{{project-approved}}

	== Desired Changes ==		== Desired Changes ==

@@ Line 3: / Line 3: @@
 == Desired Changes ==
-The objective of this project is to clear the way for the cryptographic implementations from various providers to be used in lieu of MIT Kerberos custom cryptography. The existing crypto directory should be divided into two subdirectories krb and builtin. The first of these folders will be designated for the Kerberos specific functionality, while the second directory will be a place-holder for the generic lower level cryptographic primitives. Additional directories will be added as part of the adaptation of vendor's crypto-systems ( such as NSS, OpenSSL, BSAFE etc)
+The objective of this project is to clear the way for the cryptographic implementations from various providers to be used in lieu of MIT Kerberos custom cryptography. The existing crypto directory should be divided into two subdirectories krb and builtin. The first of these folders will be designated for the Kerberos specific functionality, while the second directory will be a place-holder for the generic lower level cryptographic primitives. Additional directories will be added as part of the adaptation of vendor's crypto-systems (such as NSS, OpenSSL, BSAFE, PKCS#11, etc,)
 == Functional Requirements ==

← Older revision		Revision as of 15:40, 15 July 2009
Line 72:		Line 72:

	===Approvals===		===Approvals===
		+
		+	Greg Hudson, 2008-07-15

	===Discussion===		===Discussion===

← Older revision		Revision as of 15:38, 15 July 2009
Line 62:		Line 62:
	# Use "make check" to ensure krb5 integrity;		# Use "make check" to ensure krb5 integrity;
	# Use existing and new client/server test tools built with mixed crypto implementations.		# Use existing and new client/server test tools built with mixed crypto implementations.
		+
		+	==Review==
		+
		+	This section documents the review of the project according to [[Project policy]].
		+	It is divided into multiple sections. First, approvals should be listed. To list an approval type
		+	:<nowiki>#~~~~</nowiki>
		+	on its own line.
		+	The next section is for summarizing discussion, which should take place on krbdev@mit.edu. Provide links to the archive at http://mailman.mit.edu/pipermail/krbdev/ if appropriate. Blocking objections can be noted with <nowiki>{{project-block}}</nowiki>.
		+
		+	===Approvals===
		+
		+	===Discussion===

@@ Line 1: / Line 1: @@
-{{project-early}}
+{{project-review|2008-07-31}}
 == Desired Changes ==
@@ Line 48: / Line 48: @@
     EVP_DigestFinal_ex(&mdContext->ossl_md5_ctx , mdContext->digest , NULL);
+  }
 * Add new flags to configure to control the use of the desired cryptographic implementation. The lib/crypto make system will be modified to build lib/crypto/krb and lib/crypto/builtin files to construct libk5crypto library in case when builtin cryptography is desired. However, in the cases when the different crypto implementation was chosen, builtin makesystem will direct the build process into the implementation specific directory.

@@ Line 3: / Line 3: @@
 == Desired Changes ==
-The objective of this project is to clear the way for the cryptographic implementations from various providers to be used in lieu of MIT Kerberos custom cryptography. The existing crypto directory should be divided into two subdirectories krb and builtin. The first of these folders will be designated for the Kerberos specific functionality, while the second directory would be a place-holder for the generic lower level cryptographic primitives. Additional directories will be added as part of the adaptation of vendor's crypto-systems ( such as NSS, OpenSSL, BSAFE etc)
+The objective of this project is to clear the way for the cryptographic implementations from various providers to be used in lieu of MIT Kerberos custom cryptography. The existing crypto directory should be divided into two subdirectories krb and builtin. The first of these folders will be designated for the Kerberos specific functionality, while the second directory will be a place-holder for the generic lower level cryptographic primitives. Additional directories will be added as part of the adaptation of vendor's crypto-systems ( such as NSS, OpenSSL, BSAFE etc)
 == Functional Requirements ==
@@ Line 11: / Line 11: @@
 == Design ==
-* Divide crypto library into two directories:
+* Divide crypto directory into two subdirectories:
 krb - Kerberos specific functionality. Provides front-end into crypto routines.
@@ Line 51: / Line 51: @@
 In addition, if back-end refers to keys using opaque handles, as might be needed on a PKCS#11 device, “overload” krb5_keyblock structure by using its member “krb5_octet *contents” as a void ptr to the opaque key handle/structure. To ensure that the existing applications would still work one of the options is to assign a special value to magic that would control how krb5_keyblock->contents is used.
-* Add new flags to configure to control the use of the desired cryptographic implementation. The lib/crypto make system will be modified to build lib/crypto/krb and lib/crypto/builtin directories to construct libk5crypto library in case when builtin cryptography is desired. However, in the cases when the different crypto implementation was chosen, builtin makesystem will direct the build process into the implementation specific directory.
+* Add new flags to configure to control the use of the desired cryptographic implementation. The lib/crypto make system will be modified to build lib/crypto/krb and lib/crypto/builtin files to construct libk5crypto library in case when builtin cryptography is desired. However, in the cases when the different crypto implementation was chosen, builtin makesystem will direct the build process into the implementation specific directory.
 == Tasks/ Milestones ==
-# Split crypto directory into two directories krb and builtin.
+# Split crypto directory into two directories krb and builtin;
-# Makefile changes to handle the new directory lib/crypto structure
+# Makefile changes to handle the new structure of lib/crypto directory;
-# Implement back-end crypto based on OpenSSL or NSS
+# Implement back-end crypto based on OpenSSL or NSS;
-# Develop test cases
+# Develop test cases;
 == Testing Plan ==
-# Use "make check" to ensure krb5 integrity
+# Use "make check" to ensure krb5 integrity;
-# Use existing and new client/server test tools built with mixed crypto implementations;
+# Use existing and new client/server test tools built with mixed crypto implementations.