Reviewed: https://review.openstack.org/157990 Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=2990953cd65b7deccfa48b54e4bb4c65480eb25e Submitter: Jenkins Branch: master commit 2990953cd65b7deccfa48b54e4bb4c65480eb25e Author: Brant Knudson <bknudson at us.ibm.com> Date: Fri Feb 20 16:50:08 2015 -0600 Change use of random to random.SystemRandom There's no reason to use random directly unless the code really requires a pseudo-random number generator. This is for security hardening. SecImpact Closes-Bug: 1424089 Change-Id: I2eb0c78af230026de9139363bc05e453d581a700 ** Changed in: keystone Status: In Progress => Fix Committed -- You received this bug notification because you are a member of OpenStack Security Group, which is subscribed to OpenStack. https://bugs.launchpad.net/bugs/1424089 Title: Use SystemRandom rather than random Status in OpenStack Identity (Keystone): Fix Committed Status in OpenStack Security Advisories: Won't Fix Bug description: SystemRandom should be preferred over direct use of random. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1424089/+subscriptions