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:
pullnewsdoes 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-por-s), but not implicit TLS. AsNet::NNTPnatively 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: