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.

Sign up for GitHub

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

Jump to bottom

Document best practices from security standpoint for OpenScap team #3776

Closed

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

Labels

sssd-bot commented May 2, 2020

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

Created at 2015-07-29 11:50:07 by jhrozek
Closed as Fixed
Assigned to nobody

SSSD team shall work with the OpenScap team on checking if the sssd configuration aligns with best practices.

This ticket is a tracker for that work -- we still might need to see some use-cases first.

Comments

Comment from jhrozek at 2015-07-30 16:25:57

Fields changed

rhbz: => 0

Comment from jhrozek at 2015-07-30 16:34:46

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14 beta

Comment from jhrozek at 2016-02-16 14:09:57

This was already done here: https://fedorahosted.org/sssd/wiki/SecuritySensitiveOptions

resolution: => fixed
status: new => closed

Comment from jhrozek at 2017-02-24 14:41:33

Metadata Update from @jhrozek:

Issue set to the milestone: SSSD 1.14 beta

sssd-bot added the Closed: Fixed label

sssd-bot closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment