Path: ...!weretis.net!feeder8.news.weretis.net!news.trigofacile.com!.POSTED.2a01cb080adc1100042c67ca0935b4ab.ipv6.abo.wanadoo.fr!not-for-mail
From: =?UTF-8?Q?Julien_=C3=89LIE?= <iulius@nom-de-mon-site.com.invalid>
Newsgroups: news.admin.hierarchies
Subject: Re: Upgrading/changing from PGP to GnuPG for nl.*
Date: Wed, 22 May 2024 18:07:30 +0200
Organization: Groupes francophones par TrigoFACILE
Message-ID: <v2l582$u61p$1@news.trigofacile.com>
References: <sCIsAw.qvz0@a3.nl.invalid> <v0fv1o$62di$1@news.trigofacile.com>
 <sCnK64.wwA3@a3.nl.invalid> <v0o2j7$bvvl$1@news.trigofacile.com>
 <sDuJAC.1oJ2o@a3.nl.invalid>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 22 May 2024 16:07:30 -0000 (UTC)
Injection-Info: news.trigofacile.com; posting-account="julien"; posting-host="2a01cb080adc1100042c67ca0935b4ab.ipv6.abo.wanadoo.fr:2a01:cb08:adc:1100:42c:67ca:935:b4ab";
	logging-data="989241"; mail-complaints-to="abuse@trigofacile.com"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:5JOfEqeOi9o8lK24fnnUKVowXVI= sha256:1/xyGALE+xz5FSif/b6xrei+XAfpeNHYCFifWE3dzqQ=
	sha1:nhJRyAO0CrVCypA5UxDh1UrR7Gg= sha256:BHFwP6LOVNyN0+bFZvO/qkKOuqLKmCL0WlDj8Cxri8s=
In-Reply-To: <sDuJAC.1oJ2o@a3.nl.invalid>
Bytes: 3826
Lines: 57

Hi Adri,

>> For C News, from what I heard, it uses a file named controlperm.
>> Do you confirm a valid syntax for controlperm would now be:
>>
>> nl nl-admin@stack.nl c pv nl.newsgroups
>> nl nl-admin@stack.nl n pv nl.newsgroups
>> nl nl-admin@stack.nl r pv nl.newsgroups
>
> I have only one line in controlperm:
> 
> nl		nl-admin@stack.nl		nrc	p	nl.newsgroups
> 
> Regarding this,
> this is what I found in /var/news/bin/ctl/{checkgroups,{new,rm}group}:
> 
> # subject to $NEWSCTL/controlperm:  four fields per line, first
> # a newsgroup pattern, second an author name (or "any"), third a set of
> # operations ("n" newgroup, "r" rmgroup, "c" checkgroups), and fourth a set of
> # flags ("p" do it iff poster's identity is pgpverified,
> # "y" do it, "n" don't, "q" don't report at all, "v" include
> # entire control message in report) (default "yv"); the "p" and "n" flags may
> # be followed by the ID of the person permitted to pgpverify;
> # the pgpverify program (not supplied) is presumed to be in $NEWSBIN

Thanks for this valuable information.



> In the meantime, I've downloaded the latest version of pgpverify (1.30) from
> https://ftp.isc.org/pub/pgpcontrol/pgpverify, but the version that goes with
> my operating system (Fedora 40), /usr/libexec/news/pgpverify from INN-2.7.1,
> says it is version 1.31.  So what is going on here?
> 
> They are dated:
> # Version 1.30, 2018-01-21
> # Version 1.31, 2022-06-12
> 
> # Changes from 1.30 -> 1.31
> # -- Add a $gpg_has_allow_weak_digest_algos_flag variable to specify whether
> #    gpg supports the --allow-weak-digest-algos flag.  This variable will
> #    be overriden by INN::Config, if used.  GnuPG 1.4.20 and 2.0.23 introduced
> #    this flag, necessary to verify the signatures of old PGP keys still in
> #    use for some hierarchies.
> # -- Using at least GnuPG 1.4.20 or 2.1.0 is no longer required; this version
> #    of pgpverify will still work with previous versions of GnuPG.  However,
> #    only GnuPG 1.x and 2.0.x will be able to validate signatures made with
> #    old PGP keys.

Version 1.31 included in INN 2.7.0 and 2.7.1 is the latest one.  It just 
had not been reflected upstream yet.  It will probably be done along 
with the next update of ftp.isc.org stuff with your new key for nl.* :)

-- 
Julien ÉLIE

« Avez-vous remarqué qu'à table les mets que l'on vous sert vous mettent
   les mots à la bouche ? » (Raymond Devos)