Comet Cryptographic Support - Revision history

Jim: Added Encrypting Multiple Strings

2010-06-10T01:46:57Z

Added Encrypting Multiple Strings

← Older revision		Revision as of 01:46, 10 June 2010
Line 77:		Line 77:
	! Reset the algorithm back to old default (RC4)		! Reset the algorithm back to old default (RC4)
	ErrResult$ = CryptoSetKeyInfo("", 0, "", "")		ErrResult$ = CryptoSetKeyInfo("", 0, "", "")
		+
		+	==Encrypting Multiple Strings ==
		+	These Algorithms support encrypting multiple strings with the same IV and Key. By generating the IV and Key and calling CryptoSetKeyInfo() once, successive calls to encrypt/decrypt encrypt or decrypt successive strings. Make sure the same order is used for encrypt and decrypt. Note that for Credit card processing, each credit card must have its own IV and Key.

	== Test vectors ==		== Test vectors ==

Jim: minor

2010-06-10T01:35:17Z

minor

← Older revision		Revision as of 01:35, 10 June 2010
Line 77:		Line 77:
	! Reset the algorithm back to old default (RC4)		! Reset the algorithm back to old default (RC4)
	ErrResult$ = CryptoSetKeyInfo("", 0, "", "")		ErrResult$ = CryptoSetKeyInfo("", 0, "", "")
