Stef Walter | 10 Jul 2009 23:17

Re: Secret Storage API specification project

In case anyone is interested, a new 'secrets' DBus API has been brewing:

Michael Leupold wrote:
> Hi,
> 
> A while ago Stef Walter (GNOME Keyring) and me (KDE Wallet) started to draft a 
> common D-BUS API for secret information storage. It's meant to make Keyring- 
> and KWallet-like daemons available under a common D-BUS interface and thus 
> increase interoperability between GNOME, KDE and other applications having the 
> need to securely store passwords and other confidential information.
> 
> We just finished a first rough draft of the specification. For gaining 
> widespread acceptance and use, we'd like to invite everyone interested to join 
> the drafting process which will take place on our mailinglist [1]. This 
> encompasses people working on similar systems/daemons as well as application 
> developers interested in using such an API.
> 
> The current draft is stored inside GNOME Keyring's git repository [2] and 
> generated using gtk-doc to generate the API documentation. The current working 
> draft is available inside the freedesktop.org wiki [3]. If there's a need for 
> it we will move the spec to a repository where collaboration will be easier 
> and move the generation to docbook2html.
> 
> Please note that the current D-BUS interface name is preliminary and not 
> settled upon. It will be decided once the new fd.o specification process has 
> been finalized.
> 
> To give everyone interested the chance to join the mailinglist beforehand, I'd 
> like to start the discussions on Wednesday, 15th of July.
> 
(Continue reading)

Stef Walter | 11 Jul 2009 07:15

Removing 'trusted keys' tab

As posted a while back on this list, I've removed the 'Trusted Keys' tab
because it makes finding keys too unintuitive.

I've grayed out untrusted keys, and they now show up on the 'Other Keys'
tab. Should I add a View option to hide untrusted keys?

Let me know if this feature needs more fine tuning. I wanted to get it
in before the 'String Change Announcement' period.

Cheers,

Stef
Stef Walter | 11 Jul 2009 17:26

Seahorse + GtkBuilder

Seahorse now uses GtkBuilder :)

I've committed the GtkBuilder from Andreas Brauchli. I've tried to go
over everything, to make sure no breakages were introduced, but since
this is a massive patch, I'm sure one or two got through. We'll need to
file bugs and/or fix the problems as they come up.

In the future do we want to handle massive patches like this as a branch
in the main git repository?

Cheers,

Stef
Adam Schreiber | 11 Jul 2009 17:59
Picon

Re: Seahorse + GtkBuilder

On Sat, Jul 11, 2009 at 11:26 AM, Stef Walter<stef-list <at> memberwebs.com> wrote:
> I've committed the GtkBuilder from Andreas Brauchli. I've tried to go
> over everything, to make sure no breakages were introduced, but since
> this is a massive patch, I'm sure one or two got through. We'll need to
> file bugs and/or fix the problems as they come up.
>
> In the future do we want to handle massive patches like this as a branch
> in the main git repository?

As a branch, yes.  In the main git repo, probably not.  I tried that
when I was doing the gtk-doc work for libcryptui and gnome git doesn't
allow you to sync with master and then push your updated branch.  We
ought to use gitorius, git hub, or convince someone in the gnome
infrastructure team to run our own instance of gitorius.

Cheers,

Adam
Stef Walter | 11 Jul 2009 19:40

GtkEntryBuffer as a 'secure' entry

I've been working on a GTK+ feature I think that seahorse, gnome-keyring
and other 'security' applications can use:

http://library.gnome.org/devel/gtk/2.17/GtkEntryBuffer.html

GtkEntryBuffer is like a model for a GtkEntry. It allows us to to store
a prompted for password in non-pageable memory. It'll allow us to get
rid of the 'secure entry' code in seahorse and gnome-keyring,
krb5-auth-dialog and other places in GNOME.

It'll be in GTK+ 2.18. I guess we should wait until 2.18 is released
before depending on this new feature?

Cheers,

Stef
Adam Schreiber | 11 Jul 2009 20:43
Picon

Re: GtkEntryBuffer as a 'secure' entry

On Sat, Jul 11, 2009 at 1:40 PM, Stef Walter<stef-list <at> memberwebs.com> wrote:
> I've been working on a GTK+ feature I think that seahorse, gnome-keyring
> and other 'security' applications can use:
>
> http://library.gnome.org/devel/gtk/2.17/GtkEntryBuffer.html
>
> GtkEntryBuffer is like a model for a GtkEntry. It allows us to to store
> a prompted for password in non-pageable memory. It'll allow us to get
> rid of the 'secure entry' code in seahorse and gnome-keyring,
> krb5-auth-dialog and other places in GNOME.
>
> It'll be in GTK+ 2.18. I guess we should wait until 2.18 is released
> before depending on this new feature?

How does this "new" entry work with cut, copy and paste (see bugs and
an earlier email in the archive)?

Adam
Stef Walter | 11 Jul 2009 22:13

Re: GtkEntryBuffer as a 'secure' entry

Adam Schreiber wrote:
> How does this "new" entry work with cut, copy and paste (see bugs and
> an earlier email in the archive)?

There's no new entry. The behavior is identical to a standard GtkEntry
in password mode [ie: gtk_entry_set_visibility (entry, FALSE)]

Cheers,

Stef
Adam Schreiber | 13 Jul 2009 19:32
Picon

Re: GtkEntryBuffer as a 'secure' entry

Yes, we should wait until 2.18 is out before depending on it.

Cheers,

Adam

On Sat, Jul 11, 2009 at 4:13 PM, Stef Walter<stef-list <at> memberwebs.com> wrote:
> Adam Schreiber wrote:
>> How does this "new" entry work with cut, copy and paste (see bugs and
>> an earlier email in the archive)?
>
> There's no new entry. The behavior is identical to a standard GtkEntry
> in password mode [ie: gtk_entry_set_visibility (entry, FALSE)]
>
> Cheers,
>
> Stef
>
>
Adam Schreiber | 14 Jul 2009 18:29
Picon

Re: Removing 'trusted keys' tab

On Sat, Jul 11, 2009 at 1:15 AM, Stef Walter<stef-list <at> memberwebs.com> wrote:
> As posted a while back on this list, I've removed the 'Trusted Keys' tab
> because it makes finding keys too unintuitive.
>
> I've grayed out untrusted keys, and they now show up on the 'Other Keys'
> tab. Should I add a View option to hide untrusted keys?

I think so.

> Let me know if this feature needs more fine tuning. I wanted to get it
> in before the 'String Change Announcement' period.

This seems to work correctly.  I don't know if it's the change to
GtkBuilder or the removal of a tab, but it feels like loading my very
large keyring is faster now.

Cheers,

Adam
Victory | 26 Jul 2009 19:16

Bug in Documentation about Export Keys V2.24.1


To Replicate:

Help -> Click "Backing up Keyrings"

Offending Text:

Choose "Key -> Back Up Keyrings"

There is no option "Back Up Keyrings" in The Key Sub Menu.

Cheers!
 -- Victory

Gmane