Problem with connecting to host running ssh 2.3.0p1

Damien Miller djm at
Tue Mar 20 15:52:06 EST 2001

On Mon, 19 Mar 2001, Phil Karn wrote:

> >A fix for the endian problem went in between 2.5.1p1 and 2.5.2p2, so you
> >are running the last bad version :) If you upgrade to the just-released
> >2.5.2p1 then all should be well.
> Sorry, can you explain in more detail? Where is the endian problem?
> Is it triggered by a new client simply by a change in the default cipher?

Our Rijndael implementation was not having the correct endian macros
defined and was defaulting to little endian in all cases. This bug
exists in all OpenSSH versions which supported Rijndael upto (and including)

However, for versions before 2.5.1, the problem didn't usually manifest
because rijndael/aes was a fair way down on the list of ciphers that
were negotiated (unless the user specified Ciphers themselves)

Recent versions have moved Rijndael/AES to the top of the list so that
it is always negoitated if the client & server support it.


| Damien Miller <djm at> \ ``E-mail attachments are the poor man's
|          /   distributed filesystem'' - Dan Geer

More information about the openssh-unix-dev mailing list