[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: OpenSSH issues with Solaris 7/8 [LONG!!]
* Ed Vazquez, Jr. <firstname.lastname@example.org> [010123 14:03]:
> Hah!! That did it!
Hehehe. Sweet. :)
> Seems that the rijndael/aes code is hosed on either the OpenBSD
> side or the Solaris side. Much as I hate to say it, it looks like
> it's the OpenBSD side.
Ok. If you want to help track it down, I would imagine the developers
would like some information about OpenBSD on your sun hardware, and
solaris on your i386 (I can't recall, but I think you had it on i386
My thinking is this might be a byte sex issue, more than an operating
system issue. sparc and i386 have different byte sexes, if I recall --
and if your platforms are divided along sparc/i386 solaris/openbsd, it
might appear that the problem is in openbsd when the problem is really
in the i386.
So, if you have the time/inclination, I would suggest installing
solaris/x86 on one of your openbsd boxes, and perhaps openbsd on one of
your solaris boxes, and try again.
As you have done thus far, write down everything :) , and then submit the
results back to this list, the other two lists you have asked thus far,
and if there are any openssh lists (tech@ may be it? I haven't looked)
post to them as well.
But, of course, the developers may be able to easily check if it is a
byte-sex problem from the source code -- I have no idea. So it *may* be
wise to contact one of the developers first, and ask if it would be
useful for you to perform this testing. If I were a developer, I would
probably find it useful, but I think we can all be thankful I am not an
openssh developer. :)
``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all
really impressed down here, I can tell you.''