Héctor Abreu <inv...@invalid.invalid> wrote:
> slrn -n -h
news.gmane.org -f ~/.jnewsrc-gmane
You might prefer to use snews://
news.gmane.org as your host instead.
Your current connection between slrn and
news.gmane.org is in the
clear, unencrypted. snews://
news.gmane.org will be encrypted and keep
intermediaries (such as your ISP) from modifying data en route. Some
ISPs do this with webpages and it would be easy to do this with
netnews articles (though I know of no reports of this being done now).
I say deny them the opportunity right from the start.
> I noticed in the other reply the server
blaine.gmane.org , should I
> use that server as an alternative if I experience any problem with
>
news.gmane.org ? The latter is the only one I knew about until now.
I would only recommend switching servers if you know the alternative
server uses the same article numbering base, i.e. if
news.gmane.org is
merely a DNS cname (alias, for lack of a better term) for
blaine.gmane.org, or if you know that the two share the same article
spool then this switch should be okay.
In the case of a DNS cname there should be no reason one server works
while the other doesn't (except for DNS updates as I mentioned before)
since they both resolve to the same host.
If the two hosts ever resolve to different IPs, you probably would be
better off having two newsrc files, one for each server. Because the
two servers might use different article numbers for the same article
and using the same newsrc will give undesirable results (including
missing articles).
> 1.0.2, from the Debian (actually Devuan) repositories.
That version is out of date now but might be recent enough to work
well. Consider compiling s-lang and slrn yourself or getting slrn from
Debian's repos. Debian GNU/Linux carries 1.0.3+dfsg-1 which is current
as I type this.
> Thank you very much for the follow-up.
Sure, happy to help.