NNTPS pointers / NNSP

[Grant Taylor]

On 10/27/21 3:27 PM, Julien ÉLIE wrote:
> Hi Grant,

Hi Julien,

> Awesome!

:-)

> It's worth adding that information in our FAQ if you're OK with that.

Agreed.  Yes, I'm okay with it.

Though I might suggest holding off for a little while longer.  I have 
managed to use iproute2 policy based routing and stunnel (no iptables 
required) to get INN to act as a client to a TLS enabled NNSP (NNTPS) 
server.

I'd like to spend some more time working on things, or discuss what I've 
done with someone else interested in reproducing what I've done.  Use 
that effort to make the directions consistent.

E.g. is iptables connection marking required or not?  --  iptables or 
fancier iproute2 PBR rules achieve the same goal.  Also, compare and 
contrast stunnel with socat.  The latter of the two sets are how I did 
the client portion.

> I can reference the iptables commands you found out.  Any other 
> configuration to mention?

Ya.  More details on the client and unifying of the server (previous 
message) and client (yet to be fully described) methods.

But, yes, the spirit is sharing this so that others can utilize it if 
they so choose.



-- 
Grant. . . .
unix || die

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4013 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.isc.org/pipermail/inn-workers/attachments/20211027/0da5e009/attachment.bin>