[Bug 13067] Password hashing

https://www.w3.org/Bugs/Public/show_bug.cgi?id=13067

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |travil@microsoft.com
         Resolution|---                         |WONTFIX

--- Comment #6 from Travis Leithead [MSFT] <travil@microsoft.com> ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:


   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: No spec change
Rationale:

This is a great idea. In fact there are also lot of other interesting use cases
that one can imagine would be useful (more than just hashing a password input
field). To this end, the Web Crypto Working Group was established to design a
set of APIs for performing strong cryptography inside of the web application
(client). Given support for Web Crypto API in a user agent, one could easily
hookup form field validation callbacks that perform SHA or MD5 hashes of the
password content before it is submitted. 

Given that the Web Crypto WG is much better equipped to spec out the details
and use cases for this technology, I'd rather not add the simple feature to
input[type=password] elements exclusively, and instead support the Web Crypto
API for this and other great scenarios.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 14 February 2013 23:45:49 UTC