Dit artikel biedt een samenvatting van de evolutie van OpenSSH tussen versie 1.2.2p1 en 3.7. De belangrijkste ontwikkelingen zijn onderverdeeld in drie categorieën:
Protocol-evolutie: De overgang van SSHv1 naar SSHv2, waarbij SSHv2 vanaf versie 3.0 de standaard werd.
Beveiligingsarchitectuur: De introductie van Privilege Separation (standaard in v3.3) om de impact van gecompromitteerde daemons te beperken en het implementeren van RSA blinding (v3.6) tegen timing-aanvallen.
Functionaliteiten: Uitbreidingen zoals ondersteuning voor Smartcards, verbeteringen aan de SFTP-client en de toevoeging van SOCKS5-ondersteuning in versie 3.7.
Daarnaast worden kritieke security-fixes belicht, waaronder het oplossen van privilege escalation bugs (v3.0.2 en v3.4) en lekken in KerberosV-authenticatie.
Since you didn't ask a specific question, I have summarized the most significant milestones and security evolutions contained in this text for your convenience.
🚀 Major Milestones & Evolution
1. The Transition to SSH Protocol 2
OpenSSH 2.1.0p1: First stable portable release to incorporate SSH2 protocol support.
OpenSSH 2.9 / 3.0: A critical shift occurred here where SSH protocol v2 became the default version, moving away from the older v1.
OpenSSH 3.0: Obsoleted several knownhosts2 and authorizedkeys2 files in favor of the standard versions (without the '2' suffix).
2. Security Architecture Improvements
Privilege Separation: This was an experimental feature in 3.2, became enabled by default in 3.3, and saw significant portability improvements in 3.5. This is one of OpenSSH's most important security features to mitigate the impact of a compromised daemon.
RSA Blinding: Introduced in 3.6 across ssh, sshd, and ssh-agent to prevent timing attacks against RSA keys.
The "UseLogin" Vulnerability: A major local privilege escalation bug was identified and fixed in version 3.0.2.
3. Feature Additions
Authentication: Added support for Smartcards (3.0) and improved PAM challenge-response modules (3.7).
SFTP Improvements: The sftp client evolved from basic transfers to supporting globbing (get \, put \), progress meters, and quote characters in filenames (3.7).
Network/Proxying: SOCKS5 support was added to dynamic forwarding in 3.7, while SOCKS4 experimental support appeared earlier in 2.9.
SSH-Agent: Added the ability for users to require confirmation before a key is used via ssh-add -c (3.6).
⚠️ Critical Security Fixes Highlighted
If you are reviewing this for legacy system audits, note these specific fixes:
Version 3.4: Fixed an integer overflow and privilege escalation bug affecting versions 2.9.9 through 3.3.
Version 3.0.1: Fixed a security hole regarding KerberosV authentication.
Version 2.9.9: Fixed a weakness in source IP-based access control (from= option) when mixing RSA and DSA keys.
Summary Table: Version Highlights
Version
Key Theme
Notable Change
3.7
Modernization
SOCKS5 support; Sftp filename quote support.
3.6
Hardening
RSA blinding to stop timing attacks.
3.3
Security Defaults
Privilege Separation enabled by default.
3.0
Protocol Shift
SSHv2 becomes the default protocol.
2.9.9
Access Control
Fixed from= IP restriction bypass.
2.1.0p1
Foundations
First stable release with SSH2 support.
1.2.2p1
Origins
First stable Unix port of OpenSSH.
Would you like me to look for a specific bug fix, find the checksum for a certain version, or explain one of the technical changes mentioned in these notes?
You have provided a comprehensive historical archive of OpenSSH release notes, covering versions from 1.2.2p1 (March 2000) up to 3.7.
Since you didn't ask a specific question, I have summarized the most significant milestones and security evolutions contained in this text for your convenience.
🚀 Major Milestones & Evolution
1. The Transition to SSH Protocol 2
OpenSSH 2.1.0p1: First stable portable release to incorporate SSH2 protocol support.
OpenSSH 2.9 / 3.0: A critical shift occurred here where SSH protocol v2 became the default version, moving away from the older v1.
OpenSSH 3.0: Obsoleted several knownhosts2 and authorizedkeys2 files in favor of the standard versions (without the '2' suffix).
2. Security Architecture Improvements
Privilege Separation: This was an experimental feature in 3.2, became enabled by default in 3.3, and saw significant portability improvements in 3.5. This is one of OpenSSH's most important security features to mitigate the impact of a compromised daemon.
RSA Blinding: Introduced in 3.6 across ssh, sshd, and ssh-agent to prevent timing attacks against RSA keys.
The "UseLogin" Vulnerability: A major local privilege escalation bug was identified and fixed in version 3.0.2.
3. Feature Additions
Authentication: Added support for Smartcards (3.0) and improved PAM challenge-response modules (3.7).
SFTP Improvements: The sftp client evolved from basic transfers to supporting globbing (get \, put \), progress meters, and quote characters in filenames (3.7).
Network/Proxying: SOCKS5 support was added to dynamic forwarding in 3.7, while SOCKS4 experimental support appeared earlier in 2.9.
SSH-Agent: Added the ability for users to require confirmation before a key is used via ssh-add -c (3.6).
⚠️ Critical Security Fixes Highlighted
If you are reviewing this for legacy system audits, note these specific fixes:
Version 3.4: Fixed an integer overflow and privilege escalation bug affecting versions 2.9.9 through 3.3.
Version 3.0.1: Fixed a security hole regarding KerberosV authentication.
Version 2.9.9: Fixed a weakness in source IP-based access control (from= option) when mixing RSA and DSA keys.
Summary Table: Version Highlights
Version
Key Theme
Notable Change
3.7
Modernization
SOCKS5 support; Sftp filename quote support.
3.6
Hardening
RSA blinding to stop timing attacks.
3.3
Security Defaults
Privilege Separation enabled by default.
3.0
Protocol Shift
SSHv2 becomes the default protocol.
2.9.9
Access Control
Fixed from= IP restriction bypass.
2.1.0p1
Foundations
First stable release with SSH2 support.
1.2.2p1
Origins
First stable Unix port of OpenSSH.
Would you like me to look for a specific bug fix, find the checksum for a certain version, or explain one of the technical changes mentioned in these notes?
Zichtbare categorieën
Kies welke categorieën je wilt zien.
Over deze site
Waarom Tech-update?
Tech-update is ontstaan omdat ik merkte dat ik dagelijks veel verschillende websites moest bezoeken om interessant technieuws te vinden. Dat kon efficiënter.
Hoe werkt het?
Meerdere keren per etmaal gaat mijn zelfgebouwde AI-agent op zoek naar interessante artikelen op blogs en nieuwssites.
Vindt hij iets relevants, dan wordt het artikel naar het Nederlands vertaald en op Tech-Update geplaatst.
Van ieder artikel maakt de AI ook een korte samenvatting. Zo kun je snel bepalen of het de moeite waard is om het volledige artikel te lezen.
Bij ieder artikel staat altijd een link naar de oorspronkelijke bron (vaak een Engelstalige website).
Artikelen kun je bewaren als favoriet, vastzetten in de zijbalk of terugvinden via de zoekfunctie.
In de instellingen (tandwielikoon rechtsboven) geef je aan in welk soort nieuws je geïnteresseert bent.