SSH HashKnownHosts File Format
The HashKnownHosts option to the OpenSSH client causes it obfuscate the host field of the ~/.ssh/known_hosts file. Obfuscating this information makes it harder for threat actors (malware, border searches, etc...) to know which hosts you connect to via SSH.Hashing defaults to off, but some platforms turn it on for you:
chris:~$ grep Hash /etc/ssh/ssh_config
HashKnownHosts yes
chris:~$
|1|NWpzcOMkWUFWapbQ2ubC4NTpC9w=|ixkHdS+8OWezxVQvPLOHGi2Oawo= ecdsa-sha2-nistp256 AAAAE2Vj<...>ZHNLpyJsv
There's one record per line, with the fields separated by spaces. The first field is the remote host (SSH server) identifier.
In this case, the leading characters |1| in the host identifier are the magic string (HASH_MAGIC). It tells us that the field is hashed, rather than a plaintext hostname (or address). The remaining characters in the field comprise two parts: a 160-bit salt (random string) and a 160-bit SHA1 hash result. Both values are base64 encoded.
The various OpenSSH binaries that use information in this file feed both the remote hosts name (or address) and the salt to the hashing function in order to produce the hash result:
So, lets validate a host entry against this record the hard way. The entry above is for an IP address: Continue reading

The adapters aim to accelerate software-defined data centers and NFV.
With all of the potential upsides that NFV offers for IT operations, why aren’t enterprises pulling the trigger?
Focus on open source viewed as helping to avoid vendor lock in.
It’s touted as a better way to secure transactions.
This is the EdgeX Foundry's first code release.