[Bug 1205508] New: gpg-agent: only supports RSA keys <= 4096 bits - transparently fails loading larger SSH keys
https://bugzilla.suse.com/show_bug.cgi?id=1205508 Bug ID: 1205508 Summary: gpg-agent: only supports RSA keys <= 4096 bits - transparently fails loading larger SSH keys Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: screening-team-bugs@suse.de Reporter: smueller@atsec.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Tumbleweed: current version gpg-agent is used instead of ssh-agent to manage the keys. I.e. ssh-add loads the keys into gpg-agent. Using an RSA key > 4096, the import fails with an error that tells nothing about the issue. I.e. the user usually would think that something is broken. After checking a bit more and trying to manually interact with gpg-agent it returns the note that keys > 4096 bits are not supported by gpg-agent. May I suggest that either the error message is forwarded to the user or that ssh-agent is used in case when gpg-agent returns such an error? Note, ssh-agent can operate with larger RSA keys. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205508 https://bugzilla.suse.com/show_bug.cgi?id=1205508#c1 Pedro Monreal Gonzalez <pmonrealgonzalez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmonrealgonzalez@suse.com --- Comment #1 from Pedro Monreal Gonzalez <pmonrealgonzalez@suse.com> --- There is this fallback idea being discussed upstream atm, see: * https://dev.gnupg.org/T5494 We'll keep an eye upstream. For the time being, I think you can still spawn an ssh-agent for this: $ eval $(ssh-agent) -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com