Nathanael Demacon

> I think that sshs should always use `hostname` as the server name/ip and `host` should only be used to name it There are cases when a host doesn't have...

> I did not realize that the `config` file was actually a feature of openSSH Sorry I didn't realized, I would have told you :/ > but I will do...

> ``` > [server-02.domain.tld]:222,[10.11.12.13]:222 ecdsa-sha2-nistp256 > > server-01,server-01.doman.tld,1.2.3.4 ecdsa-sha2-nistp256 > > 5.6.7.8 ssh-rsa > ``` > > > > > > Returns: > > ``` > Host server-02.domain.tld:222 > Hostname...

> I think so, to me it makes sense to treat each line in the `known_hosts` file as a separate host for the `config` file. It should be good in...

We *could* add a custom `Description` field, I don't think that it will mess with ssh tools but it might not be a great idea to add features beyond sshconfig's...

@Plaenkler there is PR #8 but we're stuck with specifications :/

Hi! Have you tried installing OpenSSL ? ```bash dnf --enablerepo=updates-testing install openssl-libs ```

I just realized, what is `https://git.io/JBhDb` ? It's not related to sshs.

I don't believe allowed top-level directives contains anything else than `Host` or `Include`. Are you sure it's a valid configuration ?

It needs to be implemented in [mikkeloscar/sshconfig](https://github.com/mikkeloscar/sshconfig). As things continues it seems more clever to rewrite it entirely as it doesn't support a lot of features.