Why Am I getting

Syslog error messages:
Nov 22 01:00:03 gallifrey nocem[29276]: Article <ujkce3$ta8$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 02:30:03 gallifrey nocem[29276]: Article <ujkhmq$96t$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 03:30:03 gallifrey nocem[29276]: Article <ujkl7a$hgt$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 04:30:03 gallifrey nocem[29276]: Article <ujkonq$qb4$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 05:00:03 gallifrey nocem[29276]: Article <ujkqg3$upe$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 07:00:03 gallifrey nocem[29276]: Article <ujl1h3$f2q$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 07:30:03 gallifrey nocem[29276]: Article <ujl39b$k0m$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 08:30:03 gallifrey nocem[63150]: Article <ujl6pq$sms$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 09:00:03 gallifrey nocem[63150]: Article <ujl8i2$1ca$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 09:30:03 gallifrey nocem[63150]: Article <ujlaaa$5ck$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 10:30:04 gallifrey nocem[63150]: Article <ujldqr$es3$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 11:00:03 gallifrey nocem[63150]: Article <ujlfj2$jhc$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 11:30:03 gallifrey nocem[63150]: Article <ujlhbb$nth$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
Nov 22 12:00:03 gallifrey nocem[63150]: Article <ujlj3i$sq2$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2

--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Merry Christmas 2023 and Happy New year 2024 Beware https://mindspring.com

doctor@doctor.nl2k.ab.ca (The Doctor) writes:

> Why Am I getting
>
> Nov 22 01:00:03 gallifrey nocem[29276]: Article <ujkce3$ta8$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2

My first, off the top of my head guess, would be that you're trying to
use gpgv1 instead of gpgv2.

doctor@doctor.nl2k.ab.ca (The Doctor) writes:

> Why Am I getting
>
> Nov 22 01:00:03 gallifrey nocem[29276]: Article <ujkce3$ta8$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2

My first, off the top of my head, guess would be that you're trying to
use gpgv1 instead of gpgv2.

In article <87wmu838e0.fsf@asus-x205ta.furie.org.uk>,
Tom Furie <tom@furie.org.uk> wrote:
>doctor@doctor.nl2k.ab.ca (The Doctor) writes:
>
>> Why Am I getting
>>
>> Nov 22 01:00:03 gallifrey nocem[29276]: Article
><ujkce3$ta8$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status
>2
>
>My first, off the top of my head, guess would be that you're trying to
>use gpgv1 instead of gpgv2.

Could be

