I am experiencing the keeps unlocked for entire session behavior and
still can't find a way to change the setting, in Precise. This is a
_horrible_ security flaw!! I am using GPG because I want to protect my
assets and communications, and here my OS is silently subverting my
efforts.
--
You
To be clear, I support the idea of changing the default to a 10 minute
idle timeout.
See also https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/987167
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in
@Eric: When the password prompt comes up, click the arrow to see the
advanced options, and select the timeout you want.
Please open a new bug if that doesn't work for you, this ancient bug is
closed, and is unrelated to your issue.
--
You received this bug notification because you are a member
right, but I think people using gpg key on a beta version can remember
how they setup seahorse-plugins in lucid :)
--
gnome-keyring prompts lack way to set default timeout
https://bugs.launchpad.net/bugs/645561
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
We did not ship seahorse-plugins in lucid (and maybe karmic) by default
either, so it's not a regression from lucid.
--
gnome-keyring prompts lack way to set default timeout
https://bugs.launchpad.net/bugs/645561
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
This is fine and all (I guess), but seahorse-plugins is not installed by
default (at least not on my desktop). I suppose this isn't a huge issue
since Lucid users upgrading won't see a regression, but people using
maverick for the last however many months may be confused.
--
gnome-keyring
after discussion with pitti, we agreed on Marc's idea. We will still use
seahorse-plugin in maverick for that.
--
gnome-keyring prompts lack way to set default timeout
https://bugs.launchpad.net/bugs/645561
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged = Fix Committed
--
gnome-keyring prompts lack way to set default timeout
https://bugs.launchpad.net/bugs/645561
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in
This bug was fixed in the package gnome-keyring -
2.92.92.is.2.31.91-0ubuntu2
---
gnome-keyring (2.92.92.is.2.31.91-0ubuntu2) maverick; urgency=low
* debian/rules:
- don't install gnome-keyring-gpg.desktop for now as we can't configure GPG
timeout before 2.31.92 which we
Not sure we will get 2.31.92 as there is no migration from gconf - gsetting.
We will maybe keep 2.31.91.
Built and tested here.
Consequently, the patch from Kees seems fine, uploading it.
--
gnome-keyring prompts lack way to set default timeout
https://bugs.launchpad.net/bugs/645561
You
** Branch linked: lp:~ubuntu-desktop/gnome-keyring/ubuntu
--
gnome-keyring prompts lack way to set default timeout
https://bugs.launchpad.net/bugs/645561
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
just uploaded, thanks Kees :)
** Changed in: gnome-keyring (Ubuntu)
Status: Confirmed = Fix Committed
--
gnome-keyring prompts lack way to set default timeout
https://bugs.launchpad.net/bugs/645561
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
10 minutes is a bit harsh, though, isn't it? It's definitively not what
we shipped earlier; I used to survive the entire day without having to
enter my ssh/gpg passphrases over and over again. So forcing 10 minutes
would seem to be quite a large inconvenience.
--
gnome-keyring prompts lack way
Rejecting package and reopening as per discussion with Didier. Forcing
everyone to have keys forgotten after 10 minutes makes the entire idea
pretty much useless -- your are going to have to enter your key with
pretty much every email, upload, or ssh. That's not what we had in
earlier releases. I
Here's what I propose:
In Lucid and earlier, the gpg agent was handled by the seahorse-
plugins package which contains a GUI for setting the GPG timeout
preferences.
Since the newfangled gpg agent support in gnome-keyring 2.31.91 doesn't
contain settable preferences, I suggest we disable it by
On Thu, Sep 23, 2010 at 07:28:31AM -, Martin Pitt wrote:
10 minutes is a bit harsh, though, isn't it? It's definitively not what
we shipped earlier; I used to survive the entire day without having to
enter my ssh/gpg passphrases over and over again. So forcing 10 minutes
would seem to be
** Attachment added: Dependencies.txt
https://bugs.edge.launchpad.net/bugs/645561/+attachment/1624429/+files/Dependencies.txt
** Tags added: regression-potential
--
gnome-keyring prompts lack way to set default timeout
https://bugs.launchpad.net/bugs/645561
You received this bug
I'm seeing this also.
It would appear 2.31.91 ripped out gconf support, and so lost all
configuration options.
2.31.92 adds gsettings support, and resolves this. Could we get 2.31.92
in maverick?
** Changed in: gnome-keyring (Ubuntu)
Status: New = Confirmed
--
gnome-keyring prompts
** Changed in: gnome-keyring (Ubuntu)
Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)
--
gnome-keyring prompts lack way to set default timeout
https://bugs.launchpad.net/bugs/645561
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
If a configurable version isn't possible for freeze, how about a minimal
change to set to default to 10 minutes instead of the entire session.
** Patch added: gnome-keyring_2.92.92.is.2.31.91-0ubuntu2.debdiff
20 matches
Mail list logo
