I need to be able to explain succinctly how a INN peer should connect
to a Rocksolid Light peer if such is possible.
Rocksolid Light (rslight) peers and syncs using client commands instead
of innfeed. It is very simple to configure. Rocksolid Light will peer
with any NNTP peer that has user account authentication. Enter the credentials into the rslight config, list the desired newsgroups, and
away we go. Rslight uses client commands to check, push and pull
articles.
But what if a sysop using INN wants to peer with rslight? Does INN have facility for this at user level? If I sync rslight with a INN peer, only
the rslight peer is doing the synchronization of articles. Does INN have
the facility to do the inverse with a rslight peer?
I configure the rslight cron job to synchronize at randomized
intervals. Ultimately my strategy is to check and synchronize articles
at random intervals from ten to thirty minutes over a tor hidden onion circuit. I would expect a remote peer to do similarly. Randomization of
the synchronization times is a hedge against traffic analysis. Delays
of a few minutes before forwarding buffers connecting clients from
message timing correlation. It is not perfect but it helps and it
increases the cost for eavesdroppers.
The hidden onion circuit is an extra layer of security for the
connections. Each peer I link to would use a different hidden onion
address, and I would give a different hidden onion address to each such
peer. This allows every peer to hide physical location. It also allows
every peer to have a secure, private pipe to only one other peer.
Firstly I need to know how, if possible, to configure INN to
synchronize via client authentication and client commands, without
respect to the kind of network transport.
Secondly I need ideas on how to configure INN to use multiple Tor
hidden onion services, and connect INN to unique remote onion services
on a per-peer basis.
Please advise with concrete information.
I configure the rslight cron job to synchronize at randomized
intervals. Ultimately my strategy is to check and synchronize
articles at random intervals from ten to thirty minutes over a tor
hidden onion circuit. I would expect a remote peer to do similarly. Randomization of the synchronization times is a hedge against
traffic analysis. Delays of a few minutes before forwarding buffers connecting clients from message timing correlation. It is not
perfect but it helps and it increases the cost for eavesdroppers.
This should be simple with just shell scripts.
On Thu, 28 Sep 2023 01:58:43 -0500
Syber Shock <admin@sybershock.com> wrote:
But what if a sysop using INN wants to peer with rslight? Does INN have
facility for this at user level? If I sync rslight with a INN peer, only
the rslight peer is doing the synchronization of articles. Does INN have
the facility to do the inverse with a rslight peer?
I am not aware of any feature of INN that allows it to act as a nnrpd client. That doesn't mean there is no such feature, just that I am not aware of it.
The hidden onion circuit is an extra layer of security for the
connections. Each peer I link to would use a different hidden onion
address, and I would give a different hidden onion address to each such
peer. This allows every peer to hide physical location. It also allows
every peer to have a secure, private pipe to only one other peer.
Makes sense.
Firstly I need to know how, if possible, to configure INN to
synchronize via client authentication and client commands, without
respect to the kind of network transport.
Secondly I need ideas on how to configure INN to use multiple Tor
hidden onion services, and connect INN to unique remote onion services
on a per-peer basis.
Please advise with concrete information.
My setup avoids crontab and uses systemd init to spawn
What is the reason that you use systemd ? Or just by chance ?
My setup avoids crontab and uses systemd init to spawn
On Thu, 28 Sep 2023 01:58:43 -0500
Syber Shock <admin@sybershock.com> wrote:
snip
Firstly I need to know how, if possible, to configure INN to
synchronize via client authentication and client commands, without
respect to the kind of network transport.
Secondly I need ideas on how to configure INN to use multiple Tor
hidden onion services, and connect INN to unique remote onion services
on a per-peer basis.
Please advise with concrete information.
On Thu, 28 Sep 2023 01:58:43 -0500
Syber Shock <admin@sybershock.com> wrote:
snip
But what if a sysop using INN wants to peer with rslight? Does INN have
facility for this at user level? If I sync rslight with a INN peer, only
the rslight peer is doing the synchronization of articles. Does INN have
the facility to do the inverse with a rslight peer?
I am not aware of any feature of INN that allows it to act as a nnrpd client. That doesn't mean there is no such feature, just that I am not aware of it.
Anyway, pullnews will allow you to poll a nnrpd server and feed to
another, and it works quite reliably.
https://www.eyrie.org/~eagle/software/inn/docs/pullnews.html
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 365 |
Nodes: | 16 (3 / 13) |
Uptime: | 28:59:23 |
Calls: | 7,790 |
Calls today: | 5 |
Files: | 12,917 |
Messages: | 5,750,860 |