hash functions and other comments
Alex Shinn
(08 Sep 2015 06:19 UTC)
|
Re: hash functions and other comments
John Cowan
(08 Sep 2015 12:57 UTC)
|
Re: hash functions and other comments
Alex Shinn
(08 Sep 2015 13:32 UTC)
|
Re: hash functions and other comments
John Cowan
(08 Sep 2015 14:59 UTC)
|
Re: hash functions and other comments
Alex Shinn
(09 Sep 2015 04:29 UTC)
|
Re: hash functions and other comments
John Cowan
(09 Sep 2015 13:18 UTC)
|
Re: hash functions and other comments
Alex Shinn
(10 Sep 2015 02:09 UTC)
|
Re: hash functions and other comments
John Cowan
(10 Sep 2015 03:46 UTC)
|
Re: hash functions and other comments
Arthur A. Gleckler
(10 Sep 2015 03:56 UTC)
|
Re: hash functions and other comments
Alex Shinn
(10 Sep 2015 10:05 UTC)
|
Re: hash functions and other comments
Kevin Wortman
(11 Sep 2015 19:01 UTC)
|
Re: hash functions and other comments
John Cowan
(11 Sep 2015 19:51 UTC)
|
Re: hash functions and other comments
Alex Shinn
(12 Sep 2015 06:29 UTC)
|
Re: hash functions and other comments John Cowan (12 Sep 2015 22:16 UTC)
|
Re: hash functions and other comments
Alex Shinn
(15 Sep 2015 03:23 UTC)
|
Re: hash functions and other comments
John Cowan
(15 Sep 2015 11:31 UTC)
|
Re: hash functions and other comments
Alex Shinn
(15 Sep 2015 12:57 UTC)
|
Re: hash functions and other comments
Alex Shinn
(16 Sep 2015 03:01 UTC)
|
Alex Shinn scripsit: > This is minor compared to the fact that the hash functions don't > take salt as an input. Hash collision attacks are well understood > and have been fixed in Perl [1], and care was taken to fix this in > Chicken's internal hash tables as well [2]. It seems irresponsible > to design an API that prevents such security precautions. A possibility would be to have a parameter hash-salt made available to the hash functions. -- John Cowan http://www.ccil.org/~cowan xxxxxx@ccil.org When I wrote it I was more than a little febrile with foodpoisoning from an antique carrot that I foolishly ate out of an illjudged faith in the benignancy of vegetables. --And Rosta