Talk:Bcrypt: Difference between revisions
→ExpandKey function is weird: new section |
|||
Line 23: | Line 23: | ||
The article lacks a clear statement about how Bcrypt is different from other hashing functions. What parts are essential to its functioning and how it may be used. I.e. something that would speak to the broader audience of people not versed in cryptography, users of cryptography, not cryptographers themselves. An explanation would be especially beneficial because most times I've seen it being used, it was used wrongly. The fact that it uses the hash, previously generated from input to produce the salt when verifying that the hash generated from another input matches the hash generated from the previous input - is very counter-intuitive and deserves special attention IMO. [[Special:Contributions/79.176.130.107|79.176.130.107]] ([[User talk:79.176.130.107|talk]]) 14:02, 9 October 2013 (UTC) |
The article lacks a clear statement about how Bcrypt is different from other hashing functions. What parts are essential to its functioning and how it may be used. I.e. something that would speak to the broader audience of people not versed in cryptography, users of cryptography, not cryptographers themselves. An explanation would be especially beneficial because most times I've seen it being used, it was used wrongly. The fact that it uses the hash, previously generated from input to produce the salt when verifying that the hash generated from another input matches the hash generated from the previous input - is very counter-intuitive and deserves special attention IMO. [[Special:Contributions/79.176.130.107|79.176.130.107]] ([[User talk:79.176.130.107|talk]]) 14:02, 9 October 2013 (UTC) |
||
== ExpandKey function is weird == |
|||
what I can see: it takes an input, does lots of stuff, discards it and returns the input state. |
Revision as of 19:20, 21 January 2014
![]() | This article is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||||||||||||||
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
|
Seriously misleading description, now fixed
This fragment "(.. bcrypt computes..) a hash from a given input as follows: bcrypt(cost, salt, key, input)" suggested that the password is fed in input. But the intend in the original definition, and many implementations, is feeding password in key, with input a constant derived from "OrpheanBeholderScryDoubt" broken as three 64-bit blocks. Now fixed. Fgrieu (talk) 20:27, 26 June 2012 (UTC)
Popular password hashing bcrypt vs later obscure file encryption bcrypt
I bet 99% of people looking for bcrypt think of the password derivation function, not a pretty obscure program using an outdated cipher... JidGom (talk) (2011-03-30T04:58:28)
- We had the same thought on the same day. Right - all the links to bcrypt on wikipedia were about the hash. And the hash is about more than the "crypt (Unix)" program. So I fixed it. ★NealMcB★ (talk) 15:35, 30 March 2011 (UTC)
Cryptographic hash function page
Why isn't this page listed in the Cryptographic hash function page and corresponding template? Dserodio (talk) 20:32, 20 August 2012 (UTC)
- Technically it's not a hash, it's a Key derivation function.
Explain What Bcrypt Does, Not How It Is Implemented
The article lacks a clear statement about how Bcrypt is different from other hashing functions. What parts are essential to its functioning and how it may be used. I.e. something that would speak to the broader audience of people not versed in cryptography, users of cryptography, not cryptographers themselves. An explanation would be especially beneficial because most times I've seen it being used, it was used wrongly. The fact that it uses the hash, previously generated from input to produce the salt when verifying that the hash generated from another input matches the hash generated from the previous input - is very counter-intuitive and deserves special attention IMO. 79.176.130.107 (talk) 14:02, 9 October 2013 (UTC)
ExpandKey function is weird
what I can see: it takes an input, does lots of stuff, discards it and returns the input state.
- Unassessed software articles
- Unknown-importance software articles
- Unassessed software articles of Unknown-importance
- Unassessed Computing articles
- Unknown-importance Computing articles
- All Computing articles
- All Software articles
- Start-Class Cryptography articles
- Mid-importance Cryptography articles
- Start-Class Computer science articles
- Mid-importance Computer science articles
- WikiProject Computer science articles
- WikiProject Cryptography articles