Bug 176707
Summary: | Integration with ssh-agent | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Gomes <alexmipego> |
Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | valdis.kletnieks |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-03-06 19:34:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alexandre Gomes
2005-12-30 13:30:16 UTC
Bad idea, security-wise. There's 2 problems here: 1) The user may not *have* an ssh key, or even *want* one. 2) There's very good reasons to have *different* values for the login password and the ssh key passphrase. The right answer here is for the user to add it to their .xsession, or if it's desired behavior for all users, for the site admin to add code to /etc/X11/gdm/PreSession. GDM isn't really the right component for this. You'd have to do it with some sort of new pam module. Feel free to file a feature request against the pam component, though. |