nnrpd: can't bind (Invalid argument)

[Russ Allbery]

Forrest Aldrich <forrie at forrie.com> writes:

> For nnrpd+ssl I installed a self-signed cert.   I went to test and I see 
> this in the logs:

> Sep 13 13:51:17 news nnrpd[30442]: error initializing TLS: [CA_file: 
> /usr/local/news/lib/cert.pem] [CA_path: /usr/local/news/lib] [cert_file: 
> /usr/local/news/lib/cert.pem] [key_file: /usr/local/news/lib/cert.pem]
> Sep 13 13:51:17 news nnrpd[30442]:  times user 0.000 system 0.004 idle 
> 0.000 elapsed 0.005
> Sep 13 13:51:17 news nnrpd[30442]:  time 4 nntpwrite 0(1)
> Sep 13 13:52:35 news nnrpd[30448]: starttls: TLSv1 with cipher 
> DHE-RSA-AES256-SHA (256/256 bits) no authentication
> Sep 13 13:52:35 news nnrpd[30448]: myserver.com (xx.xx.xx.106) connect

> It's not clear to me that SSL is working with the message "no 
> authentication".

That just means that you're not doing SSL-based public key authentication,
which is to be expected.

> How can we tell if this is actually working and not falling back to
> normal nnrpd.

It wouldn't say "starttls" if SSL weren't working.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.