<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[wolfSSL - Embedded SSL Library — wolfSSH v1.5.0 Release]]></title>
	<link rel="self" href="https://www.wolfssl.com/forums/feed-atom-topic2511.xml" />
	<updated>2026-04-22T17:56:03Z</updated>
	<generator>PunBB</generator>
	<id>https://www.wolfssl.com/forums/topic2511-wolfssh-v150-release.html</id>
		<entry>
			<title type="html"><![CDATA[wolfSSH v1.5.0 Release]]></title>
			<link rel="alternate" href="https://www.wolfssl.com/forums/post8795.html#p8795" />
			<content type="html"><![CDATA[<p><a href="https://www.wolfssl.com/products/wolfssh/">wolfSSH v1.5.0</a> is now available! This release brings additional post-quantum hybrid key exchange algorithms, a broad hardening pass across the code base, and a large number of bug fixes. There is also one low-severity vulnerability fix in this release affecting wolfSSHd on Windows when handling an edge case in terminal resize messages received from an authenticated connection.</p><p>Please see the <a href="https://github.com/wolfSSL/wolfssh/blob/master/ChangeLog.md">ChangeLog.md</a> for full details.</p><p><strong>New Features</strong><br />The headline addition in v1.5.0 is post-quantum key exchange via ML-KEM hybrid algorithms — mlkem1024nistp384-sha384 and mlkem768x25519-sha256 — based on draft-ietf-sshm-mlkem-hybrid-kex, with interoperability testing against OpenSSH running in CI. This brings wolfSSH in line with the industry direction toward quantum-resistant SSH.</p><p>On the algorithm side, client-side rsa-sha2-512 signature support has been added. The key type is now separated from the signature type, so ssh-rsa keys can be used with ssh-rsa, rsa-sha2-256, or rsa-sha2-512 signatures, improving compatibility with modern SSH servers that have deprecated the older scheme.</p><p>Two handy SFTP client usability improvements also landed: lcd and lls commands for managing the local working directory without leaving an SFTP session.</p><p><strong>Improvements</strong><br />Several handlers that previously lacked proper callback validation have been tightened: host key acceptance, channel open requests, TCP/IP forwarding, and DH group exchange parameters are all now gated and validated. Additional defensive constant-time comparisons were also applied.</p><p>Beyond hardening, SFTP reliability saw meaningful attention – better non-blocking behavior, improved error path handling, and more robust multi-byte password support. CI coverage was expanded significantly with new sanitizer builds, multi-compiler testing, and automated Coverity scanning.</p><p><strong>Fixes</strong><br />This release contains a large number of bug fixes driven by static analysis and code review. Highlights include a non-blocking SFTP server hang on WS_WANT_WRITE, Windows authentication issues, missing hash cleanup in RSA/ECC paths, and a variety of null-dereference, bounds-check, and memory-leak fixes throughout the codebase.</p><p>Download wolfSSH v1.5.0 from our <a href="https://www.wolfssl.com/download/">download page</a>, or clone it from <a href="https://github.com/wolfSSL/wolfssh">GitHub</a>.</p><p>If you have questions about wolfSSH or any of our other products, feel free to reach out at <a href="mailto:facts@wolfssl.com">facts@wolfssl.com</a> or <a href="mailto:support@wolfssl.com">support@wolfssl.com</a>, or give us a call at +1 425 245 8247.</p><p><strong><a href="https://www.wolfssl.com/download/">Download</a> wolfSSL Now</strong></p>]]></content>
			<author>
				<name><![CDATA[shizuka]]></name>
				<uri>https://www.wolfssl.com/forums/user5631.html</uri>
			</author>
			<updated>2026-04-22T17:56:03Z</updated>
			<id>https://www.wolfssl.com/forums/post8795.html#p8795</id>
		</entry>
</feed>
