bugzilla-daemon at mindrot.org
2021-Apr-13 12:35 UTC
[Bug 3298] New: Conversion of SSH Ed25519 private key associated to a passphrase into PEM format | 'unsupported key type ED25519'
https://bugzilla.mindrot.org/show_bug.cgi?id=3298
Bug ID: 3298
Summary: Conversion of SSH Ed25519 private key associated to a
passphrase into PEM format | 'unsupported key type
ED25519'
Product: Portable OpenSSH
Version: 8.5p1
Hardware: amd64
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: ssh-keygen
Assignee: unassigned-bugs at mindrot.org
Reporter: ricky.tigg at gmail.com
OS: Fedora 34; Component: openssh-8.5p1-2.fc34.x86_64
Failed: conversion of SSH private Ed25519 key associated to a
passphrase into PEM format in order to be compatible for use with
OpenSSL.
Prerequisite: Creation of an SSH Ed25519 key pair ? using 'ssh-keygen'
? associated to a passphrase.
Task: export file to PEM format:
$ ssh-keygen -e -f id_ed25519 -m pem -out id_ed25519.pem
do_convert_to_pem: unsupported key type ED25519
Reference: Patch providing basic support of Ed25519 keys via PKCS#11
tokens: https://github.com/openssh/openssh-portable/pull/230
No mention in manual 'man ssh-keygen' regards non-compatibility of
OpenSSH-specific format ? RFC4716 ? with OpenSSL, i could reasonably
assume that OpenSSL might support it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
bugzilla-daemon at mindrot.org
2021-Apr-30 04:04 UTC
[Bug 3298] Conversion of SSH Ed25519 private key associated to a passphrase into PEM format | 'unsupported key type ED25519'
https://bugzilla.mindrot.org/show_bug.cgi?id=3298
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
CC| |djm at mindrot.org
--- Comment #1 from Damien Miller <djm at mindrot.org> ---
*** This bug has been marked as a duplicate of bug 3195 ***
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
bugzilla-daemon at mindrot.org
2022-Feb-25 02:58 UTC
[Bug 3298] Conversion of SSH Ed25519 private key associated to a passphrase into PEM format | 'unsupported key type ED25519'
https://bugzilla.mindrot.org/show_bug.cgi?id=3298
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #2 from Damien Miller <djm at mindrot.org> ---
closing bugs resolved before openssh-8.9
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
bugzilla-daemon at mindrot.org
2022-Feb-25 09:20 UTC
[Bug 3298] Conversion of SSH Ed25519 private key associated to a passphrase into PEM format | 'unsupported key type ED25519'
https://bugzilla.mindrot.org/show_bug.cgi?id=3298 --- Comment #3 from ricky.tigg at gmail.com --- Sent (chronological order): "marked as a duplicate of bug", "closing bugs resolved before openssh-8.9". I have trouble to extract a coherence of such chronology. Well, the report, whose present report is a duplicate of, is in state open. Both reports were published against Openssh versions older than version 8.9. Therefore how can the present report be closed as resolved as version previous to 8.9, while the other is not. Coherence would lead - either to close the present as duplicate for unique reason, therefore without being associated to a tier reason such as resolved as version previous to version 8.9 - or to close the present as resolved as version previous to version 8.9 for unique reason, therefore without being associated to a tier reason such as duplicate, and closing as well those reports which it is a duplicate of. -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug.