Learn more about these different git repos.
Other Git URLs
After we do #2221 we can further improve the security by not using PAM stack to pass the key between components. Rather use kernel keyring integration. GNOME keyring would call Kernel keyring and kernel keyring will do an up-call to SSSD.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.14 beta rhbz: => 0
Related ticket - #2278 was requested sooner as it's a prerequisity for OTP. Moving up.
milestone: SSSD 1.14 beta => SSSD 1.13 beta
mark: => 1
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
Mass-moving tickets not planned for the 1.13 release to 1.14
milestone: SSSD 1.13 backlog => SSSD 1.14 beta
There is an existing thesis topic proposal for this RFE: https://thesis-managementsystem.rhcloud.com/topic/show/219/gnome-keyring-storage-in-freeipa
keywords: => thesis
Michal, is this part of your thesis?
cc: => mzidek@redhat.com sensitive: => 0
milestone: SSSD 1.14 beta => SSSD 1.14 backlog
Replying to [comment:7 jhrozek]:
No, I do not touch kernel keyring at all.
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1355909 (Red Hat Enterprise Linux 7)
rhbz: 0 => [https://bugzilla.redhat.com/show_bug.cgi?id=1355909 1355909]
Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.
milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)
Metadata Update from @dpal: - Issue set to the milestone: SSSD Future releases (no date set yet)
Bugzilla closed as won't fix
Metadata Update from @thalman: - Custom field design_review reset (from 0) - Custom field mark adjusted to on (was: 1) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None
Metadata Update from @thalman: - Custom field design_review reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue tagged with: Canditate to close
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/3264
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.