** Changed in: gnome-keyring (Ubuntu Trusty)
Importance: Undecided => Wishlist
** Changed in: gnome-keyring (Ubuntu Utopic)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
alt-f2 bug is bug #1433013 not this one. and has a much wider scope than
just gnome-keyring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
Title:
regression: gnome-keyring components can't b
I can confirm that this issue still exists in vivid with gnome-keyring
3.16.0-0ubuntu1.
If terminal is opened via Alt + F2 session does not contain
SSH_AUTH_SOCK env. Workaround is to use Alt + Strg + T.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
@cbaylis
This is indeed true. See bug #1433013. At the moment as a work-around I suggest
to use:
Super -> type xterm -> hit enter
As that has the right environment. Alt-F2 does not have the right env at
the moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I can confirm that the "GNOME Keyring SSH Agent" entry is ticked in the
startup applications window. A little more experimentation has provided
more insight.
Starting with gnome-keyring 3.10.1-1ubuntu4.1, and continuing into
3.10.1-1ubuntu4.2, the ssh-agent only affects some processes started
with
This bug was fixed in the package gnome-keyring - 3.10.1-1ubuntu7.1
---
gnome-keyring (3.10.1-1ubuntu7.1) utopic; urgency=medium
* Backport changes in user session gnome-keyring jobs up to
3.14.0-1ubuntu2. (LP: #1387303)
* Enable gnome-keyring ssh and gpg daemons to appear
This seems to fix the problem on utopic with 3.10.1-1ubuntu7.1
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
Title:
regression: gnome-keyring components can't be disabled anymore
To manage notifications about this bug g
This bug was fixed in the package gnome-keyring - 3.10.1-1ubuntu4.2
---
gnome-keyring (3.10.1-1ubuntu4.2) trusty; urgency=medium
* Backport changes in user session gnome-keyring jobs up to
3.14.0-1ubuntu2. (LP: #1387303)
* Enable gnome-keyring ssh and gpg daemons to appear in
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
Title:
regression: gnome-keyring components can't be disabled anymore
To manage notifications about this b
** Tags added: verification-done-trusty verification-needed-utopic
** Description changed:
- To disable user session gnome-keyring upstart job:
+ To disable gnome-keyring ssh agent,
+ - disable gnome keyring ssh in startup applications
- $ echo manual ~/.config/upstart/gnome-keyring.override
I tagged this bug as verification-done, but had second thoughts: I've
only tested on trusty, not utopic, and it would be good to have
confirmation from somebody who uses OpenPGP smartcards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
gnome-keyring 3.10.1-1ubuntu4.2 fixed my instance of this issue on trusty
(#1388259 - ECDSA keys not working).
Many thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
Title:
regression:
** Branch linked: lp:ubuntu/trusty-proposed/gnome-keyring
** Branch linked: lp:ubuntu/utopic-proposed/gnome-keyring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
Title:
regression: gnome-ke
Hello Pascal, or anyone else affected,
Accepted gnome-keyring into utopic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
keyring/3.10.1-1ubuntu7.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package
As per my other comment:
https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1257706/comments/7
Please consider also merging this script:
https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1257706/+attachment/4305003/+files/91
-custom-gpg-agent
--
You received this bug notification because
** Changed in: gnome-keyring (Ubuntu Trusty)
Status: Confirmed => In Progress
** Changed in: gnome-keyring (Ubuntu Utopic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Description changed:
To disable user session gnome-keyring upstart job:
$ echo manual ~/.config/upstart/gnome-keyring.override
... and also disable the XDG auto-start jobs (Startup Applications)
- ==
+ =
+ SRU tests
+
+ By default environment should have SSH & GPG agent
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (Ubuntu Utopic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
On 15 January 2015 at 13:26, NightShade <1387...@bugs.launchpad.net> wrote:
> Installing the package from Vivid on my Utopic desktop has fixed my
> problems with my Yubikey neo acting as a smart card, thanks.
>
Thanks. I'll prepare SRUs into utopic & trusty then.
--
Regards,
Dimitri.
--
You r
Installing the package from Vivid on my Utopic desktop has fixed my
problems with my Yubikey neo acting as a smart card, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
Title:
regressi
This bug was fixed in the package gnome-keyring - 3.10.1-1ubuntu9
---
gnome-keyring (3.10.1-1ubuntu9) vivid; urgency=medium
* Show gnome-keyring-gpg & gnome-keyring-ssh in the startup application,
for ease of disabling.
* Make upstart jobs to start gnome-keyring gpg/ssh compon
** Branch linked: lp:ubuntu/vivid-proposed/gnome-keyring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
Title:
regression: gnome-keyring components can't be disabled anymore
To manage notifi
** Also affects: gnome-keyring (Ubuntu Vivid)
Importance: Wishlist
Assignee: Dimitri John Ledkov (xnox)
Status: In Progress
** Also affects: gnome-keyring (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: gnome-keyring (Ubuntu Trusty)
Importance: Undec
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
Title:
regression: gnome-keyring components can't be disabled anymore
To manage notifications about this bug go to:
https:
** Patch added: "gnome-keyring.patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1387303/+attachment/4266383/+files/gnome-keyring.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Meh, i've looked more into this, and I'm still annoyed.
I've tried to use gpg smartcard by default for both gpg
signing/encryption and ssh authentication and it's harder than it should
be.
Thus I'm gonna flip "NoDisplay=true" keys on gpg/ssh components such
that one can toggle those off in the UI
** Changed in: gnome-keyring (Ubuntu)
Status: Won't Fix => Incomplete
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete => In Progress
** Description changed:
To disable user session gnome-keyring upstart job:
$ echo manual ~/.config/upstart/gnome-keyring.override
This issue isn't about whether gnome-keyring is useful or not.
But there are indeed many reasons for not wanting to use it for anything
but secret store indeed, some as listed by Dmitri.
The fact that gnome-keyring doesn't implement some of these features is
rather inherent to the process, where
The ssh key breakage is worse than not handling certain key types. If
the user has ECDSA key, then "ssh-add" will fail to add ANY keys,
including RSA and DSA.
Do we really need the "acroread" of security key agents, with so many
features that none of it is reliably secure?
--
You received this
On 30 October 2014 01:51, Mike Berkley <1387...@bugs.launchpad.net> wrote:
> This same bug affects ssh keys, since gnome-keyring cannot handle ECDSA
> keys.
*sigh*
I presume the following things cannot be handled by gnome-keyring:
* gpg smartcards
* gpg smartcards, used for ssh authentication
* E
This same bug affects ssh keys, since gnome-keyring cannot handle ECDSA
keys.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387303
Title:
regression: gnome-keyring components can't be disabled anym
xdg-autostart .desktop file is used in sessions that are not upstart
managed.
upstart user session jobs are used in upstart managed sessions, e.g.
unity.
to disable a job, echo "manual" into an override file (just like with
any other upstart jobs)
One can override upstart user session jobs, on p
We can't remove xdg files, as there are session types that are not
managed by upstart.
Hence to disable or override the options passed to gnome-keyring should
be done via job override for upstart managed sessions or the xdg
autostart file for non-upstart managed sessions.
There is no bridge/compa
** Description changed:
- GNOME Keyring is by default a rather invasive service, which meddles
- with security sensitive processes invasively. This may or may not be
- wise depending on a users situation.
+ To disable user session gnome-keyring upstart job:
+
+ $ echo manual ~/.config/upstart/gno
36 matches
Mail list logo
