I think it probably needs to be explicitly called PBKDF2 HMAC then?


On Tue, Jan 28, 2014 at 12:24 PM, Paul Kehrer <notifications@github.com>wrote:

> In cryptography/hazmat/backends/interfaces.py:
>
> > @@ -65,3 +65,18 @@ def create_hmac_ctx(self, key, algorithm):
> >          """
> >          Create a HashContext for calculating a message authentication code.
> >          """
> > +
> > +
> > +class PBKDF2Backend(six.with_metaclass(abc.ABCMeta)):
> > +    @abc.abstractmethod
> > +    def pbkdf2_hash_supported(self, algorithm):
> > +        """
> > +        Return True if the hash algorithm is supported for PBKDF2 by this
> > +        backend.
> > +        """
> > +
> > +    @abc.abstractmethod
> > +    def derive_pbkdf2(self, algorithm, length, salt, iterations, key_material):
>
> This is a good point. OpenSSL and CC implement it as PBKDF2 HMAC, but it
> could hypothetically be more flexible. Current code does not handle this,
> so this is an issue.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/pyca/cryptography/pull/520/files#r9237782>
> .
>



-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: 125F 5C67 DFE9 4084