> 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. As you know, innd listens on port 119. For readers it will invoke nnrpd and this can't be configured. nnrpd does not know about the STARTTLS command, nnrpd-ssl does. Therefore on debian STARTTLS can not work because the binary /usr/lib/news/bin/nnrpd is not compiled with SSL. This can only be fixed by a.) compile nnrpd with SSL or b.) replace nnrpd with a wrapper or alternatives. > I do care. Do you care enough to help? I do. I have now explained for the third time what the problem is, and i still need a decision how you want to have the problem fixed. Gruss Michael -- It's an insane world, but i'm proud to be a part of it. -- Bill Hicks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
