I was hoping that I could quickly ack, from a security review
standpoint, python-bcrypt since I already acked it in bug 1427861.
However, the project has significantly changed since that review. The
bcrypt backend has changed from Openwall's implementation to OpenBSD's
implementation. Test vectors have also changed. I don't think this
package will require a really close look but it is going to require a
closer look than what I had anticipated.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695899

Title:
  [MIR] python-scrypt, python-bcrypt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-bcrypt/+bug/1695899/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to