On 06/11/2012 07:11 PM, Simon Schampijer wrote:
Follow-up: Upstream seem to work on the possibility to use the XDG dirs,
so one can specify an alternative path.
https://bugzilla.gnome.org/show_bug.cgi?id=613644
Thanks to Marco for pointing that out,
Simon
The enhancement to use the XDG
Follow-up: Upstream seem to work on the possibility to use the XDG dirs,
so one can specify an alternative path.
https://bugzilla.gnome.org/show_bug.cgi?id=613644
Thanks to Marco for pointing that out,
Simon
On 04/16/2012 12:33 PM, Simon Schampijer wrote:
This patch does create an
Thanks Sascha for commenting,
On 04/23/2012 11:13 PM, Sascha Silbe wrote:
Excerpts from Simon Schampijer's message of 2012-04-16 12:33:05 +0200:
This patch does create an ununcrypted default keyring
if there is not one available already. This will stop
prompts for unlocking the keyring after
On 04/16/2012 12:33 PM, Simon Schampijer wrote:
This patch does create an ununcrypted default keyring
if there is not one available already. This will stop
prompts for unlocking the keyring after logging into
Sugar.
In GNOME the session manager deals with creating
that keyring. In the OLPC
Excerpts from Simon Schampijer's message of 2012-04-16 12:33:05 +0200:
This patch does create an ununcrypted default keyring
if there is not one available already. This will stop
prompts for unlocking the keyring after logging into
Sugar.
In GNOME the session manager deals with creating
On Mon, Apr 16, 2012 at 4:33 AM, Simon Schampijer si...@schampijer.de wrote:
In GNOME the session manager deals with creating
that keyring.
Nice find, I was always wondering about that. Do you have a reference
to the exact code that does this?
Thanks,
Daniel
On Mon, Apr 16, 2012 at 07:33, Simon Schampijer si...@schampijer.de wrote:
This patch does create an ununcrypted default keyring
if there is not one available already. This will stop
prompts for unlocking the keyring after logging into
Sugar.
On Debian Testing I used these commands to stop
On Tue, Apr 17, 2012 at 5:04 PM, Daniel Drake d...@laptop.org wrote:
On Mon, Apr 16, 2012 at 4:33 AM, Simon Schampijer si...@schampijer.de wrote:
In GNOME the session manager deals with creating
that keyring.
Nice find, I was always wondering about that. Do you have a reference
to the exact
On Tue, Apr 17, 2012 at 12:26 PM, Peter Robinson pbrobin...@gmail.com wrote:
Not off the top of my head, it took a lot of googleing to find it but
basically it moves what we currently do in OOB, with a few tweaks, to
Quick nitpick here: It's not OOB, but olpc-configure, part of olpc-utils.
This patch does create an ununcrypted default keyring
if there is not one available already. This will stop
prompts for unlocking the keyring after logging into
Sugar.
In GNOME the session manager deals with creating
that keyring. In the OLPC images we do create a default
keyring on image
10 matches
Mail list logo
