You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Goldstein Lyor (JIRA)" <ji...@apache.org> on 2017/06/25 06:44:02 UTC
[jira] [Resolved] (SSHD-753) SSHD cannot read its keyfile through a
symlink
[ https://issues.apache.org/jira/browse/SSHD-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Goldstein Lyor resolved SSHD-753.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
> SSHD cannot read its keyfile through a symlink
> ----------------------------------------------
>
> Key: SSHD-753
> URL: https://issues.apache.org/jira/browse/SSHD-753
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 1.5.0
> Reporter: Anthony Wood
> Assignee: Goldstein Lyor
> Priority: Minor
> Fix For: 1.6.0
>
>
> In {{AbstractGeneratorHostKeyProvider.loadFromFile()}} the configured {{keyPath}} is checked using {{LinkOption.NOFOLLOW_LINKS}}. If the path is a symlink, the key will be ignored. Perversely, this class then generates and writes out a new key (if overwriteAllowed) writing through the symlink and clobbering the original; on every startup it will ignore its own previous key and do it again.
> Note this is *not* about following or listing symlinks for, e.g., SFTP clients (SSHD-733).
> Since the key path is purely server-side configuration, SSHD should not interfere with deployment details such as whether its private key is behind a symlink.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)