Bug#350747: stunnel: fails to start

Hello Luc, I am currently waiting for the next stable release of stunnel 4 (the current version is considered testing) that will fix some bugs. I think I can remove stunnel4 package and put the next version of stunnel4 as standard package of stunnel since there is a compatibility script for

Bug#350747: stunnel: fails to start

tag 350747 + moreinfo thanks Heya, The last mail in this bug report is already 10 weeks old. Luk, do you still remember how you generated the cert that lead to this stunnel problem? Marc -- BOFH #418: Sysadmins busy fighting SPAM. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a

Processed: Re: Bug#350747: stunnel: fails to start

Processing commands for [EMAIL PROTECTED]: tag 350747 + moreinfo Bug#350747: stunnel: fails to start There were no tags set. Tags added: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs

Bug#350747: stunnel: fails to start

Marc 'HE' Brockschmidt wrote: tag 350747 + moreinfo thanks Heya, The last mail in this bug report is already 10 weeks old. Luk, do you still remember how you generated the cert that lead to this stunnel problem? I can find it back, though it takes some time... Anyway, stunnel4 worked

Bug#350747: stunnel: fails to start

Hello Justin, Justin Pryzby wrote: Is there any progress on this bug? Does stunnel need to have files regenerated during upgrade? I am not sure that this is a bug, when certificates are generated conforming to documentation stunnel works fine. The only solution is to regenerate your

Bug#350747: stunnel: fails to start

On Sun, Mar 26, 2006 at 10:38:34AM +0200, Julien Lemoine wrote: Hello Justin, Justin Pryzby wrote: Is there any progress on this bug? Does stunnel need to have files regenerated during upgrade? I am not sure that this is a bug, when certificates are generated conforming to

Bug#350747: stunnel: fails to start

Julien Lemoine wrote: Hello Justin, Justin Pryzby wrote: Is there any progress on this bug? Does stunnel need to have files regenerated during upgrade? I am not sure that this is a bug, when certificates are generated conforming to documentation stunnel works fine. The only

Bug#350747: stunnel: fails to start

Hello, * Luk Claes [EMAIL PROTECTED] [2006-03-26 16:12:37 +0200]: Note that in my case I generated the certificates in one file and the only solution was using stunnel4... Can you give me openssl command that you used to generate your certificate in order to reproduce this problem ? Thanks

Bug#350747: stunnel: fails to start

Hello, Is there any progress on this bug? Does stunnel need to have files regenerated during upgrade? Thanks Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#350747: stunnel: fails to start

Hi I wanted to file a similar bug... What worked for me was regenerating the certificate and key (though I put them in the same file) after upgrading to stunnel4. I hope this helps. Cheers Luk -- Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D Fingerprint: D5AF 25FB

Bug#350747: stunnel: fails to start

Package: stunnel Version: 2:3.26-3 Severity: grave Justification: renders package unusable Created a certificate and a key, using openssl req -new -x509 -days 730 -nodes -out stunnel-cert.pem -keyout stunnel.pem stunnel 3.25-3 used to work. Upgrading to a higher version, I get: Jan 31

Bug#350747: stunnel: fails to start

Hello Jesus, Hum it is strange, I tested stunnel 3 and it works well with a pem file containing both private and certificate as specified in stunnel 3 documentation. Extract from documentation : --- STUNNEL MAN EXTRACT --- The order of contents of the .pem file is also