[AOLSERVER] [ aolserver-Patches-423820 ] patch for nsperm/init.tcl
Patches item #423820, was updated on 2001-05-13 17:27
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=303152&aid=423820&group_id=3152
Category: aolserver3_3
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Hal Heisler (hheisler)
Assigned to: Nobody/Anonymous (nobody)
Summary: patch for nsperm/init.tcl
Initial Comment:
Allows one to specify in the tcl configuration file
where nsperm files reside.
Example
ns_section "ns/server/${server}/module/nsperm"
ns_param nspermdirectory "${serverdir}/modules/nsperm"
--
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=303152&aid=423820&group_id=3152
[AOLSERVER] Unsubscribe
Automatic digest processor wrote: > There is one message totalling 68 lines in this issue. > > Topics of the day: > > 1. [ aolserver-Bugs-423587 ] gmake on FreeBSD 4.3/Aolserver-3.3.1 > > -- > > Date:Sat, 12 May 2001 10:31:21 -0700 > From:"Mr. Source Forge" <[EMAIL PROTECTED]> > Subject: [ aolserver-Bugs-423587 ] gmake on FreeBSD 4.3/Aolserver-3.3.1 > > Bugs item #423587, was updated on 2001-05-12 10:31 > You can respond by visiting: > http://sourceforge.net/tracker/?func=detail&atid=103152&aid=423587&group_id=3152 > > Category: Configuration: Server > Group: aolserver3_3 > Status: Open > Resolution: None > Priority: 5 > Submitted By: Tyge Cawthon (tyge) > Assigned to: Nobody/Anonymous (nobody) > Summary: gmake on FreeBSD 4.3/Aolserver-3.3.1 > > Initial Comment: > gmake does not work correctly on FreeBSD 4.3 and > Aolserver-3.3.1. > > I believe the problem is the file > /aolserver-3.3.1/include/Makefile.global > > Towards the end of the file there is line: > TCL8X_LIB=libtcl83g. > I am not sure, but I believe the line should be: > TCL8X_LIB=libtcl8.3g. > > Could someone please check into this. > See example below: > > BEFORE: > #Note: Tcl 7.6 on *BSD has a different name for no > apparent reason. > # > TCL8X_DIR=tcl8.3.2 > TCL76_DIR=tcl7.6 > ifeq (bsd, $(findstring bsd, $(PLATFORM))) >TCL76_LIB=libtcl76.a > ===> TCL8X_LIB=libtcl83g.a <=== > else >TCL76_LIB=libtcl7.6.a# >TCL8X_LIB=libtcl8.3g.a > endif > > AFTER: > #NOTE: Tcl 7.6 on *BSD has a different name for no > apparent reason. > # > TCL8X_DIR=tcl8.3.2 > TCL76_DIR=tcl7.6 > ifeq (bsd, $(findstring bsd, $(PLATFORM))) >TCL76_LIB=libtcl76.a > ===> TCL8X_LIB=libtcl8.3g.a <=== > else >TCL76_LIB=libtcl7.6.a >TCL8X_LIB=libtcl8.3g.a > endif > > -- > > You can respond by visiting: > http://sourceforge.net/tracker/?func=detail&atid=103152&aid=423587&group_id=3152 > > -- > > End of AOLSERVER Digest - 11 May 2001 to 12 May 2001 (#2001-120) > -- == John Muller InHaven | BCG T: 212-879-1583 F: 212-327-2239 E: [EMAIL PROTECTED] ==
[AOLSERVER] [ aolserver-Patches-423820 ] patch for nsperm/init.tcl
Patches item #423820, was updated on 2001-05-13 17:27
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=303152&aid=423820&group_id=3152
Category: aolserver3_3
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Hal Heisler (hheisler)
Assigned to: Nobody/Anonymous (nobody)
Summary: patch for nsperm/init.tcl
Initial Comment:
Allows one to specify in the tcl configuration file
where nsperm files reside.
Example
ns_section "ns/server/${server}/module/nsperm"
ns_param nspermdirectory "${serverdir}/modules/nsperm"
--
>Comment By: Hal Heisler (hheisler)
Date: 2001-05-14 08:20
Message:
Logged In: YES
user_id=20579
Trying to attach the patch again.
--
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=303152&aid=423820&group_id=3152
Re: [AOLSERVER] ns_realloc error
Rob, I wish I could tell you more, but the error seems to occur very sporadically. Sometimes the server will stay up for weeks and sometimes it will crash with this error message after a few minutes. I haven't been able to track down any single thing that seems to be occuring right before this error happens. My question was kind of general because I am not sure what situations can cause this error to occur. Maybe the server truly is out of memory, but top says otherwise. Do you know the situations in which this error will occur? Brian
Re: [AOLSERVER] nsssl -> openssl ?
O.K, With a little Makefile and source hacking I got nsopenssl.so to build. (OPENSSL_free isn't in my version of OpenSSL, was it added later? [tclcmds.c]) Now my problem is that the module fails to load the certfile.pem. I created my own self-signed certificate using openssl, and from what I can tell it looks O.K. Has anyone tryed this before? I just think I'm missing something that my brain can't figure out. :-) P.S. The cert was generated from an unencrypted 3DES 1024-bit key if that helps any. "Daniel P. Stasinski" wrote: > > > I was wondering if there was anything in the works to port > > nsssl from BSAFE to OpenSSL? It appears that getting > > your hands on BSAFE would be the first problem. > > Try nsopenssl at: > > http://scottg.net/webtools/opennsd/modules/nsopenssl/ > > Daniel P. Stasinski > http://www.disabilities-r-us.com > [EMAIL PROTECTED]
[AOLSERVER] Best version for production server?
Hi there, I was wondering what everybody's opinion was on the most stable version of the server for use in a production environment? I have a production server running version 3.0 on Linux - it handles a CRM (Customer Relations Management) system which deals with about 10K email messages per day for various About.com properties. The system itself is relatively similar to Kana, for those of you who are familiar with that product. I've found, though, that the main server will freeze mysteriously about once a week; nothing is written out to the log files, and servers running on other ports will still respond. I'd like to upgrade to a more recent version of AOLServer. Any suggestions/discussion on what a good version to pick would be much appreciated! thanks, thomas __ Thomas Park Technology About The Human Internet http://About.com 27 Melcher St. 3rd floor Boston, Massachusetts 02210 voice: 617.670.4019 email: [EMAIL PROTECTED] __
Re: [AOLSERVER] Best version for production server?
Use AOLserver 3.4pre1 which will be released as AOLserver 3.4 this week. If you don't want to do that, AOLserver 3.3.1 is the most recent "released" version. Kris > -Original Message- > From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On Behalf > Of Thomas Park > Sent: Mon, 05-14-01 01:39p > To: [EMAIL PROTECTED] > Subject: [AOLSERVER] Best version for production server? > > > Hi there, > > I was wondering what everybody's opinion was on the most stable > version of the server for use in a production environment? I > have a production server running version 3.0 on Linux - it > handles a CRM (Customer Relations Management) system which deals > with about 10K email messages per day for various About.com > properties. The system itself is relatively similar to Kana, for > those of you who are familiar with that product. > > I've found, though, that the main server will freeze mysteriously > about once a week; nothing is written out to the log files, and > servers running on other ports will still respond. I'd like to > upgrade to a more recent version of AOLServer. Any > suggestions/discussion on what a good version to pick would be > much appreciated! > > thanks, > thomas > > __ > Thomas Park > Technology > > About > The Human Internet > > http://About.com > 27 Melcher St. 3rd floor > Boston, Massachusetts > 02210 > > voice: 617.670.4019 > email: [EMAIL PROTECTED] > __ >
Re: [AOLSERVER] ns_realloc error
Brian Jones wrote: > Maybe the server truly is > out of memory, but top says otherwise. Do you know the situations in which > this error will occur? You would have to look at top just before this happened, because after it happens, most of the memory used by AOLserver will be released. It seems like a small amount (less than a meg). Is the amount always the same? --Tom Jackson
Re: [AOLSERVER] Best version for production server?
Thomas Park wrote: > > Hi there, > > I was wondering what everybody's opinion was on the most stable version of the >server for use in a production environment? I have a production server running >version 3.0 on Linux - it handles a CRM (Customer Relations Management) system which >deals with about 10K email messages per day for various About.com properties. The >system itself is relatively similar to Kana, for those of you who are familiar with >that product. > > I've found, though, that the main server will freeze mysteriously about once a week; >nothing is written out to the log files, and servers running on other ports will >still respond. I'd like to upgrade to a more recent version of AOLServer. Any >suggestions/discussion on what a good version to pick would be much appreciated! you might be running into the 'thread memory leak bug' present in the earilier 3.X versions of aolserver. the latest version 3.3.1 fixes that problem. the link for downloading 3.3.1 is http://aolserver.com/archive/server/aolserver-3.3.1.tar.gz -mike > > thanks, > thomas > > __ > Thomas Park > Technology > > About > The Human Internet > > http://About.com > 27 Melcher St. 3rd floor > Boston, Massachusetts > 02210 > > voice: 617.670.4019 > email: [EMAIL PROTECTED] > __
Re: [AOLSERVER] nsssl -> openssl ?
Make sure your private key is not passphrase-protected; if it is, it'll fail to be loaded by the server. You can use openssl to take the passphrase off, but make sure you lock up this file so that only the server can read it (root will also be able to read it, obviously): openssl rsa -in key1.pem -out key2.pem The latest version is nsopenssl-1.1 and is available at http://scottg.net. You'll want to use this version, and it requires OpenSSL 0.9.6 or higher (though I haven't tested with 0.9.6a yet). /s. > O.K, > > With a little Makefile and source hacking I got nsopenssl.so to > build. (OPENSSL_free isn't in my version of OpenSSL, was it added > later? [tclcmds.c]) > > Now my problem is that the module fails to load the certfile.pem. I > created my own self-signed certificate using openssl, and from what I > can tell it looks O.K. Has anyone tryed this before? I just think > I'm missing something that my brain can't figure out. :-) > > P.S. > The cert was generated from an unencrypted 3DES 1024-bit key if that > helps any. > > "Daniel P. Stasinski" wrote: > > > > > I was wondering if there was anything in the works to port > > > nsssl from BSAFE to OpenSSL? It appears that getting > > > your hands on BSAFE would be the first problem. > > > > Try nsopenssl at: > > > > http://scottg.net/webtools/opennsd/modules/nsopenssl/ > > > > Daniel P. Stasinski > > http://www.disabilities-r-us.com > > [EMAIL PROTECTED] > >
Re: [AOLSERVER] nsssl -> openssl ?
I've always wondered why servers bother to encrypt the private key. The passphrase is right there in the server configuration so why bother? Kris > -Original Message- > From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On Behalf > Of Scott Goodwin > Sent: Mon, 05-14-01 02:40p > To: [EMAIL PROTECTED] > Subject: Re: [AOLSERVER] nsssl -> openssl ? > > > Make sure your private key is not passphrase-protected; if it is, it'll > fail to be loaded by the server. You can use openssl to take the > passphrase > off, but make sure you lock up this file so that only the server can read > it (root will also be able to read it, obviously): > > > openssl rsa -in key1.pem -out key2.pem > > > The latest version is nsopenssl-1.1 and is available at http://scottg.net. > > You'll want to use this version, and it requires OpenSSL 0.9.6 or higher > (though I haven't tested with 0.9.6a yet). > > /s. > > > > O.K, > > > > With a little Makefile and source hacking I got nsopenssl.so to > > build. (OPENSSL_free isn't in my version of OpenSSL, was it added > > later? [tclcmds.c]) > > > > Now my problem is that the module fails to load the certfile.pem. I > > created my own self-signed certificate using openssl, and from what I > > can tell it looks O.K. Has anyone tryed this before? I just think > > I'm missing something that my brain can't figure out. :-) > > > > P.S. > > The cert was generated from an unencrypted 3DES 1024-bit key if that > > helps any. > > > > "Daniel P. Stasinski" wrote: > > > > > > > I was wondering if there was anything in the works to port > > > > nsssl from BSAFE to OpenSSL? It appears that getting > > > > your hands on BSAFE would be the first problem. > > > > > > Try nsopenssl at: > > > > > > http://scottg.net/webtools/opennsd/modules/nsopenssl/ > > > > > > Daniel P. Stasinski > > > http://www.disabilities-r-us.com > > > [EMAIL PROTECTED] > > > > >
Re: [AOLSERVER] nsssl -> openssl ?
> I've always wondered why servers bother to encrypt the private key. The > passphrase is right there in the server configuration so why bother? I believe that if you use Apache/mod_ssl with an encrypted key, the server will pause at startup time and prompt you to enter the passphrase on the command line. The problems with this approach should be obvious...
Re: [AOLSERVER] nsssl -> openssl ?
Rob Mayoff wrote: > I believe that if you use Apache/mod_ssl with an encrypted key, the > server will pause at startup time and prompt you to enter the passphrase > on the command line. > > The problems with this approach should be obvious... Particularly when it's a remote server. That command-line prompt on the (nonexistent) console is not 100% useful. I discovered this "security feature" the hard way once.
Re: [AOLSERVER] nsssl -> openssl ?
The keyfile was decrypted before I created the CSR. The server dies trying to load the signed (by me) certificate, even though: openssl x509 -noout -text -in certfile.pem Reguritates out the cert information O.K. I guess I failed to mention I'm using nsopenssl 1.1 I must have an older version of OpenSSL, since the OPENSSL_free stub isn't there. I'll try and upgrade OpenSSL and try again. Scott Goodwin wrote: > > Make sure your private key is not passphrase-protected; if it is, it'll > fail to be loaded by the server. You can use openssl to take the passphrase > off, but make sure you lock up this file so that only the server can read > it (root will also be able to read it, obviously): > > openssl rsa -in key1.pem -out key2.pem > > The latest version is nsopenssl-1.1 and is available at http://scottg.net. > > You'll want to use this version, and it requires OpenSSL 0.9.6 or higher > (though I haven't tested with 0.9.6a yet). > > /s. > > > O.K, > > > > With a little Makefile and source hacking I got nsopenssl.so to > > build. (OPENSSL_free isn't in my version of OpenSSL, was it added > > later? [tclcmds.c]) > > > > Now my problem is that the module fails to load the certfile.pem. I > > created my own self-signed certificate using openssl, and from what I > > can tell it looks O.K. Has anyone tryed this before? I just think > > I'm missing something that my brain can't figure out. :-) > > > > P.S. > > The cert was generated from an unencrypted 3DES 1024-bit key if that > > helps any. > > > > "Daniel P. Stasinski" wrote: > > > > > > > I was wondering if there was anything in the works to port > > > > nsssl from BSAFE to OpenSSL? It appears that getting > > > > your hands on BSAFE would be the first problem. > > > > > > Try nsopenssl at: > > > > > > http://scottg.net/webtools/opennsd/modules/nsopenssl/ > > > > > > Daniel P. Stasinski > > > http://www.disabilities-r-us.com > > > [EMAIL PROTECTED] > > > >
Re: [AOLSERVER] nsssl -> openssl ?
Which is why I'm not going to bother to put the code in nsopenssl to ask for the passphrase. I'll probably add a message in the error log telling the user that the private key may be pass-phrase protected and how to tell if it is and how to take off the pass-phrase. /s. > I've always wondered why servers bother to encrypt the private key. The > passphrase is right there in the server configuration so why bother? > > Kris > > > > -Original Message- > > From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On Behalf > > Of Scott Goodwin > > Sent: Mon, 05-14-01 02:40p > > To: [EMAIL PROTECTED] > > Subject: Re: [AOLSERVER] nsssl -> openssl ? > > > > > > Make sure your private key is not passphrase-protected; if it is, it'll > > fail to be loaded by the server. You can use openssl to take the > > passphrase > > off, but make sure you lock up this file so that only the server can read > > it (root will also be able to read it, obviously): > > > > > > openssl rsa -in key1.pem -out key2.pem > > > > > > The latest version is nsopenssl-1.1 and is available at http://scottg.net. > > > > You'll want to use this version, and it requires OpenSSL 0.9.6 or higher > > (though I haven't tested with 0.9.6a yet). > > > > /s. > > > > > > > O.K, > > > > > > With a little Makefile and source hacking I got nsopenssl.so to > > > build. (OPENSSL_free isn't in my version of OpenSSL, was it added > > > later? [tclcmds.c]) > > > > > > Now my problem is that the module fails to load the certfile.pem. I > > > created my own self-signed certificate using openssl, and from what I > > > can tell it looks O.K. Has anyone tryed this before? I just think > > > I'm missing something that my brain can't figure out. :-) > > > > > > P.S. > > > The cert was generated from an unencrypted 3DES 1024-bit key if that > > > helps any. > > > > > > "Daniel P. Stasinski" wrote: > > > > > > > > > I was wondering if there was anything in the works to port > > > > > nsssl from BSAFE to OpenSSL? It appears that getting > > > > > your hands on BSAFE would be the first problem. > > > > > > > > Try nsopenssl at: > > > > > > > > http://scottg.net/webtools/opennsd/modules/nsopenssl/ > > > > > > > > Daniel P. Stasinski > > > > http://www.disabilities-r-us.com > > > > [EMAIL PROTECTED] > > > > > > > > > >
Re: [AOLSERVER] nsssl -> openssl ?
I have test platform that contains everything necessary to compile and configure aolserver, nsopenssl, ssldump in a self-contained area to test in. If you can't get it working and you want to try out the test suite, I'll let you know how to download. /s. > The keyfile was decrypted before I created the CSR. The server dies > trying to load the signed (by me) certificate, even though: > > openssl x509 -noout -text -in certfile.pem > > Reguritates out the cert information O.K. I guess I failed to mention > I'm using nsopenssl 1.1 > > I must have an older version of OpenSSL, since the OPENSSL_free stub > isn't there. I'll try and upgrade OpenSSL and try again. > > Scott Goodwin wrote: > > > > Make sure your private key is not passphrase-protected; if it is, it'll > > fail to be loaded by the server. You can use openssl to take the passphrase > > off, but make sure you lock up this file so that only the server can read > > it (root will also be able to read it, obviously): > > > > openssl rsa -in key1.pem -out key2.pem > > > > The latest version is nsopenssl-1.1 and is available at http://scottg.net. > > > > You'll want to use this version, and it requires OpenSSL 0.9.6 or higher > > (though I haven't tested with 0.9.6a yet). > > > > /s. > > > > > O.K, > > > > > > With a little Makefile and source hacking I got nsopenssl.so to > > > build. (OPENSSL_free isn't in my version of OpenSSL, was it added > > > later? [tclcmds.c]) > > > > > > Now my problem is that the module fails to load the certfile.pem. I > > > created my own self-signed certificate using openssl, and from what I > > > can tell it looks O.K. Has anyone tryed this before? I just think > > > I'm missing something that my brain can't figure out. :-) > > > > > > P.S. > > > The cert was generated from an unencrypted 3DES 1024-bit key if that > > > helps any. > > > > > > "Daniel P. Stasinski" wrote: > > > > > > > > > I was wondering if there was anything in the works to port > > > > > nsssl from BSAFE to OpenSSL? It appears that getting > > > > > your hands on BSAFE would be the first problem. > > > > > > > > Try nsopenssl at: > > > > > > > > http://scottg.net/webtools/opennsd/modules/nsopenssl/ > > > > > > > > Daniel P. Stasinski > > > > http://www.disabilities-r-us.com > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > >
[AOLSERVER] [ aolserver-Bugs-423587 ] gmake on FreeBSD 4.3/Aolserver-3.3.1
Bugs item #423587, was updated on 2001-05-12 10:31 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=103152&aid=423587&group_id=3152 Category: Configuration: Server Group: aolserver3_3 Status: Open Resolution: None Priority: 5 Submitted By: Tyge Cawthon (tyge) Assigned to: Nobody/Anonymous (nobody) Summary: gmake on FreeBSD 4.3/Aolserver-3.3.1 Initial Comment: gmake does not work correctly on FreeBSD 4.3 and Aolserver-3.3.1. I believe the problem is the file /aolserver-3.3.1/include/Makefile.global Towards the end of the file there is line: TCL8X_LIB=libtcl83g. I am not sure, but I believe the line should be: TCL8X_LIB=libtcl8.3g. Could someone please check into this. See example below: BEFORE: #Note: Tcl 7.6 on *BSD has a different name for no apparent reason. # TCL8X_DIR=tcl8.3.2 TCL76_DIR=tcl7.6 ifeq (bsd, $(findstring bsd, $(PLATFORM))) TCL76_LIB=libtcl76.a ===> TCL8X_LIB=libtcl83g.a <=== else TCL76_LIB=libtcl7.6.a# TCL8X_LIB=libtcl8.3g.a endif AFTER: #NOTE: Tcl 7.6 on *BSD has a different name for no apparent reason. # TCL8X_DIR=tcl8.3.2 TCL76_DIR=tcl7.6 ifeq (bsd, $(findstring bsd, $(PLATFORM))) TCL76_LIB=libtcl76.a ===> TCL8X_LIB=libtcl8.3g.a <=== else TCL76_LIB=libtcl7.6.a TCL8X_LIB=libtcl8.3g.a endif -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=103152&aid=423587&group_id=3152
[AOLSERVER] nsfreetds-0.1pre (an internal TDS-based database driver) up for testing
All, This is to announce the release of nsfreetds-0.1pre, an internal database driver that uses TDS to connect to both Microsoft SQL Server and Sybase databases. It uses the FreeTDS 0.51 implementation of the TDS protocol for connectivity. The driver has been tested with AOLserver 3.3.1 on both x86 Linux and SPARC Solaris 2.6, connecting to Sybase 11 running on SPARC Solaris 2.6, and Microsoft SQL Server 7 and 2000 running on both WinNT 4.0 and Win2000. The home for nsfreetds is at: http://panoptic.com/wiki/aolserver/nsfreetds nsfreetds-0.1pre is available at: ftp://ftp.panoptic.com/pub/nsfreetds/nsfreetds-0.1pre.tar.gz The nsfreetds FAQ is at: http://panoptic.com/wiki/aolserver/nsfreetdsFAQ I invite everyone interested to download nsfreetds and try it out, and provide me with any feedback. It would also be nice if people using the driver would send me an email and let me know if they were able to get the driver working and describe what configuration they used with it (both AOLserver and database version and platform information). I'd also like to see if someone could benchmark the nsfreetds driver against the nssybpd and nsodbc drivers, to get an idea of the difference between an internal vs. external (in the case of nssybpd) and a native TDS driver vs. an ODBC driver (in the case of nsodbc). - Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/
Re: [AOLSERVER] nsssl -> openssl ?
Scott Goodwin wrote: > > I have test platform that contains everything necessary to compile and > configure aolserver, nsopenssl, ssldump in a self-contained area to test > in. If you can't get it working and you want to try out the test suite, > I'll let you know how to download. > > /s. > > > The keyfile was decrypted before I created the CSR. The server dies > > trying to load the signed (by me) certificate, even though: > > > > openssl x509 -noout -text -in certfile.pem > > > > Reguritates out the cert information O.K. I guess I failed to mention > > I'm using nsopenssl 1.1 > > > > I must have an older version of OpenSSL, since the OPENSSL_free stub > > isn't there. I'll try and upgrade OpenSSL and try again. > > > > Scott Goodwin wrote: > > > > > > Make sure your private key is not passphrase-protected; if it is, it'll > > > fail to be loaded by the server. You can use openssl to take the > passphrase > > > off, but make sure you lock up this file so that only the server can > read > > > it (root will also be able to read it, obviously): > > > > > > openssl rsa -in key1.pem -out key2.pem > > > > > > The latest version is nsopenssl-1.1 and is available at > http://scottg.net. > > > > > > You'll want to use this version, and it requires OpenSSL 0.9.6 or higher > > > (though I haven't tested with 0.9.6a yet). I'll try again with 0.9.6a and let you know how it goes. Hopefully it's backwards-compatible. :-) > > > > > > /s. > > > > > > > O.K, > > > > > > > > With a little Makefile and source hacking I got nsopenssl.so to > > > > build. (OPENSSL_free isn't in my version of OpenSSL, was it added > > > > later? [tclcmds.c]) > > > > > > > > Now my problem is that the module fails to load the certfile.pem. I > > > > created my own self-signed certificate using openssl, and from what I > > > > can tell it looks O.K. Has anyone tryed this before? I just think > > > > I'm missing something that my brain can't figure out. :-) > > > > > > > > P.S. > > > > The cert was generated from an unencrypted 3DES 1024-bit key if that > > > > helps any. > > > > > > > > "Daniel P. Stasinski" wrote: > > > > > > > > > > > I was wondering if there was anything in the works to port > > > > > > nsssl from BSAFE to OpenSSL? It appears that getting > > > > > > your hands on BSAFE would be the first problem. > > > > > > > > > > Try nsopenssl at: > > > > > > > > > > http://scottg.net/webtools/opennsd/modules/nsopenssl/ > > > > > > > > > > Daniel P. Stasinski > > > > > http://www.disabilities-r-us.com > > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > >
