DOMString. This should be set to
is considered vulnerable in most cryptographic applications, but is still considered safe in PBKDF2. However, it's advisable to transition away from it everywhere, so unless you need to use
, don't. Use a different digest algorithm instead.
BufferSource. This should be a random or pseudo-random value of at least 16 bytes. Unlike the input key material passed into
saltdoes not need to be kept secret.
Numberrepresenting the number of times the hash function will be executed in
deriveKey(). This determines how computationally expensive (that is, slow) the
deriveKey()operation will be. In this context, slow is good, since it makes it more expensive for an attacker to run a dictionary attack against the keys. The general guidance here is to use as many iterations as possible, subject to keeping an acceptable level of performance for your application.
See the examples for
Web Cryptography API
The definition of 'SubtleCrypto.Pbkdf2Params' in that specification.
Browsers that support the "PBKDF2" algorithm for the
method will support this type.