From https://bugzilla.redhat.com/show_bug.cgi?id=1435924, this should reproduce the problem:
1. Generate a ssh key using the keytype ed25519 and enter a password when creating the key:
$ ssh-keygen -t ed25519
2. Log out from your computer and log in again
3. Start a ssh session to a remote host:
$ ssh <email address hidden>
I tried that with bionic, which has seahorse 3.20.0
Comment #88 hints that trusty is affected and also broke, can someone confirm that please? trusty has seahorse 3.10.2-0ubuntu1
According to https:/ /bugs.launchpad .net/ubuntu/ +source/ seahorse/ +bug/1420522 it's fixed in seahorse 3.30, which is present in ubuntu cosmic and later.
From https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1435924, this should reproduce the problem:
1. Generate a ssh key using the keytype ed25519 and enter a password when creating the key:
$ ssh-keygen -t ed25519
2. Log out from your computer and log in again
3. Start a ssh session to a remote host:
$ ssh <email address hidden>
I tried that with bionic, which has seahorse 3.20.0
Comment #88 hints that trusty is affected and also broke, can someone confirm that please? trusty has seahorse 3.10.2-0ubuntu1
Releases older than trusty are EOL by now.