Re: [kitten] I-D: Best practices for password hashing and storage

[Simon Josefsson <[e-mail]>]

Hi,

Nice work!  Some minor comments:

  1) I consider PLAIN worse than DIGEST/CRAM-MD5.  Maybe it will help
  the reader understand better if you explain the criteria for sorting.

  2) By describing how implementations should handle credentials for
  PLAIN, it encourages continued use of PLAIN.  PLAIN is a bad idea from
  many perspectives.  I believe that it is better to say that if any
  work to improve security is done on a client or server that uses
  PLAIN, it should be to move to SCRAM-SHA-256, not to implement various
  mitigations.  Mitigations prolongs the transition pain and deter focus
  from the process of moving away from PLAIN.

/Simon

"Sam Whited" <[e-mail]> writes:

> Hi all,
>
> I've been working on a document making recommendations for password
> hashing and storage (possibly with a focus on SASL). I was encouraged to
> turn it into an I-D and ask if it was something the KITTEN WG would be
> interested in? If so, what would the process look like going forward?
>
> The initial draft has been uploaded here:
> https://datatracker.ietf.org/doc/draft-whited-kitten-password-storage/
>
> As an I-D the scope of the document is potentially much broader than the
> one I was originally writing, so suggestions for anything else that
> might be useful to include would be welcome. For example, adding a
> section on how to properly tune KDFs for your service might be a good
> future addition.
>
> —Sam