Hash upgradability - Revision history

Zarutian at 16:49, 10 April 2010

2010-04-10T16:49:31Z

New page

E integers have the operation [[Integer#cryptoHash/0|cryptoHash/0]] which performs a SHA-1 hash on the two's complement representation of the number. This will be an unfortunate permanent choice once SHA-1 is broken.

We should switch to an interface which acknowledges the need for hash algorithm upgrade.

—[[User:Kevin Reid|Kevin Reid]] 17:30, 29 August 2009 (CDT)

==Proposals==

* Simple: rename cryptoHash to sha1Hash. Add other algorithms as desired. --[[User:Kevin Reid|Kevin Reid]] 17:30, 29 August 2009 (CDT)
:Disadvantage of this: Does not allow code to be sensibly generic over hash algorithms without taking an arbitrary verb to call on Integer. --[[User:Kevin Reid|Kevin Reid]] 17:30, 29 August 2009 (CDT)

* Define explicit hash algorithm objects, and provide a standard one which is SHA-1. Also add a provision to ask for the current recommended hash algorithm.
**Simple: Hash function which takes and returns integers, just extracting the current cryptoHash/0 facility. --[[User:Kevin Reid|Kevin Reid]] 18:09, 29 August 2009 (CDT)
**Complex: Also take the opportunity to handle (1) hash large data blocks or streams without turning them into integers first and (2) permit returning an array of octets rather than a big integer as the result, when this is more directly useful. See [[HashAlgorithm]] for a proposed protocol. --[[User:Kevin Reid|Kevin Reid]] 18:09, 29 August 2009 (CDT)
::I support that proposal as it promotes decaupling --[[User:Zarutian|Zarutian]] 11:49, 10 April 2010 (CDT)

==Notes==

Designation of hash algorithms by programs, if part of the solution to this issue, should use some sort of well-defined namespace. See [http://groups.google.com/group/friam/browse_frm/thread/76b2a1dc8e72ae4b/e2014c634b1db4c7?#e2014c634b1db4c7 this friam list thread: Apr 2, 2010] for discussion. David Hopwood's [http://www.users.zetnet.co.uk/hopwood/crypto/scan/ Standard Cryptographic Algorithm Naming] is the right sort of thing, but not being maintained.

[[Category:Unresolved design issues]]

Kevin Reid: /* Proposals */ fix list formatting

2010-04-10T16:47:10Z

Proposals: fix list formatting

←Older revision		Revision as of 16:47, 10 April 2010
Line 11:		Line 11:

	* Define explicit hash algorithm objects, and provide a standard one which is SHA-1. Also add a provision to ask for the current recommended hash algorithm.		* Define explicit hash algorithm objects, and provide a standard one which is SHA-1. Also add a provision to ask for the current recommended hash algorithm.
-
	**Simple: Hash function which takes and returns integers, just extracting the current cryptoHash/0 facility. --[[User:Kevin Reid\|Kevin Reid]] 18:09, 29 August 2009 (CDT)		**Simple: Hash function which takes and returns integers, just extracting the current cryptoHash/0 facility. --[[User:Kevin Reid\|Kevin Reid]] 18:09, 29 August 2009 (CDT)
-
	**Complex: Also take the opportunity to handle (1) hash large data blocks or streams without turning them into integers first and (2) permit returning an array of octets rather than a big integer as the result, when this is more directly useful. See [[HashAlgorithm]] for a proposed protocol. --[[User:Kevin Reid\|Kevin Reid]] 18:09, 29 August 2009 (CDT)		**Complex: Also take the opportunity to handle (1) hash large data blocks or streams without turning them into integers first and (2) permit returning an array of octets rather than a big integer as the result, when this is more directly useful. See [[HashAlgorithm]] for a proposed protocol. --[[User:Kevin Reid\|Kevin Reid]] 18:09, 29 August 2009 (CDT)

Kevin Reid: add notes on designating hash algorithms

2010-04-10T02:09:53Z

add notes on designating hash algorithms

←Older revision		Revision as of 02:09, 10 April 2010
Line 15:		Line 15:

	**Complex: Also take the opportunity to handle (1) hash large data blocks or streams without turning them into integers first and (2) permit returning an array of octets rather than a big integer as the result, when this is more directly useful. See [[HashAlgorithm]] for a proposed protocol. --[[User:Kevin Reid\|Kevin Reid]] 18:09, 29 August 2009 (CDT)		**Complex: Also take the opportunity to handle (1) hash large data blocks or streams without turning them into integers first and (2) permit returning an array of octets rather than a big integer as the result, when this is more directly useful. See [[HashAlgorithm]] for a proposed protocol. --[[User:Kevin Reid\|Kevin Reid]] 18:09, 29 August 2009 (CDT)
		+
		+	==Notes==
		+
		+	Designation of hash algorithms by programs, if part of the solution to this issue, should use some sort of well-defined namespace. See [http://groups.google.com/group/friam/browse_frm/thread/76b2a1dc8e72ae4b/e2014c634b1db4c7?#e2014c634b1db4c7 this friam list thread: Apr 2, 2010] for discussion. David Hopwood's [http://www.users.zetnet.co.uk/hopwood/crypto/scan/ Standard Cryptographic Algorithm Naming] is the right sort of thing, but not being maintained.

	[[Category:Unresolved design issues]]		[[Category:Unresolved design issues]]

Kevin Reid: Proposal #2

2009-08-29T23:09:13Z

Proposal #2

←Older revision		Revision as of 23:09, 29 August 2009
Line 10:		Line 10:
	:Disadvantage of this: Does not allow code to be sensibly generic over hash algorithms without taking an arbitrary verb to call on Integer. --[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)		:Disadvantage of this: Does not allow code to be sensibly generic over hash algorithms without taking an arbitrary verb to call on Integer. --[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)

		+	* Define explicit hash algorithm objects, and provide a standard one which is SHA-1. Also add a provision to ask for the current recommended hash algorithm.
		+
		+	**Simple: Hash function which takes and returns integers, just extracting the current cryptoHash/0 facility. --[[User:Kevin Reid\|Kevin Reid]] 18:09, 29 August 2009 (CDT)
		+
		+	**Complex: Also take the opportunity to handle (1) hash large data blocks or streams without turning them into integers first and (2) permit returning an array of octets rather than a big integer as the result, when this is more directly useful. See [[HashAlgorithm]] for a proposed protocol. --[[User:Kevin Reid\|Kevin Reid]] 18:09, 29 August 2009 (CDT)

	[[Category:Unresolved design issues]]		[[Category:Unresolved design issues]]

Kevin Reid: sigh

2009-08-29T22:44:45Z

sigh

←Older revision		Revision as of 22:44, 29 August 2009
Line 5:		Line 5:
	—[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)		—[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)

-	=={{Proposals}}==	+	==Proposals==

	* Simple: rename cryptoHash to sha1Hash. Add other algorithms as desired. --[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)		* Simple: rename cryptoHash to sha1Hash. Add other algorithms as desired. --[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)

Kevin Reid: typos

2009-08-29T22:44:09Z

typos

←Older revision		Revision as of 22:44, 29 August 2009
Line 10:		Line 10:
	:Disadvantage of this: Does not allow code to be sensibly generic over hash algorithms without taking an arbitrary verb to call on Integer. --[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)		:Disadvantage of this: Does not allow code to be sensibly generic over hash algorithms without taking an arbitrary verb to call on Integer. --[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)

-	[[Category:~~[[Unesolved~~ design issues]]	+
		+	[[Category:Unresolved design issues]]

Kevin Reid at 22:30, 29 August 2009

2009-08-29T22:30:31Z

←Older revision		Revision as of 22:30, 29 August 2009
Line 5:		Line 5:
	—[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)		—[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)

-	==Proposals==	+	=={{Proposals}}==

	* Simple: rename cryptoHash to sha1Hash. Add other algorithms as desired. --[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)		* Simple: rename cryptoHash to sha1Hash. Add other algorithms as desired. --[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)
	:Disadvantage of this: Does not allow code to be sensibly generic over hash algorithms without taking an arbitrary verb to call on Integer. --[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)		:Disadvantage of this: Does not allow code to be sensibly generic over hash algorithms without taking an arbitrary verb to call on Integer. --[[User:Kevin Reid\|Kevin Reid]] 17:30, 29 August 2009 (CDT)

-	* Define explicit hash algorithm objects, and provide a standard one which is SHA-1. Also add a provision to ask for the current recommended hash algorithm.	+	[[Category:[[Unesolved design issues]]
-	**Simple: Hash function which takes and returns integers, just extracting the current cryptoHash/0 facility. --[[~~User~~:~~Kevin Reid\|Kevin Reid]] 18:09, 29 August 2009 (CDT)~~	+
-	**Complex: Also take the opportunity to handle (1) hash large data blocks or streams without turning them into integers first and (2) permit returning an array of octets rather than a big integer as the result, when this is more directly useful. See [[~~HashAlgorithm]] for a proposed protocol. --[[User:Kevin Reid\|Kevin Reid]] 18:09, 29 August 2009 (CDT)~~	+
-	~~::I support that proposal as it promotes decaupling --[[User:Zarutian\|Zarutian]] 11:49, 10 April 2010 (CDT)~~	+
-		+
-	~~==Notes==~~	+
-		+
-	Designation of hash algorithms by programs, if part of the solution to this issue, should use some sort of well-defined namespace. See [http://groups.google.com/group/friam/browse_frm/thread/76b2a1dc8e72ae4b/e2014c634b1db4c7?#e2014c634b1db4c7 this friam list thread: Apr 2, 2010] for discussion. David Hopwood's [http://www.users.zetnet.co.uk/hopwood/crypto/scan/ Standard Cryptographic Algorithm Naming] is the right sort of thing, but not being maintained.	+
-		+
-	~~[[Category:Unresolved~~ design issues]]	+