Re: [AOLSERVER] Problems with nsopenssl-2.1a(compilation) and nsopenssl-3.0beta26(runtime)

2007-01-24 Thread Pedro Liska
Hi Scott, It's working now! I started from scratch deleting all executables and sources of everything (Tcl, AOLserver, OpenSSL, nsopenssl). And I used your ./config call. Since I had already installed local copies of Tcl (with --enable-threads) and OpenSSL before my post to this mailing list,

Re: [AOLSERVER] Problems with nsopenssl-2.1a(compilation) and nsopenssl-3.0beta26(runtime)

2007-01-23 Thread Pedro Liska
I grabbed nsopenssl from cvs and still got the same error. I included what I did below. Do you think starting from a fresh Red Hat ES 4 install would make a difference? I'm pretty much at the point that if someone told me that throwing the IBM R50 thinkpad (where I'm testing this stuff) off a 50

Re: [AOLSERVER] Problems with nsopenssl-2.1a(compilation) and nsopenssl-3.0beta26(runtime)

2007-01-23 Thread Scott Goodwin
I notice below that while you are pre-binding to port 80, you aren't pre-binding to port 443, which is the port SSL defaults to (though this probably isn't causing your segfault). Are you using the RedHat's default OpenSSL and Tcl system installations? Looks like you're using your own

[AOLSERVER] Problems with nsopenssl-2.1a(compilation) and nsopenssl-3.0beta26(runtime)

2007-01-22 Thread Pedro Liska
Hi, I got AOLserver 4.5 running my website with no problems. But I also need https to work and that's where things got nasty. I'm aiming for AOLserver 4.5 with nsopenssl-2.1a but I also tried getting nsopenssl-3.0beta26 to work. When gmake'ing nsopenssl-2.1a I get the following error:

Re: [AOLSERVER] Problems with nsopenssl-2.1a(compilation) and nsopenssl-3.0beta26(runtime)

2007-01-22 Thread Scott Goodwin
nsopenssl 2.x won't work with AOLserver 4.5.x. nsopenssl-3.0beta26 is segfaulting when generating temporary 512-bit keys. This was fixed a while back -- go grab the cvs copy of nsopenssl from sourceforge. I just compiled it with AOLserver 4.5.0 and it runs, though it gives me an error