Public bug reported:
I am using Seahorse to create and setup new secure shell keys to my
servers and other computers. The first five keys are created as
expected. When I attempt to create the 6th key I proceed as follows:
Press the green + sign
Select Secure Shell Key
Enter a description for the key
Click Create and Set Up
Enter my password twice
Enter the Server address and login name
Click Set Up
At this point I receive an error message
Couldn't configure Secure Shell keys on remote computer.
Received disconnect from 192.168.0.112 port 22:2: Too many authentication
failures for ken
packet_write_wait: Connection to 192.168.0.112 port 22: Broken pipe
If I delete one of the 5 keys I have already created I CAN create a key
for this server. The error ALWAYS occurs on the 6th key I attempt to
create. Upon investigation I find that the default number of bad
attempts to connect to an ssh server is 5. If I up this value on the
target server to 6 I CAN create a key for that server in Seahorse.
I suspect that in the process of setting up the new key Seahorse is
trying all available keys to see if one works for the target server and
if not Seahorse will prompt me for my password on the target server.
This issue has been in Seahorse for a LONG time. I believe I submitted a
bug report on CentOS 6 or perhaps Ubuntu 9.10 several years ago. It is
present in the version of Seahorse included with CentOS 7 (Seahorse
3.14.1) as well as the version in Ubuntu Mate 16.04.
Please advise if I can provide any additional information.
Ken
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: seahorse 3.18.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
Uname: Linux 4.4.0-63-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: MATE
Date: Wed Feb 22 06:06:22 2017
InstallationDate: Installed on 2017-01-24 (29 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: seahorse
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: seahorse (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/1666918
Title:
Issue when creating more than 5 ssh keys
Status in seahorse package in Ubuntu:
New
Bug description:
I am using Seahorse to create and setup new secure shell keys to my
servers and other computers. The first five keys are created as
expected. When I attempt to create the 6th key I proceed as follows:
Press the green + sign
Select Secure Shell Key
Enter a description for the key
Click Create and Set Up
Enter my password twice
Enter the Server address and login name
Click Set Up
At this point I receive an error message
Couldn't configure Secure Shell keys on remote computer.
Received disconnect from 192.168.0.112 port 22:2: Too many authentication
failures for ken
packet_write_wait: Connection to 192.168.0.112 port 22: Broken pipe
If I delete one of the 5 keys I have already created I CAN create a
key for this server. The error ALWAYS occurs on the 6th key I attempt
to create. Upon investigation I find that the default number of bad
attempts to connect to an ssh server is 5. If I up this value on the
target server to 6 I CAN create a key for that server in Seahorse.
I suspect that in the process of setting up the new key Seahorse is
trying all available keys to see if one works for the target server
and if not Seahorse will prompt me for my password on the target
server.
This issue has been in Seahorse for a LONG time. I believe I submitted
a bug report on CentOS 6 or perhaps Ubuntu 9.10 several years ago. It
is present in the version of Seahorse included with CentOS 7 (Seahorse
3.14.1) as well as the version in Ubuntu Mate 16.04.
Please advise if I can provide any additional information.
Ken
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: seahorse 3.18.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
Uname: Linux 4.4.0-63-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: MATE
Date: Wed Feb 22 06:06:22 2017
InstallationDate: Installed on 2017-01-24 (29 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: seahorse
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1666918/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
