Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 23 |
Nodes: | 6 (0 / 6) |
Uptime: | 52:04:43 |
Calls: | 583 |
Files: | 1,139 |
Messages: | 111,529 |
Are there any other users of signcontrol.py except Julien |elie for fr.*
and what PGP/GPG versions do you use?
TIA
In signcontrol.py, I found the origin of the stray "=" prepended to the key ID:
| if passphrase:
| os.system(
| config["PROGRAM_GPG"]
| + " --emit-version --no-comments --no-escape-from-lines"
| ' --no-throw-keyids --armor --detach-sign --local-user "='
| + config["ID"] ^^^^^^^^^^^^^^^^
| + '" --no-tty --passphrase "'
| + passphrase
| + '" --output '
| + file_message
| + ".pgp "
| + flag
| + " "
| + file_message
| + ".txt"
| )
| else:
| os.system(
| config["PROGRAM_GPG"]
| + " --emit-version --no-comments --no-escape-from-lines"
| ' --no-throw-keyids --armor --detach-sign --local-user "='
| + config["ID"] ^^^^^^^^^^^^^^^^
| + '" --output '
| + file_message
| + ".pgp "
| + flag
| + " "
| + file_message
| + ".txt"
| )
The same problem exists in signcontrol,py V 1.5.0
I checked the man pages for all versions of GnuPG that exist on the Eternal-September and --local-user is documented as an option in all
of them, i.e. "--local-user control@eternal-september.org".
Is there actually a version of GnuPG that understands "--local-user=control@eternal-september.org"
or is this just a typo that went unnoticed until now?
I recently determined that I should resume issuing regular checkgroup
control messages for eternal-september.* and also give signcontrol.py
a try, so I downloaded signcontrol.py V 1.5.1 and create a signcontrol.conf for the Eternal-September environment. Unfortunately, signcontrol.py complained
about being unable to find the secret key for ID "=control@eternal-september.org",
which was correct as the actual ID contained in secring.gpg and configured in signcontrol.conf is "control@eternal-september.org" (without the equal sign).
In signcontrol.py, I found the origin of the stray "=" prepended to the key ID
Are there any other users of signcontrol.py except Julien |elie for fr.*
and what PGP/GPG versions do you use?
The problem is the combination of rCy=rCO and rCy rCy. Either will work, but not
both.
The bug was introduced in commit d59c843f3259. The change was from
rCy-u IDrCO to rCy--local-user =IDrCO, when it should be either rCy--local=user=IDrCO or rCy--local-user IDrCO.
Are you sure the ID is control@eternal-september.org and not news@eternal-september.org as mentioned in https://www.eternal-september.org/control/pgpkey.txt?_________________________________________________________
control.ctl entries also use news@eternal-september.org:
newgroup:*:eternal-september.*:drop
rmgroup:*:eternal-september.*:drop checkgroups:news@eternal-september.org:eternal-september.*:verify-news@eternal-september.org
newgroup:news@eternal-september.org:eternal-september.*:verify-news@eternal-september.org
rmgroup:news@eternal-september.org:eternal-september.*:verify-news@eternal-september.org
Where did you get the link to the key and the control.ctl entry from?
The new PGP keys use GnuPG 2.x and there are separate keys for different purposes
(NoCem, control messages).
Thanks to your detailed explanations in your reply to Richard I was able to sort things out and now signcontrol works as expected.
Hi Wolfgang,
Where did you get the link to the key and the control.ctl entry from?
The new PGP keys use GnuPG 2.x and there are separate keys for different purposes
(NoCem, control messages).
It was added in January 2010: >https://github.com/rra/control-archive/commit/4781fd1587147bea2a22bf7bfdd4b7fe63de298f
Looking at what happened near that time in news.admin.hierarchies, I
found out:
https://groups.google.com/g/news.admin.hierarchies/c/hCFUMgU4s3M
There's a message from you on January, 2nd in that thread :-)
From: Colin Macleod <user7@newsgrouper.org.invalid>
Newsgroups: rocksolid.nodes.help,news.admin.peering
Subject: Re: ** ANNOUNCEMENT: First go-pugleaf Node Online **
Date: Wed, 16 Jul 2025 16:32:55 GMT
Message-ID: <1752683575-7@newsgrouper.org>
...
You might like to know that I'm currently working on improving the archive >search facility of my newsgrouper.org site so that you will be able to
send links to articles/threads found via search to other people. These
will be viewable without registration.
From: Ray Banana <rayban@banana.shacknet.nu>
Newsgroups: news.admin.hierarchies
Subject: Re: control-archive 1.2.0 released
Date: Sat, 02 Jan 2010 11:47:10 +0100
Should your new key be declared in control.ctl and PGPKEYS?
https://www.eternal-september.org/control-eternal-september.asc
pub rsa4096 2025-07-16 [SC]
17A7E98E3038BE35428F30E4F53C21EEF3D2EA49
uid [ inconnue] Control <control@eternal-september.org>
Thanks to your detailed explanations in your reply to Richard I was able to >> sort things out and now signcontrol works as expected.
Looks like the expected flag was "=Control <control@eternal-september.org>".
Beware that modern versions of INN cope with UIDs containing spaces
but other legacy news servers may not.
Rationale in Section 3 of:
https://www.eyrie.org/~eagle/faqs/usenet-hier.html
Should your new key be declared in control.ctl and PGPKEYS?
https://www.eternal-september.org/control-eternal-september.asc
pub rsa4096 2025-07-16 [SC]
17A7E98E3038BE35428F30E4F53C21EEF3D2EA49
uid [ inconnue] Control <control@eternal-september.org>
Yes, please.
Looks like the expected flag was "=Control <control@eternal-september.org>".
What confused me was the unexpected "=" strict match indicator that is
always added by signcontrol.py ;-)
"If you're using GnuPG, in order to not get any spaces into the user ID,
you need to use gpg --gen-key --allow-freeform-uid, enter the desired
^^^^^^^^^^^^^^^^^
user ID as the name, and then press Enter when asked for an e-mail ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
address or comment. The recommended user ID is the e-mail address of the ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sender, but it has to be entered as the name or GnuPG will not generate ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
the right user ID. A later version of pgpverify will hopefully make this ^^^^^^^^^^^^^^^^^^
unnecessary, but older versions will be around for quite some time."
This caveat also applies to signcontrol.py's
"Manage my PGP keys (generate/import/export/remove/revoke)"
The information will normally be updated in the next control-archiveShould your new key be declared in control.ctl and PGPKEYS?
https://www.eternal-september.org/control-eternal-september.asc
pub rsa4096 2025-07-16 [SC]
17A7E98E3038BE35428F30E4F53C21EEF3D2EA49
uid [ inconnue] Control <control@eternal-september.org>
Yes, please.
release by Russ. I have opened a issue to remember that:
https://github.com/rra/control-archive/issues/9
Isn't the current wording when running that function enough? I do not[...]
see more information to add, unless I am mistaken?
----------------------------------------------------------------------- Please put the e-mail address from which you will send control articles
in the key ID (the real name field). And leave the other fields blank,
for better compatibility with Usenet software.
Choose a 3072-bit or 4096-bit RSA key which *never expires*.
You should also provide a strong passphrase, for security reasons.
There is no need to edit the key after it has been generated.
Please note that the key generation may not finish if it is launched
on a remote server, owing to a lack of enough entropy. Use your own
computer instead and import the key on the remote one afterwards. -----------------------------------------------------------------------