Actions
Bug #3742
closed
SSH doesn't answer post-2.2 upgrade
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Operating System
Target version:
-
Start date:
07/06/2014
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2
Affected Architecture:
Description
After upgrade from 2.1.4, on at least 32 bit, SSH is running properly but sends a RST back when attempting to connect to the port it should be using. When restarting it under Status>Services, it fails with:
Jul 6 16:12:57 php: sshd: New alert found: pfSense has started creating your SSH keys. SSH Startup will be delayed. Please note that reloading the filter rules and changes will be delayed until this operation is completed. Jul 6 16:12:58 php: sshd: New alert found: pfSense has completed creating your SSH keys. SSH is now started. Jul 6 16:12:58 sshd[12805]: Received signal 15; terminating. Jul 6 16:12:58 php: sshd: The command '/usr/sbin/sshd' returned exit code '255', the output was 'bad addr or host: <NULL> (hostname nor servname provided, or not known)' Jul 6 16:12:58 php: sshd: New alert found: SSHD failed to start.
The system had SSH keys from prior to the upgrade, it shouldn't have needed to generate new keys.
Updated by Renato Botelho almost 11 years ago
What is the snapshot timestamp? I tested on Sun Jul 06 14:26:03 CDT 2014 and it's ok
About the sshd keys being regenerated, the code checks for all keys and if one of them doesn't exist it re-creates all of them. Since new types were added on 2.2 (ecdsa and ed25519), they are always missing and keys are re-generated. Maybe we should change it to re-create only missing keys.
Updated by Chris Buechler almost 11 years ago
- Status changed from New to Rejected
root cause in #3749
Actions