Bug#503495: inn2: SSL-Documentation and -Support is wrong/broken

2008-12-07 Thread Julien ÉLIE
Hi Michael, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503495 I don't think debian should make it harder than needed to enable encryption. NNTPS is a way to do it, but putting protocols inside SSL on another port is nowadays deprecated in favor of TLS upgrade through STARTTLS. We reall

Bug#503495: inn2: SSL-Documentation and -Support is wrong/broken

2008-10-26 Thread Russ Allbery
Michael Holzt <[EMAIL PROTECTED]> writes: >> c) run nnrpd from inetd. > > This is not possible without the use of a secondary ip address. Or running innd on port 433 and coordinating that with your peers and then running nnrpd on port 119 out of xinetd or the like, which is really a better soluti

Bug#503495: inn2: SSL-Documentation and -Support is wrong/broken

2008-10-26 Thread Julien ÉLIE
Hi Michael, I can surely send a patch. Oh, in case there is a new version for Lenny, could you please update at the same time the license: http://inn.eyrie.org/viewcvs/*checkout*/branches/2.4/LICENSE There is a new paragraph about lib/md5.c which is currently missing in what is shipped wi

Bug#503495: inn2: SSL-Documentation and -Support is wrong/broken

2008-10-26 Thread Michael Holzt
> > This can only be fixed by a.) compile nnrpd with SSL or b.) replace nnrpd > > with a wrapper or alternatives. > c) run nnrpd from inetd. This is not possible without the use of a secondary ip address. As i already said, innd listens on port 119 and will hand over readers to nnrpd. For most use

Bug#503495: inn2: SSL-Documentation and -Support is wrong/broken

2008-10-26 Thread Marco d'Itri
On Oct 26, Michael Holzt <[EMAIL PROTECTED]> wrote: > > Also, upstream strongly believes that nnrpd should really be started > > from inetd. > I believe you are talking about NNTPS which is on a different port (563) on > which inetd can listen and involke nnrpd/nnrpd-ssl with option -S. STARTTLS >

Bug#503495: inn2: SSL-Documentation and -Support is wrong/broken

2008-10-26 Thread Michael Holzt
> Also, upstream strongly believes that nnrpd should really be started > from inetd. I believe you are talking about NNTPS which is on a different port (563) on which inetd can listen and involke nnrpd/nnrpd-ssl with option -S. STARTTLS on the other hand "upgrades" an unencrypted reader connection

Bug#503495: inn2: SSL-Documentation and -Support is wrong/broken

2008-10-26 Thread Marco d'Itri
On Oct 26, Michael Holzt <[EMAIL PROTECTED]> wrote: > I can surely send a patch. But to be able to do this, i need a decision from > you how you want to have the STARTTLS issue fixed. I don't know why you are > currently building a nnrpd binary without SSL support and a nnrpd-ssl binary > with

Bug#503495: inn2: SSL-Documentation and -Support is wrong/broken

2008-10-26 Thread Michael Holzt
> Send a patch. I have no time to work on this, or even to determine how > much of your report is correct. I can surely send a patch. But to be able to do this, i need a decision from you how you want to have the STARTTLS issue fixed. I don't know why you are currently building a nnrpd binary wi

Bug#503495: inn2: SSL-Documentation and -Support is wrong/broken

2008-10-26 Thread Marco d'Itri
Send a patch. I have no time to work on this, or even to determine how much of your report is correct. -- ciao, Marco signature.asc Description: Digital signature

Bug#503495: inn2: SSL-Documentation and -Support is wrong/broken

2008-10-26 Thread Michael Holzt
Package: inn2 Version: 2.4.5-2 Severity: normal README.Debian.gz contains some information regarding SSL support but it turns out that whats written there is simply wrong, also the SSL support in the package is completely broken anyway. 1. It is told that one needs a CA cert in /etc/news/nnrpd-c