From: Eric Wong <normalperson@...>
Date: 2018-07-20T08:53:48+00:00
Subject: [ruby-core:88014] Re: [Ruby trunk Feature#14915] Deprecate String#crypt, move implementation to string/crypt

merch-redmine@jeremyevans.net wrote:
> Personally, I think it's best to punt and require the user
> provide implementations for creating a password hash and
> checking the password hash via two callable options (e.g.
> :create_password_hash and :check_password_hash).  That way the
> user can determine which password hash format they want to
> use, and it doesn't tie Webrick to one particular hash
> implementation.  If that is considered acceptable I can work
> on a patch for Webrick that keeps the current default behavior
> with a deprecation warning if the callable options are not
> provided.

Is the worth the effort for you or anybody to work on
such an option (which still requires user education) vs
telling them to use Htdigest, which already exists?

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>