On Thu, 3 Nov 2016 18:51, vinc...@vinc17.net said:
> The fallback to Curses is actually a bug when --no-tty is provided
> as a gpg option, because this is documented as:
I agree.
> So, the terminal can't be used to output the prompt for the
> passphrase. I suppose that applications that do not
On 2016-11-03 17:44:22 +0100, Werner Koch wrote:
> BTW, the fallback to Curses can also be troublesome if the calling
> application does not know about this and has no way to redraw the
> screen.
The fallback to Curses is actually a bug when --no-tty is provided
as a gpg option, because this is do
On Thu, 3 Nov 2016 16:13, d...@fifthhorseman.net said:
> i do not either, but i will work on a patch that provides something
> approximating this approach today.
Thanks.
> I'm not sure why you prefer it that way. If pinentry is used as a
Because the pinentry code makes assumptions on how it h
On Thu 2016-11-03 01:44:44 -0400, Vincent Lefevre wrote:
> On 2016-11-02 23:52:43 -0400, Daniel Kahn Gillmor wrote:
>> I think we ought to take the "systemd" meme out of discussion here. I
>> think it's being used by conflation with "d-bus", and that confusion is
>> unlikely to be helpful in resol
On Thu 2016-11-03 03:33:47 -0400, Werner Koch wrote:
> On Thu, 3 Nov 2016 04:52, d...@fifthhorseman.net said:
>
>> a bit of background:
>
> Thanks for that good summary.
>
>> * pinentry-gnome3: d-bus, fallback to terminal if d-bus connectivity
>>fails (this is actually somehow mixed at the mo
On Thu, 3 Nov 2016 04:52, d...@fifthhorseman.net said:
> a bit of background:
Thanks for that good summary.
> * pinentry-gnome3: d-bus, fallback to terminal if d-bus connectivity
>fails (this is actually somehow mixed at the moment; it's not clear
>whether pinentry should fall back to
On 2016-11-02 23:52:43 -0400, Daniel Kahn Gillmor wrote:
> I think we ought to take the "systemd" meme out of discussion here. I
> think it's being used by conflation with "d-bus", and that confusion is
> unlikely to be helpful in resolving these issues.
[...]
Thanks for the explanations. So, the
On Wed 2016-11-02 06:25:25 -0400, Vincent Lefevre wrote:
> I think that this might be related with systemd. I have reported
> another bug (bug 842908) as actually gnupg does not work *at all*
> via SSH without $DISPLAY on one of my machines with systemd, even
> when there isn't a running gpg-agent
On 2016-11-02 10:46:37 +0100, Werner Koch wrote:
> It works for more than a decade for me. I just walked to my laptop and
> tried gpg from that laptop console: The pinentry works as expected. Now
> back to my X server, from where I access my laptop via ssh -X, gpg works
> also with the pinentry s
On Wed, 2 Nov 2016 10:00, vinc...@vinc17.net said:
> The fact that gpg (which has the expected $DISPLAY) conveys DISPLAY
> to gpg-agent should be sufficient to tell where pinentry should
> open its window (or use the text terminal when DISPLAY is unset).
> But the problem is that this does not wo
On 2016-11-02 08:25:34 +0100, Werner Koch wrote:
> gpg conveys DISPLAY to gpg-agent so that pinentry can use the expected
> display. However, if there is a still abnother pinentry open on the
> otehr display you need to wait for its timeout first.
>
> ssh does not convey DISPLAY to gpg-agent so t
On Tue, 1 Nov 2016 10:29, e...@gmx.de said:
> I am not sure, it behaves weird. Sometimes I cannot open messages in
> mutt, it seems to hang. And pressing Ctrl-C releases it and the message
Using mutt with or without "set crypt_use_gpgme" ?
> although all other X11 programs did work. Thinking ag
12 matches
Mail list logo
