Michal Ludvig told me that: > Andy Polyakov told me that: > >>>Attached is "commit candidate," which is prepared for future >>>processor steppings (*_cipher_omnivorous), optimized for small input >>>(alloca instead of fixed realign buffer size), as well as "ported" to >>> Windows. Could you verify that it works? > > As far as I can tell it works - I have built it in 0.9.7 tree and am > using it system-wide (e.g. for ssh/sshd). So far no problems :-)
Wait ... sometimes it fails. Interactive SSH sessions typically run well, but in some cases I get a segfault: E.g. # ssh -v [EMAIL PROTECTED] /usr/X11R6/bin/xlogo OpenSSH_3.8p1, SSH protocols 1.5/2.0, OpenSSL 0.9.7d 17 Mar 2004 debug1: Reading configuration data /root/.ssh/config debug1: Applying options for * debug1: Applying options for ozzy debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to ozzy [10.20.1.72] port 22. debug1: Connection established. debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/identity-cvs type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_3.8p1 debug1: match: OpenSSH_3.8p1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.8p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY Warning: Permanently added 'ozzy,10.20.1.72' (RSA) to the list of known hosts. debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering public key: id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 149 debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: Requesting X11 forwarding with authentication spoofing. debug1: Requesting authentication agent forwarding. debug1: Sending command: /usr/X11R6/bin/xlogo debug1: client_input_channel_open: ctype x11 rchan 4 win 65536 max 16384 debug1: client_request_x11: request from 127.0.0.1 57574 debug1: channel 1: new [x11] debug1: confirm x11 Segmentation fault This happens in padlock_aes_cipher(), but I haven't got a usefull backtrace: #0 0x400b62c8 in padlock_aes_cipher () from /usr/lib/libcrypto.so.0.9.7 #1 0xbfffcf90 in ?? () #2 0x00000040 in ?? () #3 0xbfffcfc0 in ?? () [...] I will try to find out where exactly it dies... Michal Ludvig ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
