Re: [openssl.org #2775] [openssh 5.9p1-8] Segmentation fault libcrypto.so.1.0.0

2012-04-13 Thread Kurt Roeckx
On Fri, Apr 13, 2012 at 12:22:56PM +0200, Andy Polyakov wrote: > > There is also: > > http://bugs.debian.org/665836 > > I don't quite understand. The problem was reported for i386, but only > amd64 update packages are provided. I think you have a misunderstanding of how Debian works. I am using

Re: [openssl.org #2775] [openssh 5.9p1-8] Segmentation fault libcrypto.so.1.0.0

2012-04-13 Thread Andy Polyakov
> There is also: > http://bugs.debian.org/665836 I don't quite understand. The problem was reported for i386, but only amd64 update packages are provided. Even though x86_64 module was fixed too, CBC decrypt on x86_64 is handles by another module. So the x86_64 fix was more for some other unspecif

Re: [openssl.org #2775] [openssh 5.9p1-8] Segmentation fault libcrypto.so.1.0.0

2012-04-13 Thread Andy Polyakov via RT
> Please, consider this bugreport: > > https://bugs.archlinux.org/task/29111 Just for record, I consider that it's originator's responsibility to report that problem is diagnosed and solved to archlinux. __ OpenSSL Project

Re: [openssl.org #2775] [openssh 5.9p1-8] Segmentation fault libcrypto.so.1.0.0

2012-03-31 Thread Andy Polyakov
>> Please, consider this bugreport: >> >> https://bugs.archlinux.org/task/29111 > > There is also: > http://bugs.debian.org/665836 Yes, looks like exact duplicate. For reference. It should be possible to avoid vpaes by setting OPENSSL_ia32cap environment variable to ~0x200. Why x86_64 is

Re: [openssl.org #2775] [openssh 5.9p1-8] Segmentation fault libcrypto.so.1.0.0

2012-03-30 Thread Kurt Roeckx
On Wed, Mar 28, 2012 at 10:34:49AM +0200, Joe Bew via RT wrote: > Please, consider this bugreport: > > https://bugs.archlinux.org/task/29111 There is also: http://bugs.debian.org/665836 Kurt __ OpenSSL Project

Re: [openssl.org #2775] [openssh 5.9p1-8] Segmentation fault libcrypto.so.1.0.0

2012-03-29 Thread Andy Polyakov via RT
> Please, consider this bugreport: > > https://bugs.archlinux.org/task/29111 I can't reproduce the problem. Well, I didn't use archlinux binaries, but I could replace 1.0.0 libcrypto.so with 1.0.1 libcrypto.so on rhel and successfully run ssh... I've double-checked and can confirm that vpaes was