Navigation:
OpenSSH 8.2 freeware
... runs in the background of your GNU/Linux operating system and protects your entire network from intruders and attackers. It is the open source version of the SSH (Secure Shell) specification. ...
| Author | OpenBSD Project |
| Released | 2020-02-25 |
| Filesize | 860 kB |
| Downloads | 276 |
| OS | Linux |
| Installation | Instal And Uninstall |
| Keywords | Secure connection, SSH client, SSH library, SSH, Secure, Network, Connection |
| Users' rating (18 rating) |
OpenSSH Free Download - we do not host any OpenSSH torrent files or links of OpenSSH on rapidshare.com, depositfiles.com, megaupload.com etc. All OpenSSH download links are direct OpenSSH download from publisher site or their selected mirrors.
| 8.2 | Feb 25, 2020 | New Release | FIDO/U2F Support: This release adds support for FIDO/U2F hardware authenticators to OpenSSH. U2F/FIDO are open standards for inexpensive two-factor authentication hardware that are widely used for website authentication. In OpenSSH FIDO devices are supported by new public key types "ecdsa-sk" and "ed25519-sk", along with corresponding certificate types. |
| 8.1 | Oct 9, 2019 | New Release | Security: ssh(1), sshd(8), ssh-add(1), ssh-keygen(1): an exploitable integer overflow bug was found in the private key parsing code for the XMSS key type. This key type is still experimental and support for it is not compiled by default. No user-facing autoconf option exists in portable OpenSSH to enable it. This bug was found by Adam Zabrocki and reported via SecuriTeam's SSD program. ssh(1), sshd(8), ssh-agent(1): add protection for private keys at rest in RAM against speculation and memory side-channel attacks like Spectre, Meltdown and Rambleed. This release encrypts private keys when they are not in use with a symmetric key that is derived from a relatively large "prekey" consisting of random data (currently 16KB). |
| 8.0 | Apr 17, 2019 | New Release | This release contains mitigation for a weakness in the scp(1) tool and protocol (CVE-2019-6111): when copying files from a remote system to a local directory, scp(1) did not verify that the filenames that the server sent matched those requested by the client. This could allow a hostile server to create or clobber unexpected local files with attacker-controlled content. This release adds client-side checking that the filenames sent from the server match the command-line request, The scp protocol is outdated, inflexible and not readily fixed. We recommend the use of more modern protocols like sftp and rsync for file transfer instead. |
