You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pullnews does not currently support TLS connections. An option to activate it for downstream servers may be useful. We can already configure a port for the downstream server (via -p or -s), but not implicit TLS. As Net::NNTP natively provides a function to activate it, it should be easy to support it in pullnews.
As for upstream servers, pullnews.marks could use the following syntax:
server[:port][_TLS] [username password]
so as to ask for implicit TLS and/or a different port.
Make sure that server is correctly parsed, as it may contain colons (if written as an IPv6 address).
We would had:
news.server.com:563_TLS
news.server.com:433
The text was updated successfully, but these errors were encountered:
Implicit and explicit TLS support can now be negotiated by pullnews for
connections to upstream servers configured in pullnews.marks, and to
the downstream server specified in the -s flag.
Also, a port can be specified for connections to upstream servers (it
was already possible for the downstream server).
close#256
pullnews
does not currently support TLS connections. An option to activate it for downstream servers may be useful. We can already configure a port for the downstream server (via-p
or-s
), but not implicit TLS. AsNet::NNTP
natively provides a function to activate it, it should be easy to support it inpullnews
.As for upstream servers, pullnews.marks could use the following syntax:
so as to ask for implicit TLS and/or a different port.
Make sure that server is correctly parsed, as it may contain colons (if written as an IPv6 address).
We would had:
The text was updated successfully, but these errors were encountered: