Re: Retro is the New Neo (Again) : Retro and Smol Tools for the

On 2023-11-18, Syber Shock <[email protected]> wrote:
> On Sat, 18 Nov 2023 06:23:47 -0600
> Syber Shock <[email protected]> wrote:
>
>> On Sat, 18 Nov 2023 11:07:29 -0000 (UTC)
>> Bozo User <[email protected]> wrote:
>> 
>> <snip>
>> 
>> > Citadel can be accesed thru NNTP, really useful with slrnpull.
>> > Ditto with DOVE/FIDOnet from syncrho.net
>> 
>> Where can I find documentation for peering a Citadel server with
>> Usenet or another Citadel or NNTP peer? The link below says it has
>> full NNTP exposure but I find documentation lacking in my search.
>> 
>> "In theory, Citadel supports Network News Transfer Protocol (NNTP).
>> Regrettably, tests show that the feature does not work. According to
>> the developer, the feature was never fully implemented."
>> 
>> https://www.admin-magazine.com/Archive/2020/57/An-overview-of-the-Citadel-BBS/(offset)/6
>> 
>> "If you expose the standard, text mode NNTP interface to citadel,
>> without even full implementation of the NNTP server, then you have
>> tons of NNTP clients that can recover the Citadel data and look at it
>> in ANY way they please, and post to any room without even running the
>> webcit hybrid."
>> 
>> https://www.mail-archive.com/[email protected]/msg09329.html
>> 
>> So in theory NNTP should work, or NNTP is not really implemented.
>> Which is it? Where do I get the docs?
>
> Earlier documentation said that NNTP(S) were on ports 70 and 71. I
> could not connect on those ports.
>
> I prodded port 119:
>
> ~$ telnet uncensored.citadel.org 119
> Connected to uncensored.citadel.org.
> Escape character is '^]'.
> 200 uncensored.citadel.org NNTP Citadel server is not finished yet
> help
> 100 This is the Citadel NNTP service.
> RTFM http://www.ietf.org/rfc/rfc3977.txt
> list
> 215 list of newsgroups follows
> ctdl....said+20no+20one+20ever 2099321056 3549663 n
> ctdl.a+2fv+20talk 2099348353 3552509 n
> ctdl.ancient+20computing 2099369202 3567580 n
> ctdl.anime+2fcomics 2099348086 3584955 n
> ctdl.annoyances 2099367489 3606152 n
> ctdl.bbs+20list+20-+20other+20systems+20and+20citadels+20 2099342736
> 4638801 n ctdl.boom+20sticks 2099368993 3605197 n
> [truncated]
>
> Notice: "RTFM", but no docs on config and giving client / peer
> instructions.
>
> I prodded with TLS:
>
> ~$ openssl s_client -verify_quiet -connect uncensored.citadel.org:563 |
> grep TLS | head -n 16
> New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
>     Protocol  : TLSv1.3
>     Cipher    : TLS_AES_256_GCM_SHA384
>     TLS session ticket lifetime hint: 7200 (seconds)
>     TLS session ticket:
>     Protocol  : TLSv1.3
>     Cipher    : TLS_AES_256_GCM_SHA384
>     TLS session ticket lifetime hint: 7200 (seconds)
>     TLS session ticket: [truncated]
>
> So it is using TLS 1.3, which means that Citadel is not slouching on
> connection security.
>
> I still would like documentation for all the NNTP features and
> limitations. Does anyone know where to find it?
>
> Web front end, Putty BBS access, groupware, mailing lists, and NNTP all
> bundled together sounds useful. It could be a dream or a nightmare.
>

synchro.net port 119 (plain) or 563 (tls)