Bug#334501: [Pkg-openssl-devel] Bug#334501: libcryto.so.0.9.8 cause a SIGFAULT in ssh

[Kurt Roeckx]

On Thu, Oct 20, 2005 at 10:37:55AM +0200, Christoph Martin wrote:
> 
> > Of course we can't change this, since this would be an ABI
> > change.
> 
> Are you shure? Is this change really visible to the application? Anyway
> I would prefere to include the correct fix in the next version. We are
> in unstable and in the early stages of the 0.9.8 transition. Things may
> break. We just have to again bump the shlibs version.

Yes, I've just installed such a changed version, and ssh
segfaults again.  It's also in the public header, so it's really
off limit.

>From the ssh source for instance:
static RC4_KEY rc4;

        memset(&rc4, 0, sizeof(rc4));

I see 2 options:
- Wait for the next soname change to start using the assembler
  version again.
- Make the assembler version aware of the size of an RC4_KEY.

> BTW: Upstream does not define the RC4_CHAR flag for this architecture.
> It also does not define the flag for ia64 where we do define it. We
> might have the same problem with ia64.

Right, so it's a good idea to drop it in the future.

The IA64 version atleast seems to have support for using
different sizes of the code, unfortuantly, it does:
#define SZ      4       // this is set to sizeof(RC4_INT)

Instead of just setting it to the sizeof() itself.

So this might require changing too.  I'll try and test this on
the ia64 porter machine later.


Kurt