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 > on the other hand "upgrades" an unencrypted reader connection on port 119 to > an encrypted one by sending the STARTTLS command. I am well aware about the difference between SSL-wrapped TCP and STARTTLS.
> 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. b is not an interesting solution. To implement a and ditch nnrpd-ssl I would like to see data showing that SSL support does not use more memory as long as it's not used (which probably is true. nnrpd-ssl used to be in a different package for other reasons, so maybe it's time to fold it in). -- ciao, Marco
signature.asc
Description: Digital signature
