Bug 2622 - ThinLinc doesn't work properly if ssh isn't on port 22 (ssh-keyscan fails)
Summary: ThinLinc doesn't work properly if ssh isn't on port 22 (ssh-keyscan fails)
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Agent (show other bugs)
Version: 1.6.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Peter Åstrand
URL:
Keywords:
: 2937 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-17 09:13 CET by Peter Åstrand
Modified: 2022-05-31 12:52 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Peter Åstrand cendio 2008-01-17 09:13:19 CET 
From Issue5674. We have a /vsm/ssh_hostname parameter, that specifies the host to run ssh-keyscan against, but we do not have a /vsm/ssh_port parameter. This means that if SSH is not running on port 22, the host keys cannot be fetched.
Comment 2 Pierre Ossman cendio 2018-09-26 16:26:11 CEST 
*** Bug 2937 has been marked as a duplicate of this bug. ***
Comment 4 Samuel Mannehed cendio 2022-05-31 12:52:05 CEST 
Another thing that we should consider when solving this is that tl-setup's firewall module assumes that the SSH server runs on port 22. The attached patch wouldn't solve that problem.
Note You need to log in before you can comment on or make changes to this bug.