(And I'll cc the developers list so they can see the problem.) The archives show there have been a number of queries on "handshake failure" errors in the past year (including mine a couple of weeks ago), but I haven't seen but one response. So while I don't (yet) have any definite answers, perhaps I provide some suggestions.
First of all, note that the "s2_pkt.c:371" the end of the error message is telling which source code file, and even the line number, where the error occured. Hmm, it looks like it ran out of data. Well, that wasn't too helpful, but it's good to check. A key problem here [hey, developers, take note!] is that we don't know whether the "error" was the s2_pkt code taking a dive because of a "shouldn't happen" condition it couldn't handle (poor code?), or because the two parties here couldn't agree on a handshake. Consider the latter possibility. In my case I was testing a server I am setting up, and I had doubts about how the certificates are set up. Removing them entirely also resulted in a 'handshake failure', so this could be problem with the certificates. Some things to check: Are the certificates on your second destination valid? Does their setup correspond with that on your first destination? Do you have other services that use them? (Are you going to a standard https server, or a custom server?) Have you checked the logs? Also: use 'openssl'. (It may be easier to manipulate than your executable, and it has a bunch of options affecting the SSL aspects.) Do something like 'openssl s_client -connect <host>:443' to connect to the secure http server. (There is no prompt. Type something like "get / http/1.0" and hit return twice.) Also note that openssl can also be run as a minimal web server. Good luck, and let me know what if you find anything. === JJ ============================================================= On Mon, 12 Nov 2001, Vikram Motwani wrote: > Hi, > > I am new to ssl and am trying to upload files to a > server using https post. I am using an executable that > takes <infile> <URL:https://...> <username> <password> > as inputs from the command prompt. > > Unfortunately it was written by someone else. I can > upload files from a machines on one domain but not on > other. > > I get the following error on client trying to upload > files to server: > > 279:error:1407F0E1:SSL routines:SSL2_WRITE:ssl > handshake failure.\ssl\s2_pkt.c:371. > > Can anyone tell me how to fix this and what the > problem might be. > > Thanks in advance, > > Vikram > > __________________________________________________ > Do You Yahoo!? > Find a job, post your resume. > http://careers.yahoo.com > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
