| Summary: | Can't add ED25519 keys with `ssh-add` | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Augier <christophe> |
| Component: | RPM Packages | Assignee: | Guillaume Rousse <guillomovitch> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | marja11 |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | openssh | CVE: | |
| Status comment: | |||
|
Description
Augier
2015-08-16 10:06:22 CEST
Assigning to maintainer CC:
(none) =>
marja11 You're probably not using openssh implementation of ssh agent (ssh-agent), but another one, such as gnome-keyring. Check $SSH_AUTH_SOCK value, if that's something such as '/run/user/...' instead of '/tmp/...', that's the case. Upstream bug for gnome-keyring here: https://bugzilla.gnome.org/show_bug.cgi?id=641082 for `$SSH_AUTH_SOCK` is not set here. AFAIK, any SSH agent is supposed to set SSH_AGENT_PID and SSH_AUTH_SOCK environment variables. If you don't have any of them, that's another hint you're not using the one provided by openssh project. That's right, my bad, I have reinstalled Mageia a few days ago. SSH agent is not started anymore on boot (dunno why, maybe I should open a bug about it?). I started SSH Agent and ssh-added, all works well. Closing this, then. Thx for help. Closing. Status:
NEW =>
RESOLVED |