Gnupg on openbsd with enigma rouncube plugin

[Mik J]

Hello,
My goal is to use the enigma plugin that is part of roundcube webmail.
I get this error output[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: /bin/gpg2 --status-fd '3' --command-fd '4' --no-secmem-warning --no-tty --no-default-keyring --no-options --no-permission-warning --exit-on-status-write-error --trust-model always --pinentry-mode loopback --ignore-time-conflict --ignore-valid-from --with-colons --with-fingerprint --with-fingerprint --fixed-list-mode --homedir '/enigma/myemail at mydomain.org' --utf8-strings --list-secret-keys -- 'myemail at mydomain.org'
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: BEGIN PROCESSING
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: selecting streams
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: => got 1
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: GPG error stream ready for reading
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: => about to read 65536 bytes from GPG error
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: => read 61 bytes
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: selecting streams
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: => got 1
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: GPG error stream ready for reading
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: => about to read 65536 bytes from GPG error
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: => read 1 bytes
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: ERROR: gpg: Fatal: failed to open '/dev/null': Device not configured
[18-Sep-2022 00:41:46 +0200]: <e9n8l1qh> GPG: selecting streams
Soa) When I launch this commandgpg2 --status-fd '3' --command-fd '4' --no-secmem-warning --no-tty --no-default-keyring --no-options --no-permission-warning --exit-on-status-write-error --trust-model always --pinentry-mode loopback --ignore-time-conflict --ignore-valid-from --with-colons --with-fingerprint --with-fingerprint --fixed-list-mode --homedir '/enigma/myemail at mydomain.org' --utf8-strings --list-secret-keys -- 'myemail at mydomain.org'I have this error gpg: Fatal: status-fd is invalid: Bad file descriptor

If ! remove --status-fd I have this errorgpg: command-fd is invalid: Bad file descriptor
b) I found this post on the openbsd mailling listhttps://misc.openbsd.narkive.com/BLr2vq7b/roundcube-and-enigma-pgp
Where they say"it would be better if the code were changed to use the arc4random() family of functions, which avoid the need for this" (this = /dev/urandom I guess)


In point a) why do i have these errors related to status-fd and command-fdIn point b) gnupg cannot use arc4random() to get its entropy ? Is there any plans to implement that ?
Regards




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20220924/cce089a9/attachment.html>