- From: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
- Date: Wed, 6 Nov 2013 11:40:30 +0000
- To: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
All, What is the expected algorithm ’type' for the prf parameter of the Pbkdf2Params dictionary: 1. A symmetric signing hash function (e.g: prf : {name:“HMAC”, hash: {name=“SHA-1”}} ) 2. A digest function, and we always automatically wrap it with HMAC (prf : {name=“SHA-1”} ) 3. Either a symmetric signing hash function or a digest function. If it is a digest function we automatically wrap it with HMAC Currently everybody uses HMAC, so we could go for option 2 and make it easier for the user of the API and automatically wrap an HMAC around the provided hash function. But what if a vulnerability is detected in HMAC and a hypothetical HMAC2 is recommended instead of the vulnerable HMAC. So we would preferable do option 3 or 1, reading the spec I’m not sure what the expected behaviour is, my guess is option 1, but I’m not sure. Kind regards, Nick ________________________________ Inventive Designers' Email Disclaimer: http://www.inventivedesigners.com/email-disclaimer
Received on Wednesday, 6 November 2013 11:40:59 UTC