readers issue

Julien ÉLIE julien at trigofacile.com
Thu Dec 17 20:25:04 UTC 2015


The Doctor,

> Using slrn in ssl mode
>
> Dec 16 16:51:40 ns2 nnrpd[4123]: starttls: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) no authentication
> Dec 16 16:51:40 ns2 nnrpd[4123]: doctor.nl2k.ab.ca (204.209.81.1) connect - port 119
> Dec 16 16:51:40 ns2 nnrpd[4123]: doctor.nl2k.ab.ca res <local>@nl2k.ab.ca
> Dec 16 16:51:40 ns2 nnrpd[4123]: doctor.nl2k.ab.ca match_user <local>@nl2k.ab.ca <local>@nl2k.ab.ca
>
> auth "local" {
>      hosts: "204.209.81.0/24"
>      default: "<local>@nl2k.ab.ca"
> }
>
> access "local" {
>      users: "<local>@nl2k.ab.ca"
>      newsgroups: "*"
> }
>
> All right why are SSL clients suddenly not working.

You were correctly identified as "<local>@nl2k.ab.ca", according to your 
logs.
Why do you say SSL clients no longer work?  What happens for them?  Is 
slrn throwing an error?  Is your SSL certificate still valid?

-- 
Julien ÉLIE

« – Il est parti comme il est venu…
   – Il ne faisait que passer… » (Astérix)


More information about the inn-workers mailing list