On Thu, 26 Aug 2021 16:23, Klaus Ethgen said:
> It seems that I have the problem all time I use the QT pinentry. The
> gtk2 pinentry seems to be fine and with the switch to QT one, the
Did you tried pinentry 1.2.0 which we released last week?
FWIW, I am using xfce and had some problem with
Am Fr den 27. Aug 2021 um 14:12 schrieb Jerry Seibert:
> On Thu, 26 Aug 2021 16:23:16 +0100, Klaus Ethgen stated:
> >Unfortunately, the gtk3 version of pinentry has some toxic dependencies
> >that I never want to have.
>
> Would you be so kind as to list, and possibly explain, those toxic
>
Am Fr den 27. Aug 2021 um 14:12 schrieb Jerry Seibert:
> On Thu, 26 Aug 2021 16:23:16 +0100, Klaus Ethgen stated:
> >Unfortunately, the gtk3 version of pinentry has some toxic dependencies
> >that I never want to have.
>
> Would you be so kind as to list, and possibly explain, those toxic
>
On Thu, 26 Aug 2021 16:23:16 +0100, Klaus Ethgen stated:
>Unfortunately, the gtk3 version of pinentry has some toxic dependencies
>that I never want to have.
Would you be so kind as to list, and possibly explain, those toxic
dependencies?
--
Jerry
Hi,
I have an update for this issue.
It seems that I have the problem all time I use the QT pinentry. The
gtk2 pinentry seems to be fine and with the switch to QT one, the
problem appears. Now I have the problem on debian and gentoo.
Even more, a `gpg-connect-agent updatestartuptty /bye` over
Am Sa den 6. Mär 2021 um 16:32 schrieb Klaus Ethgen:
> [0] https://bugs.gentoo.org/show_bug.cgi?id=774468
Sadly, Gentoo closed that bug as invalid as they do not have pam_gnupg
in their software stack and so they say, that it is a usecase that is
not supportet by them.
It is a bit short
Hi!
I am not sure whether you already di this: Use a script like
--8<---cut here---start->8---
#!/bin/sh
MYPINENTRY="/foo/bar/pinentry-gtk-2"
locale >/tmp/pinentry.err
set >>/tmp/pinentry.err
exec strace -o /tmp/pinentry.trc -e read=0 $MYPINENTRY -d "$@"
I created a bug ([0]) for gentoo.
Gruß
Klaus
[0] https://bugs.gentoo.org/show_bug.cgi?id=774468
--
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen
Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
Hi,
Am Fr den 5. Mär 2021 um 17:05 schrieb Mark H. Wood via Gnupg-users:
> The only thing I can think of to check is: have you selected
> pinentry-qt5 using 'eselect'?
Sure. That is all fine.
~> eselect pinentry list
Available pinentry binary implementations:
[1]
That was a dead end.
Even without libcap linkage, the pinentry does not work.
Also the process capabilities of a manual started gpg-agent are the
same.
Gruß
Klaus
--
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16Klaus
Some further debuging of the capabilities:
pinentry(-qt) has no file capabilities, the process of gpg-agent has the
following:
~> getpcaps 27031
27031:
cap_dac_override,cap_net_admin,cap_net_raw,cap_sys_rawio,cap_sys_admin=i
And in strace I find the following:
28441 20:23:54
On Fri, Mar 05, 2021 at 10:16:41AM +0100, Klaus Ethgen wrote:
> I have a my setup depending strongly on gpg-agent. For this, I preseed
> some passphrases via pam_gnupg.
>
> While this setup work well on my Devuan machine, I have some troubles on
> the Gentoo one, that I don't get solved.
>
>
Hi Werner,
Am Fr den 5. Mär 2021 um 15:59 schrieb Werner Koch:
> On Fri, 5 Mar 2021 10:16, Klaus Ethgen said:
>
> > While this setup work well on my Devuan machine, I have some troubles on
> > the Gentoo one, that I don't get solved.
>
> I am also using Devuan without problems. Did you used
On Fri, 5 Mar 2021 10:16, Klaus Ethgen said:
> While this setup work well on my Devuan machine, I have some troubles on
> the Gentoo one, that I don't get solved.
I am also using Devuan without problems. Did you used
touch /var/lib/elogind/USERNAME
to avoid elogin stealing the socket
14 matches
Mail list logo
