On Thu 2016-11-10 04:50:08 -0800, Vincent Lefevre wrote:
> No, this is wrong. In this case, the user isn't necessarily using
> the graphical session.
as far as the graphical session is aware, the user is using it.
> I don't use gnome-keyring, but the dependency on pinentry comes
> from gnupg-agen
On Thu 2016-11-10 01:39:32 -0800, Werner Koch wrote:
> On Wed, 9 Nov 2016 00:41, d...@fifthhorseman.net said:
>
>> dbus-user-session is also very much in line with gpg-agent's
>> --standard-socket option (which is now the default): both of them have
>> the concept of a single session running for
On Wed, 9 Nov 2016 00:41, d...@fifthhorseman.net said:
> dbus-user-session is also very much in line with gpg-agent's
> --standard-socket option (which is now the default): both of them have
> the concept of a single session running for any given user on the
> machine.
In GnuPG that depends on t
Control: tags 842015 + help
On Wed 2016-11-09 01:57:41 -0600, Vincent Lefevre wrote:
> OK, but it uses dbus. So, there should be a way with dbus to know
> whether the user is currently using the graphical session.
We *do* know whether the user is currently using the graphical session.
The user is
On 2016-11-08 17:41:54 -0600, Daniel Kahn Gillmor wrote:
> From the dbus-user-session package description:
>
> This model merges all parallel non-graphical login sessions (text
> mode, ssh, cron, etc.), and up to one graphical session, into a
> single "user-session" or "super-sessio
Hi Vincent--
On Tue 2016-11-08 10:23:22 -0600, Vincent Lefevre wrote:
> Yes, dbus-user-session got installed automatically as a consequence
> of dependencies.
dbus-user-session is also very much in line with gpg-agent's
--standard-socket option (which is now the default): both of them have
the co
On Tue 2016-11-08 02:55:22 -0600, Vincent Lefevre wrote:
> Then, there should be another mean (I don't know which one) so that
> pinentry-gnome3 displays the prompt at the right place, e.g. when
> the user has an X session open locally on the machine but also
> accesses the machine remotely via ssh
On 2016-11-07 23:15:19 -0500, Daniel Kahn Gillmor wrote:
> On Sun 2016-11-06 04:25:27 -0500, Vincent Lefevre wrote:
> > No, this is not a timeout issue, as a window is opened on the
> > X display, while it should never do that when DISPLAY is unset.
>
> DISPLAY has nothing to do with how pinentry
On Sun 2016-11-06 04:25:27 -0500, Vincent Lefevre wrote:
> On 2016-11-06 01:13:53 -0500, Daniel Kahn Gillmor wrote:
>> If you want a pinentry that only speaks curses (and never tries to
>> integrate with a gnome3 session), you should install pinentry-curses and
>> either remove pinentry-gnome3, or
On 2016-11-06 01:13:53 -0500, Daniel Kahn Gillmor wrote:
> If you want a pinentry that only speaks curses (and never tries to
> integrate with a gnome3 session), you should install pinentry-curses and
> either remove pinentry-gnome3, or place "pinentry-program
> /usr/bin/pinentry-curses" in your gp
Control: tag 842015 + moreinfo
On Sat 2016-11-05 06:31:39 -0400, Vincent Lefevre wrote:
> Control: reopen 842015
> Control: found 842015 0.9.7-7
>
> On 2016-11-04 23:23:43 -0400, Daniel Kahn Gillmor wrote:
>> The three bugs above are all caused by a situation where the user wants
>> to use secret
Control: reopen 842015
Control: found 842015 0.9.7-7
On 2016-11-04 23:23:43 -0400, Daniel Kahn Gillmor wrote:
> The three bugs above are all caused by a situation where the user wants
> to use secret key material with gpg, while relying on pinentry-gnome3
> with access to a d-bus session, but wher
12 matches
Mail list logo
