RE: SSL_ERROR_SYSCALL errno=0

Thanks for the reply. I'll give the suggestions a try tomorrow. We've been thinking, that our kernel version (it is custom and does not support all system calls) is relatively old and missing some features that are required by OpenSSL. I'll post back tomorrow, if anything changes. Note: I've tried

Re: SSL_ERROR_SYSCALL errno=0

Strace shows the following before the error: ioctl(10, TCGETS, 0x7fffe068) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x300 26000 _llseek(0xa, 0, 0, 0x7fffe2f8, 0x1) = -1 ESPIPE (Illegal seek) -- View this message in context: http://openssl.6

SSL_ERROR_SYSCALL errno=0

Hello, I have an issue, that I've been trying to resolve for weeks now. I have 2 devices. The major different between them is the linux Kernel version. On Linux 2.6.24.6, ssl_connect() works flawlessly. On 2.4.21 it returns -1. The SSL_get_error() returns SSL_ERROR_SYSCALL but errno is 0 (perror()

RE: SSMTP Client: SSL routines:SSL23_GET_SERVER_HELLO

Just to add more details, here are the replies that my code prints out, when trying to connect to smtp.gmail.com:587 *220 mx.google.com ESMTP x3sm39000551eep.17 - gsmtp //EHLO// 250-mx.google.com at your service, [80.149.109.201] 250-SIZE 3588257

RE: SSMTP Client: SSL routines:SSL23_GET_SERVER_HELLO

sorry for the late reply. I was on vacation. Unfortunately, I returned and could not find the managed switch anymore. Someone must've taken it. So I won't be able to post a .pcap file, since I cannot remote capture. However, it seems I managed to get rid of the "unknown protocol" error. I was usi

SSMTP Client: SSL routines:SSL23_GET_SERVER_HELLO

openssl_capture.txt Hello, I'm using OpenSSL in order to encrypt some emails, that a piece of hardware sends. But, whenever I try to call SSL_connect(), I get : SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol After sending