pan 0.146 no longer connects with SSL, still connects with unencrypted port 119
Arch Linux pan-0.146-1
I had been connecting successfully with the same SSL server profile since 2016. This past week, I could no longer connect via SSL. Changing the port back to 119 resulted in a successful unencrypted connection.
After a few days of this, I checked with my Usenet provider. They confirmed that pan was creating the socket, but not sending the username/password handshake.
`Our logs showed your SSL connection was established, but your news client exited before sending userid/passwd. Please check your client settings.
Apr 26 16:12:39 news1 nnrpd[8502]: 104.190.210.161 connect
Apr 26 16:12:39 news1 nnrpd[8502]: 104.190.210.161 SSL Connection Apr 26
16:12:39 news1 nnrpd[8502]: 104.190.210.161 exit articles 0:0 groups 0
#(null):
Apr 26 16:12:39 news1 nnrpd[8502]: 104.190.210.161 times user 0.025 system
0.006 elapsed 27.181 #(null):`
I checked my pacman update logs and noticed a gnutls update that happened within the timeframe when pan stopped connecting via SSL. I incorrectly assumed that the update broke pan and the package needed to be rebuilt. After filing an Arch bug (https://bugs.archlinux.org/task/66473), I tried downgrading gnutls to 3.6.12 and 3.6.11. Eventually, I updated back to gnutls-3.6.13-1 and rebuilt the pan package myself, but had no success.
I've attached the output of 'pan --debug --verbose' using ports 119 pan.119.log and 563 pan.563.log
While the package was building, I came across numerous deprecated calls - I don't know if one of those is to blame or not. As noted previously, I have been connecting successfully since 2016 with SSL on port 563.