ls /usr/local/bin/*gpg*
/usr/local/bin/gpg /usr/local/bin/gpgme-json
/usr/local/bin/gpg-agent /usr/local/bin/gpgme-tool
/usr/local/bin/gpg-card /usr/local/bin/gpgparsemail
/usr/local/bin/gpg-connect-agent /usr/local/bin/gpgrt-config
/usr/local/bin/gpg-error /usr/local/bin/gpgscm
/usr/local/bin/gpg-error-config /usr/local/bin/gpgsm
/usr/local/bin/gpg-wks-client /usr/local/bin/gpgsplit
/usr/local/bin/gpg-wks-server /usr/local/bin/gpgsplit2
/usr/local/bin/gpg-zip /usr/local/bin/gpgtar
/usr/local/bin/gpg2 /usr/local/bin/gpgv
/usr/local/bin/gpgconf /usr/local/bin/gpgv2
/usr/local/bin/gpgme-config

--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Merry Christmas 2023 and Happy New year 2024 Beware https://mindspring.com

In article <ujnlbb$2jj3$3@gallifrey.nk.ca>,
The Doctor <doctor@doctor.nl2k.ab.ca> wrote:
>In article <87wmu838e0.fsf@asus-x205ta.furie.org.uk>,
>Tom Furie <tom@furie.org.uk> wrote:
>>doctor@doctor.nl2k.ab.ca (The Doctor) writes:
>>
>>> Why Am I getting
>>>
>>> Nov 22 01:00:03 gallifrey nocem[29276]: Article
>><ujkce3$ta8$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status
>>2
>>
>>My first, off the top of my head, guess would be that you're trying to
>>use gpgv1 instead of gpgv2.
>
>Could be
>
>ls /usr/local/bin/*gpg*
>/usr/local/bin/gpg /usr/local/bin/gpgme-json
>/usr/local/bin/gpg-agent /usr/local/bin/gpgme-tool
>/usr/local/bin/gpg-card /usr/local/bin/gpgparsemail
>/usr/local/bin/gpg-connect-agent /usr/local/bin/gpgrt-config
>/usr/local/bin/gpg-error /usr/local/bin/gpgscm
>/usr/local/bin/gpg-error-config /usr/local/bin/gpgsm
>/usr/local/bin/gpg-wks-client /usr/local/bin/gpgsplit
>/usr/local/bin/gpg-wks-server /usr/local/bin/gpgsplit2
>/usr/local/bin/gpg-zip /usr/local/bin/gpgtar
>/usr/local/bin/gpg2 /usr/local/bin/gpgv
>/usr/local/bin/gpgconf /usr/local/bin/gpgv2
>/usr/local/bin/gpgme-config
>

The question then in INN, how does one set the correct pgp executable?

>--
>Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
>Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
>Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
>Merry Christmas 2023 and Happy New year 2024 Beware https://mindspring.com

--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Merry Christmas 2023 and Happy New year 2024 Beware https://mindspring.com

On Nov 24, 2023 at 10:47:19 AM CST, "The Doctor" <The Doctor> wrote:

>> Could be
>>
>> ls /usr/local/bin/*gpg*
>> /usr/local/bin/gpg /usr/local/bin/gpgme-json
>> /usr/local/bin/gpg-agent /usr/local/bin/gpgme-tool
>> /usr/local/bin/gpg-card /usr/local/bin/gpgparsemail
>> /usr/local/bin/gpg-connect-agent /usr/local/bin/gpgrt-config
>> /usr/local/bin/gpg-error /usr/local/bin/gpgscm
>> /usr/local/bin/gpg-error-config /usr/local/bin/gpgsm
>> /usr/local/bin/gpg-wks-client /usr/local/bin/gpgsplit
>> /usr/local/bin/gpg-wks-server /usr/local/bin/gpgsplit2
>> /usr/local/bin/gpg-zip /usr/local/bin/gpgtar
>> /usr/local/bin/gpg2 /usr/local/bin/gpgv
>> /usr/local/bin/gpgconf /usr/local/bin/gpgv2
>> /usr/local/bin/gpgme-config
>>
>
> The question then in INN, how does one set the correct pgp executable?

I forget the various was to set it besides at 'configure' time, but you can
modify lib/innshellvars.pl:

$gpg = '/usr/local/bin/gpg';

On Nov 24, 2023 at 11:12:54 AM CST, "Jesse Rehmer"
<jesse.rehmer@blueworldhosting.com> wrote:

> On Nov 24, 2023 at 10:47:19 AM CST, "The Doctor" <The Doctor> wrote:
>
>>> Could be
>>>
>>> ls /usr/local/bin/*gpg*
>>> /usr/local/bin/gpg /usr/local/bin/gpgme-json
>>> /usr/local/bin/gpg-agent /usr/local/bin/gpgme-tool
>>> /usr/local/bin/gpg-card /usr/local/bin/gpgparsemail
>>> /usr/local/bin/gpg-connect-agent /usr/local/bin/gpgrt-config
>>> /usr/local/bin/gpg-error /usr/local/bin/gpgscm
>>> /usr/local/bin/gpg-error-config /usr/local/bin/gpgsm
>>> /usr/local/bin/gpg-wks-client /usr/local/bin/gpgsplit
>>> /usr/local/bin/gpg-wks-server /usr/local/bin/gpgsplit2
>>> /usr/local/bin/gpg-zip /usr/local/bin/gpgtar
>>> /usr/local/bin/gpg2 /usr/local/bin/gpgv
>>> /usr/local/bin/gpgconf /usr/local/bin/gpgv2
>>> /usr/local/bin/gpgme-config
>>>
>>
>> The question then in INN, how does one set the correct pgp executable?
>
> I forget the various was to set it besides at 'configure' time, but you can
> modify lib/innshellvars.pl:
>
> $gpg = '/usr/local/bin/gpg';

Errr, also in lib/innshellvars. Someone else will maybe chime in with 'the
right way'.

In article <ujqlim$d8m$1@nnrp.usenet.blueworldhosting.com>,
Jesse Rehmer <jesse.rehmer@blueworldhosting.com> wrote:
>On Nov 24, 2023 at 10:47:19 AM CST, "The Doctor" <The Doctor> wrote:
>
>>> Could be
>>>
>>> ls /usr/local/bin/*gpg*
>>> /usr/local/bin/gpg /usr/local/bin/gpgme-json
>>> /usr/local/bin/gpg-agent /usr/local/bin/gpgme-tool
>>> /usr/local/bin/gpg-card /usr/local/bin/gpgparsemail
>>> /usr/local/bin/gpg-connect-agent /usr/local/bin/gpgrt-config
>>> /usr/local/bin/gpg-error /usr/local/bin/gpgscm
>>> /usr/local/bin/gpg-error-config /usr/local/bin/gpgsm
>>> /usr/local/bin/gpg-wks-client /usr/local/bin/gpgsplit
>>> /usr/local/bin/gpg-wks-server /usr/local/bin/gpgsplit2
>>> /usr/local/bin/gpg-zip /usr/local/bin/gpgtar
>>> /usr/local/bin/gpg2 /usr/local/bin/gpgv
>>> /usr/local/bin/gpgconf /usr/local/bin/gpgv2
>>> /usr/local/bin/gpgme-config
>>>
>>
>> The question then in INN, how does one set the correct pgp executable?
>
>I forget the various was to set it besides at 'configure' time, but you can
>modify lib/innshellvars.pl:
>
> $gpg = '/usr/local/bin/gpg';

Will adjust accordingly.
--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Merry Christmas 2023 and Happy New year 2024 Beware https://mindspring.com

In article <ujqll3$gmu$1@nnrp.usenet.blueworldhosting.com>,
Jesse Rehmer <jesse.rehmer@blueworldhosting.com> wrote:
>On Nov 24, 2023 at 11:12:54 AM CST, "Jesse Rehmer"
><jesse.rehmer@blueworldhosting.com> wrote:
>
>> On Nov 24, 2023 at 10:47:19 AM CST, "The Doctor" <The Doctor> wrote:
>>
>>>> Could be
>>>>
>>>> ls /usr/local/bin/*gpg*
>>>> /usr/local/bin/gpg /usr/local/bin/gpgme-json
>>>> /usr/local/bin/gpg-agent /usr/local/bin/gpgme-tool
>>>> /usr/local/bin/gpg-card /usr/local/bin/gpgparsemail
>>>> /usr/local/bin/gpg-connect-agent /usr/local/bin/gpgrt-config
>>>> /usr/local/bin/gpg-error /usr/local/bin/gpgscm
>>>> /usr/local/bin/gpg-error-config /usr/local/bin/gpgsm
>>>> /usr/local/bin/gpg-wks-client /usr/local/bin/gpgsplit
>>>> /usr/local/bin/gpg-wks-server /usr/local/bin/gpgsplit2
>>>> /usr/local/bin/gpg-zip /usr/local/bin/gpgtar
>>>> /usr/local/bin/gpg2 /usr/local/bin/gpgv
>>>> /usr/local/bin/gpgconf /usr/local/bin/gpgv2
>>>> /usr/local/bin/gpgme-config
>>>>
>>>
>>> The question then in INN, how does one set the correct pgp executable?
>>
>> I forget the various was to set it besides at 'configure' time, but you can
>> modify lib/innshellvars.pl:
>>
>> $gpg = '/usr/local/bin/gpg';
>
>Errr, also in lib/innshellvars. Someone else will maybe chime in with 'the
>right way'.

I wonder if Julien should adjust this accordingly.
--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Merry Christmas 2023 and Happy New year 2024 Beware https://mindspring.com

Hi The Doctor,

>>> Nov 22 01:00:03 gallifrey nocem[29276]: Article
>>> <ujkce3$ta8$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
>>
>> $gpg = '/usr/local/bin/gpg';
>
> I wonder if Julien should adjust this accordingly.

There's no universal path to where binaries are installed, so it cannot
just be hard-coded. When configuring the package, INN tries to find the
appropriate installed binary, if any. Naturally, if you install GnuPG
after INN, it won't have set it up right.

Regarding <ujkce3$ta8$1@rasp.pasdenom.info> signed with the nonobot key,
it should normally work with both GnuPG 1 and GnuPG 2.
I am really unsure the problem comes from that.

Are you certain you have properly imported its key following the
instructions of the manual page?
(https://www.eyrie.org/~eagle/software/inn/docs/perl-nocem.html)

Is it listed in your <pathetc>/pgp/ncmring.gpg keyring?

% gpg --list-keys --primary-keyring /home/news/etc/pgp/ncmring.gpg

pub rsa3072 2021-12-03 [SC]
8A90C13AE047AC7306BB2E4721EDE4D6D4455599
uid [ inconnue] nono le petit robot (nocem) <robot@pasdenom.info>
sub rsa3072 2021-12-03 [E]

--
Julien ÉLIE

« – Nous parlerons quand l'interprète dormira. [Bong !]
– Il dort. On peut parler. » (Astérix)

Hi Jesse,

>>>> Nov 22 01:00:03 gallifrey nocem[29276]: Article
>>>> <ujkce3$ta8$1@rasp.pasdenom.info>: /usr/local/bin/gpg exited with status 2
>>>
>>> The question then in INN, how does one set the correct pgp executable?
>>
>> I forget the various was to set it besides at 'configure' time, but you can
>> modify lib/innshellvars.pl:
>>
>> $gpg = '/usr/local/bin/gpg';
>
> Errr, also in lib/innshellvars. Someone else will maybe chime in with 'the
> right way'.

perl-nocem uses the INN::Config Perl module to set its variables. The
path to the GnuPG binaries should then be changed in
<pathlib>/perl/INN/Config.pm (or in a custom directory where all Perl
modules are installed, depending on the distribution).

There are 2 lines:

our $gpgv = '/usr/bin/gpgv';
our $gpg = '/usr/bin/gpg';

--
Julien ÉLIE

« L'art de la médecine consiste à distraire le malade pendant que la
nature le guérit. » (Voltaire)

Julien ÉLIE <iulius@nom-de-mon-site.com.invalid> writes:
> There's no universal path to where binaries are installed, so it
> cannot just be hard-coded. When configuring the package, INN tries to
> find the appropriate installed binary, if any. Naturally, if you
> install GnuPG after INN, it won't have set it up right.

I think it would be better if there was runtime configuration
controlling the gpg command to use and any options required
(e.g. --allow-weak-digest-algos), rather than trying to work it out in
configure.

Figuring out details like program paths and supported options at
configure time works very badly if there’s a packaging step involved
before deployment.

--
https://www.greenend.org.uk/rjk/

Hi Richard,

>> There's no universal path to where binaries are installed, so it
>> cannot just be hard-coded. When configuring the package, INN tries to
>> find the appropriate installed binary, if any. Naturally, if you
>> install GnuPG after INN, it won't have set it up right.
>
> I think it would be better if there was runtime configuration
> controlling the gpg command to use and any options required
> (e.g. --allow-weak-digest-algos), rather than trying to work it out in
> configure.

That's a good idea. Do you mean flags to pass to perl-nocem? For
instance by setting up the channel feed this way:

nocem!\
:!*,news.lists.filters\
:Tc,Wf,Ap:/usr/lib/news/bin/perl-nocem -c "/usr/bin/gpg" -o
"--verify --allow-weak-digest-algos" -k "/etc/news/pgp/ncmring.gpg" -l
"/var/log/news/perl-nocem.log" -v

When the flags are not set, the current defaults would be used.

-c would also work with gpgv (naturally, "--verify
--allow-weak-digest-algos" would then have to be removed from -o).
Using -l would enable logging to the given file, and at debug level if
-v is also given.

--
Julien ÉLIE

« Ma devise : une bonne sieste et au lit. » (Jean-Jacques Peroni)

In article <uk2sn3$355iq$1@news.trigofacile.com>,
Julien � LIE <iulius@nom-de-mon-site.com.invalid> wrote:
>Hi Richard,
>
>>> There's no universal path to where binaries are installed, so it
>>> cannot just be hard-coded. When configuring the package, INN tries to
>>> find the appropriate installed binary, if any. Naturally, if you
>>> install GnuPG after INN, it won't have set it up right.
>>
>> I think it would be better if there was runtime configuration
>> controlling the gpg command to use and any options required
>> (e.g. --allow-weak-digest-algos), rather than trying to work it out in
>> configure.
>
>That's a good idea. Do you mean flags to pass to perl-nocem? For
>instance by setting up the channel feed this way:
>
>nocem!\
> :!*,news.lists.filters\
> :Tc,Wf,Ap:/usr/lib/news/bin/perl-nocem -c "/usr/bin/gpg" -o
>"--verify --allow-weak-digest-algos" -k "/etc/news/pgp/ncmring.gpg" -l
>"/var/log/news/perl-nocem.log" -v
>
>When the flags are not set, the current defaults would be used.
>
>-c would also work with gpgv (naturally, "--verify
>--allow-weak-digest-algos" would then have to be removed from -o).
>Using -l would enable logging to the given file, and at debug level if
>-v is also given.
>

Is this available now?

>--
>Julien ÉLIE
>
>« Ma devise : une bonne sieste et au lit. » (Jean-Jacques Peroni)

--
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism ; unsubscribe from Google Groups to be seen
Merry Christmas 2023 and Happy New year 2024 Beware https://mindspring.com

Hi The Doctor,
>> perl-nocem -c "/usr/bin/gpg" -o "--verify --allow-weak-digest-algos"
>> -k "/etc/news/pgp/ncmring.gpg" -l "/var/log/news/perl-nocem.log" -v
>
> Is this available now?

Not yet. It was just a proposal.
I can implement these flags in December if they appear to be useful.
(I'll keep you informed.)

Meanwhile, haven't you tried to modify <pathlib>/perl/INN/Config.pm to
change the path to gpg?

--
Julien ÉLIE

« – Par Thor !
– Par Odin !
– Par exemple ! » (Astérix)

Julien ÉLIE <iulius@nom-de-mon-site.com.invalid> writes:
>>> There's no universal path to where binaries are installed, so it
>>> cannot just be hard-coded. When configuring the package, INN tries to
>>> find the appropriate installed binary, if any. Naturally, if you
>>> install GnuPG after INN, it won't have set it up right.
>> I think it would be better if there was runtime configuration
>> controlling the gpg command to use and any options required
>> (e.g. --allow-weak-digest-algos), rather than trying to work it out in
>> configure.
>
> That's a good idea. Do you mean flags to pass to perl-nocem? For
> instance by setting up the channel feed this way:

I was thinking of pgpverify but it applies to anything in INN that uses
pgp.

--
https://www.greenend.org.uk/rjk/

Hi Richard,

>>> I think it would be better if there was runtime configuration
>>> controlling the gpg command to use and any options required
>>> (e.g. --allow-weak-digest-algos), rather than trying to work it out in
>>> configure.
>>
>> That's a good idea. Do you mean flags to pass to perl-nocem? For
>> instance by setting up the channel feed this way:
>
> I was thinking of pgpverify but it applies to anything in INN that uses
> pgp.

pgpverify is only used for control articles (it is called by
controlchan); perl-nocem does the verification on its own.

Looking again at this thread, I am unsure adding more runtime
configuration would solve the problem. I would like to understand more
the use cases behind that.

Regarding the path to the GnuPG binaries, there's already the
possibility to override them without touching shipped files.
I remember having added a long time ago the possibility to modify the
variables set by INN::Config. If an executable Perl script named
innshellvars.pl.local is present in <pathetc>, it will be run.

So one could force in <pathetc>/innshellvars.pl.local:

$gpgv = '/usr/local/bin/gpgv2';
$gpg = '/usr/local/bin/gpg2';

and GnuPG 2 will be used.
The Doctor, could you please try that and confirm NoCeM notices now work
for you? Otherwise, something else should be fixed first. I really
doubt the problem comes from the version of GnuPG as nono's notices from
pasdenom.info are signed with a PGP key compatible with GnuPG 1.

And regarding the possibility to control the options given to GnuPG, why
an end user should change the defaults which are working? Do you have
different options in mind that should be used? (One may break pgpverify
if for instance he removes --status-fd=1 or --logger-fd=1 from the
passed options.)
Packaged versions of INN should already have the right options (tested
by their maintainers, in coherence with the GnuPG version(s) in the
distribution). Anyway, if a new version of GnuPG changes things, it
could be a bug to fix in pgpverify or perl-nocem as for instance the
GnuPG output may change and no longer be rightly parsable. This cannot
be handled with options so the underlying problem will still be here and
not solved...

--
Julien ÉLIE

« Le mariage et la mort sont tous les deux souhaitables : l'un promet le
bonheur, l'autre le garantit. » (Mark Twain)

Hi,
Julien ÉLIE a tapoté :
> Hi The Doctor,
> > > perl-nocem -c "/usr/bin/gpg" -o "--verify --allow-weak-digest-algos"
> > > -k "/etc/news/pgp/ncmring.gpg" -l "/var/log/news/perl-nocem.log" -v
> >
> > Is this available now?

This logging doesn't work on INN 2.7.1.

>
> Not yet. It was just a proposal.
> I can implement these flags in December if they appear to be useful.
> (I'll keep you informed.)

It will be useful!

--
Stéphane
Sorry for my bad English