OpenSSH Portable Release

Normal OpenSSH development produces a very small, secure, and easy to maintain version for the OpenBSD project. The OpenSSH Portability Team takes that pure version and adds portability code so that OpenSSH can run on many other operating systems. (Unfortunately, in particular since OpenSSH does authentication, it runs into a *lot* of differences between Unix operating systems.)

The OpenSSH provided here is designed to run on the following Unix operating systems:

• AIX
• HP-UX
• Irix
• Linux
• NeXT
• SCO
• SNI/Reliant Unix
• Solaris
• Digital Unix/Tru64/OSF
• macOS
• Cygwin
• ... and more are being added all the time.

The portable OpenSSH follows development of the official version, but releases are not synchronized. Portable releases are marked with a 'p' (e.g. 4.0p1). The official OpenBSD source will never use the 'p' suffix, but will instead increment the version number when it hits 'stable spots' in development.

The following files describe the development efforts of the OpenSSH portability development team. The release files are signed with the PGP public key contained in the file RELEASE_KEY.asc on the ftp site. This key is also available through the key server network and has a fingerprint of 7168B983815A5EEF59A4ADFD2A3F414E736060BA.

• Portability ChangeLog
• Installation instructions

Reporting bugs

Bugs in OpenSSH Portable can be reported via the channels described in Problem reports. Note that many operating system vendors modify the OpenSSH that they ship; in those cases you should report problems to those vendors, unless the problem can also be reproduced with an unmodified OpenSSH.

Developers

Bleeding-edge nightly snapshots are available here. Portable OpenSSH's source tree is also available by git:

• git://anongit.mindrot.org/openssh.git (clone only)
• https://anongit.mindrot.org/openssh.git (web and clone)

This repository is provided and maintained by Damien Miller. It is also mirrored at GitHub.

Building

Once checked out, the configure file needs to be created by running autoreconf from the autoconf package (the required version is listed in the INSTALL file). It will also need to be run again if any changes are made to the configure.ac file.

Developers are asked to read and follow these guidelines when submitting code. Patches should be sent in unified diff format.

Download

HTTP

In the HTTP directory you will find tarballs of the current version and diffs against the OpenBSD source. Historical versions are available in the old/ directory.

FTP

In the FTP directory you will find tarballs of the current version, diffs against the OpenBSD source and supporting documentation. Historical versions are available in the old/ directory.

rsync

This is a list of currently known rsync mirrors: