Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conduct security audit of the password obfuscation code #1794

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

Conduct security audit of the password obfuscation code #1794

sssd-bot opened this issue May 2, 2020 · 0 comments
Assignees
Labels
Closed: Fixed Issue was closed as fixed.

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/752

  • Created at 2010-12-23 00:49:34 by dpal
  • Closed as Fixed
  • Assigned to jhrozek

Review the password obfuscation code with NSS team and make sure that best practices are followed.

Comments


Comment from sbose at 2011-01-05 11:48:12

I think this should be done better sooner than later to avoid more issues with OpenLDAP using NSS. See https://fedorahosted.org/sssd/ticket/762


Comment from jhrozek at 2011-01-11 14:16:04

During a security audit conducted by a senior NSS developer these enhancements were proposed:
- use PK11_KeyGen() instead of PK11_GenerateRandom() and then use PK11_ExtractKeyValue() followed by PK11_GetKeyData() to get the key data.
- include a warning about password obfuscation not increasing security directly in the source file so that people who would like to use the code see it. The current version only includes a warning in the sssd-ldap manual page only.

owner: somebody => jhrozek


Comment from sgallagh at 2011-01-11 15:24:13

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.5.1


Comment from sgallagh at 2011-01-20 18:26:03

Fixed by fd72f76

resolution: => fixed
status: new => closed
upgrade: => 0


Comment from dpal at 2012-01-19 03:02:53

Fields changed

rhbz: => 0


Comment from dpal at 2017-02-24 14:35:46

Metadata Update from @dpal:

  • Issue assigned to jhrozek
  • Issue set to the milestone: SSSD 1.5.1
@sssd-bot sssd-bot added the Closed: Fixed Issue was closed as fixed. label May 2, 2020
@sssd-bot sssd-bot closed this as completed May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Fixed Issue was closed as fixed.
Projects
None yet
Development

No branches or pull requests

2 participants