-
-	~~== Links to other pages ==~~
-	~~[http://www.di-mgt.com.au/cryptoCreditcard.html Encrypting credit card numbers in a database]~~

	== Test vectors ==		== Test vectors ==

Jim: added aes test data reference

2010-06-10T01:34:26Z

added aes test data reference

← Older revision		Revision as of 01:34, 10 June 2010
Line 77:		Line 77:
	! Reset the algorithm back to old default (RC4)		! Reset the algorithm back to old default (RC4)
	ErrResult$ = CryptoSetKeyInfo("", 0, "", "")		ErrResult$ = CryptoSetKeyInfo("", 0, "", "")
		+
		+	== Links to other pages ==
		+	[http://www.di-mgt.com.au/cryptoCreditcard.html Encrypting credit card numbers in a database]
		+
		+	== Test vectors ==
		+	Test vectors are a set of known ciphers for a given input and key. [http://csrc.nist.gov/ NIST] distributes the reference AES test vectors as [http://csrc.nist.gov/groups/STM/cavp/documents/aes/KAT_AES.zip AES Known Answer Test (KAT) Vectors (in ZIP format)].
		+
		+	Would anyone care to download these and write a test program?

	== Links to other pages ==		== Links to other pages ==
	[http://www.di-mgt.com.au/cryptoCreditcard.html Encrypting credit card numbers in a database]		[http://www.di-mgt.com.au/cryptoCreditcard.html Encrypting credit card numbers in a database]

Jim: minor

2010-06-09T23:21:36Z

minor

← Older revision		Revision as of 23:21, 9 June 2010
Line 1:		Line 1:
-	~~'''~~ Supported Encryption Algorithms ~~'''~~	+	== Supported Encryption Algorithms ==
	*RC4 - Rivest Cipher 4: [http://en.wikipedia.org/wiki/RC4 Wiki]		*RC4 - Rivest Cipher 4: [http://en.wikipedia.org/wiki/RC4 Wiki]
	*3DES - Triple Data Encryption Standard: [http://en.wikipedia.org/wiki/Triple_DES Wiki]		*3DES - Triple Data Encryption Standard: [http://en.wikipedia.org/wiki/Triple_DES Wiki]
	*AES - Advanced Encryption Standard: [http://en.wikipedia.org/wiki/Advanced_Encryption_Standard Wiki]		*AES - Advanced Encryption Standard: [http://en.wikipedia.org/wiki/Advanced_Encryption_Standard Wiki]

-	~~'''~~Supported Hashing Algorithms~~'''~~	+	== Supported Hashing Algorithms ==
	*SHA1 - Secure Hash Algorithm 1: [http://en.wikipedia.org/wiki/SHA-1 Wiki]		*SHA1 - Secure Hash Algorithm 1: [http://en.wikipedia.org/wiki/SHA-1 Wiki]
	*MD5 - Message Digest 5: [http://en.wikipedia.org/wiki/MD5 Wiki]		*MD5 - Message Digest 5: [http://en.wikipedia.org/wiki/MD5 Wiki]
Line 78:		Line 78:
	ErrResult$ = CryptoSetKeyInfo("", 0, "", "")		ErrResult$ = CryptoSetKeyInfo("", 0, "", "")

-	== Links to other ~~help~~ pages ==	+	== Links to other pages ==
	[http://www.di-mgt.com.au/cryptoCreditcard.html Encrypting credit card numbers in a database]		[http://www.di-mgt.com.au/cryptoCreditcard.html Encrypting credit card numbers in a database]

Jim: minor

2010-06-09T23:15:32Z

minor

← Older revision		Revision as of 23:15, 9 June 2010
Line 1:		Line 1:
-	~~== Comet Cryptographic Support ==~~
	''' Supported Encryption Algorithms '''		''' Supported Encryption Algorithms '''
	*RC4 - Rivest Cipher 4: [http://en.wikipedia.org/wiki/RC4 Wiki]		*RC4 - Rivest Cipher 4: [http://en.wikipedia.org/wiki/RC4 Wiki]

Jim: Crypto moved to Comet Cryptographic Support: better name

2010-06-09T23:14:43Z

Crypto moved to Comet Cryptographic Support: better name

← Older revision

Revision as of 23:14, 9 June 2010

Jim: minor

2010-06-09T22:03:30Z

minor

← Older revision		Revision as of 22:03, 9 June 2010
Line 1:		Line 1:
-	== Supported Encryption Algorithms ==	+	== Comet Cryptographic Support ==
		+	''' Supported Encryption Algorithms '''
	*RC4 - Rivest Cipher 4: [http://en.wikipedia.org/wiki/RC4 Wiki]		*RC4 - Rivest Cipher 4: [http://en.wikipedia.org/wiki/RC4 Wiki]
	*3DES - Triple Data Encryption Standard: [http://en.wikipedia.org/wiki/Triple_DES Wiki]		*3DES - Triple Data Encryption Standard: [http://en.wikipedia.org/wiki/Triple_DES Wiki]
Line 79:		Line 80:

	== Links to other help pages ==		== Links to other help pages ==
-	;[~~[Help~~:~~Contents\|Help contents]~~]	+	[http://www.di-mgt.com.au/cryptoCreditcard.html Encrypting credit card numbers in a database]

Jim: added code example

2010-06-09T21:48:37Z

added code example

← Older revision		Revision as of 21:48, 9 June 2010
Line 1:		Line 1:
-	= ~~Comet Cryptographic Capabilities~~ =	+	== Supported Encryption Algorithms ==
-		+
-	~~'''~~Supported Encryption Algorithms~~'''~~	+
	*RC4 - Rivest Cipher 4: [http://en.wikipedia.org/wiki/RC4 Wiki]		*RC4 - Rivest Cipher 4: [http://en.wikipedia.org/wiki/RC4 Wiki]
	*3DES - Triple Data Encryption Standard: [http://en.wikipedia.org/wiki/Triple_DES Wiki]		*3DES - Triple Data Encryption Standard: [http://en.wikipedia.org/wiki/Triple_DES Wiki]
Line 39:		Line 37:

	== IV - Initialization Vector [http://en.wikipedia.org/wiki/Initialization_vector Wiki] ==		== IV - Initialization Vector [http://en.wikipedia.org/wiki/Initialization_vector Wiki] ==
-	In Comet the AES and 3DES algorithms are implemented using CBC ([http://en.wikipedia.org/wiki/Block_cipher_modes_of_operation#Cipher-block_chaining_.28CBC.29 Cypher Block Chaining]) mode which incorporates feedback from previous cypher operations while encrypting the plaintext. Because at the onset of the encryption there is no feedback information available, it becomes necessary to supply some initial data that can be used to ensure adequate concealment of the initial block of data. To ensure proper concealment of your data a IV or "Initialization Vector" must be supplied to the encryption code. The size of a IV should be the same size as the chosen algorithm's Block Size (8-3DES, 16-AES). This IV value should be unique and must be used for both encrypt and decrypt operations. There is no need to conceal the IV as it cannot be used to learn anything about the key or plaintext and as such it may be stored with the encrypted data. You can use the IB statement [http://wiki.signature.net/index.php/IB_Statements/cryptogeneraterandom CryptoGenerateRandom] to create an IV of any desired length.	+	In Comet the AES and 3DES algorithms are implemented using CBC ([http://en.wikipedia.org/wiki/Block_cipher_modes_of_operation#Cipher-block_chaining_.28CBC.29 Cypher Block Chaining]) mode which incorporates feedback from previous cypher operations while encrypting the plaintext. Because at the onset of the encryption there is no feedback information available, it becomes necessary to supply some initial data that can be used to ensure adequate concealment of the initial block of data. To ensure proper concealment of your data an IV or "Initialization Vector" must be supplied to the encryption code. The size of an IV should be the same size as the chosen algorithm's Block Size (8-3DES, 16-AES). This IV value should be unique and must be used for both encrypt and decrypt operations. There is no need to conceal the IV as it cannot be used to learn anything about the key or plaintext and as such it may be stored with the encrypted data. You can use the IB statement [http://wiki.signature.net/index.php/IB_Statements/cryptogeneraterandom CryptoGenerateRandom] to create an IV of any desired length.
		+
		+	==Cryptographic Keys==
		+	An encryption key (called a "seed" in previous documentation), is a series of (random) bytes used to encrypt the data. 3DES requires 3 keys of 56 bits each. The Crypto API expects all 3 keys to be grouped together in the form of 3 consecutive 8-byte blocks. The parity bit (2**7) of each byte is ignored so the total number of bits used will be 168. For AES, the key length depends on the encryption strength desired.
		+
		+	Keys may be generated in many ways. Comet32 Supplies the CryptoGenerateRandom() function to facilitate key/IV generation. The Key and the IV must be "remembered" somewhere, preferably not with the encrypted data. Credit card processing standards require that a different key be used for each credit card instance.

	== Internet Basic Support ==		== Internet Basic Support ==
-	Cryptography in Comet is accomplished through the use of the below listed IB (Internet Basic) ~~statements~~.	+	Cryptography in Comet is accomplished through the use of the below listed IB (Internet Basic) functions.
	*[http://wiki.signature.net/index.php/IB_Statements/encrypt Encrypt]		*[http://wiki.signature.net/index.php/IB_Statements/encrypt Encrypt]
-	**This ~~statement~~ is used to encrypt a block of data.	+	**This function is used to encrypt a block of data.
	*[http://wiki.signature.net/index.php/IB_Statements/decrypt Decrypt]		*[http://wiki.signature.net/index.php/IB_Statements/decrypt Decrypt]
-	**This ~~statement~~ is used to decrypt a block of data.	+	**This function is used to decrypt a block of data.
	*New - [http://wiki.signature.net/index.php/IB_Statements/cryptosetkeyinfo CryptoSetKeyInfo]		*New - [http://wiki.signature.net/index.php/IB_Statements/cryptosetkeyinfo CryptoSetKeyInfo]
-	**This ~~statement~~ is used to specify the desired algorithm and to supply all of the parameters required for encryption/decryption. Because a Key and IV must be specified at this time, the SEED value normally supplied to the encrypt/decrypt functions is not used and will be ignored.	+	**This function is used to specify the desired algorithm and to supply all of the parameters required for encryption/decryption. Because a Key and IV must be specified at this time, the SEED value normally supplied to the encrypt/decrypt functions is not used and will be ignored.
	*New - [http://wiki.signature.net/index.php/IB_Statements/cryptogeneraterandom CryptoGenerateRandom]		*New - [http://wiki.signature.net/index.php/IB_Statements/cryptogeneraterandom CryptoGenerateRandom]
-	**This ~~statement~~ will generate a binary string of random characters of any length. It can be used for Key and IV generation.	+	**This function will generate a binary string of random characters of any length. It can be used for Key and IV generation.
	*New - [http://wiki.signature.net/index.php/IB_Statements/cryptocreatehash CryptoCreateHash]		*New - [http://wiki.signature.net/index.php/IB_Statements/cryptocreatehash CryptoCreateHash]
-	**This ~~statement~~ will generate a hash of the supplied string as defined by the specified hashing ~~algoritm~~.	+	**This function will generate a hash of the supplied string as defined by the specified hashing algorithm.
		+
		+	== Storing Credit card information ==
		+	The Following code encrypts the info for a credit card.
		+
		+	! Lets do 256 bit AES
		+	KeySize = 256
		+	BlockSize = 16
		+	Key$ = CryptoGenerateRandom(KeySize/8) ! Generate a key
		+	IV$ = CryptoGenerateRandom(BlockSize) ! Generate an IV
		+	! Store the IV and Key somewhere separate from the encrypted data
		+	...
		+	! Pass info to Encryption sub-system
		+	ErrResult$ = CryptoSetKeyInfo('AES', KeySize, Key$, IV$)
		+	If (ErrResult$ NE "+OK")Print "bad call to CryptoSetKeyInfo -- result is:'; ErrResult$
		+	! Get Credit card info into CC$ (the Card Security Code (CSC or CVV), must NOT be stored anywhere on the disk, even encrypted)
		+	CC$ = CCNO$ + CCDate$
		+	E$ = Encrypt(CC$, "")
		+	! Now E$ contains the encrypted credit card info -- Store it somewhere
		+	...
		+	! Reset the algorithm back to old default (RC4)
		+	ErrResult$ = CryptoSetKeyInfo("", 0, "", "")
		+
		+	== Links to other help pages ==
		+	;[[Help:Contents\|Help contents]]

Brian at 00:19, 7 June 2010

2010-06-07T00:19:11Z

← Older revision		Revision as of 00:19, 7 June 2010
Line 48:		Line 48:
	**This statement is used to decrypt a block of data.		**This statement is used to decrypt a block of data.
	*New - [http://wiki.signature.net/index.php/IB_Statements/cryptosetkeyinfo CryptoSetKeyInfo]		*New - [http://wiki.signature.net/index.php/IB_Statements/cryptosetkeyinfo CryptoSetKeyInfo]
-	**This statement is used to ~~identify~~ the desired algorithm and to supply all of the parameters required for encryption/decryption. Because a Key and IV must be specified at this time, the SEED value normally supplied to the encrypt/decrypt functions is not used and will be ignored.	+	**This statement is used to specify the desired algorithm and to supply all of the parameters required for encryption/decryption. Because a Key and IV must be specified at this time, the SEED value normally supplied to the encrypt/decrypt functions is not used and will be ignored.
	*New - [http://wiki.signature.net/index.php/IB_Statements/cryptogeneraterandom CryptoGenerateRandom]		*New - [http://wiki.signature.net/index.php/IB_Statements/cryptogeneraterandom CryptoGenerateRandom]
	**This statement will generate a binary string of random characters of any length. It can be used for Key and IV generation.		**This statement will generate a binary string of random characters of any length. It can be used for Key and IV generation.
	*New - [http://wiki.signature.net/index.php/IB_Statements/cryptocreatehash CryptoCreateHash]		*New - [http://wiki.signature.net/index.php/IB_Statements/cryptocreatehash CryptoCreateHash]
	**This statement will generate a hash of the supplied string as defined by the specified hashing algoritm.		**This statement will generate a hash of the supplied string as defined by the specified hashing algoritm.

Brian at 23:57, 6 June 2010

2010-06-06T23:57:04Z

← Older revision		Revision as of 23:57, 6 June 2010
Line 32:		Line 32:
	*IV Required: Yes		*IV Required: Yes

-	'''SHA-1 - ~~Rivest Cipher 4~~: [http://en.wikipedia.org/wiki/~~RC4~~ Wiki]'''	+	'''SHA1 - Secure Hash Algorithm 1: [http://en.wikipedia.org/wiki/SHA-1 Wiki]'''
		+	*Output: 160 bits (20 bytes)
		+
		+	'''MD5 - Message Digest 5: [http://en.wikipedia.org/wiki/MD5 Wiki]'''
		+	*Output: 128 bits (16 bytes)

	== IV - Initialization Vector [http://en.wikipedia.org/wiki/Initialization_vector Wiki] ==		== IV - Initialization Vector [http://en.wikipedia.org/wiki/Initialization_vector Wiki] ==