Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Signed release tags (Julien ?LIE)
2. Re: NNTPS pointers / NNSP (Julien ?LIE)
----------------------------------------------------------------------
Message: 1
Date: Sun, 17 Apr 2022 22:49:57 +0200
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Signed release tags
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi all,
I've just regenerated our 32 release tags. They're now all signed tags.
The public PGP key used is this one:
https://keys.openpgp.org/vks/v1/by-fingerprint/0B2AA9D3B9C9447C9B04C2977C54D173C671B7F6
% gpg --search-keys "0B2AA9D3B9C9447C9B04C2977C54D173C671B7F6"
gpg: data source: https://keys.openpgp.org:443
(1) 4096 bit RSA key 7C54D173C671B7F6, cr???: 2022-03-08
All the release tags now appear as Verified in the GitHub interface:
https://github.com/InterNetNews/inn/tags
As I've force-pushed the signed tags, replacing the previous ones, those
who have a clone of the repository will need updating their local tags:
git fetch --prune-tags
P.-S.: I've also renamed the 2.2.0 tag to 2.2 as that version was really
2.2 (and so was its name in the release notes too).
--
Julien ?LIE
? Audentes fortunat iuvat. ? (Virgile)
------------------------------
Message: 2
Date: Mon, 18 Apr 2022 09:33:28 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: NNTPS pointers / NNSP
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Grant,
> Much of my testing has been on HTTP/80 vs HTTPS/443 as that's what I
> spend more time speaking.? But I have every single expectation that the
> same methodology can be directly applied to NNTP/119, NNPS/433, and
> NNTPS/563.
[...]
> I'm ultimately keying off of remote IP and remote port pairs. As
> such, I expect that INN(d) et al. will remain configured just like
> they are today and will simply have something outside of them do the
> TLS helper function, mid-span. }:-)
Have you made any progress on your tests? (including NNTP and NNSP ports)
>> You could also discuss that in news.software.nntp; maybe other people
>> are willing to experiment too.
>
> Good idea.
I believe it could be an interesting discussion there (news.software.nntp).
--
Julien ?LIE
??? Le bureau des renseignements??
? Sais pas. Adressez-vous aux renseignements, ils vous
renseigneront.?? (Ast?rix)
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 140, Issue 3
*******************************************
