Re: gnome-keyring Seahorse Documentation

["Jim Campbell" <jwcampbell fastmail net>]

Hi All,

On Wed, Dec 14, 2011, at 11:47 AM, Guy Hulbert wrote:
> Hi Stef
> 
> Thanks for your reply.
> 
> Yaron Sheffer contacted me off-list to let me know about:
> http://live.gnome.org/GnomeKeyring/SecurityFAQ
> 
> and answered some of my questions.
> 
> I looked at GNUPG some time ago and convinced myself that the
> command-line version is sufficient to be able to create a secure USB
> escrow key.  If I can do the same using SeaHorse as an interface
> then I'm happy.  I will publish any code I write.
> 
> I'm not a specialist but the RSA algorithm was included in my
> introductory algebra course (1977) and I own copies of Cheswick and
> Bellovin's book as well as a couple of Schneier's books.
> 
> On Wed, 2011-14-12 at 14:44 +0100, Stef Walter wrote:
> > On 2011-12-12 15:48, Guy Hulbert wrote:
> > > I couldn't find much but this comment
> > > http://live.gnome.org/Seahorse/TrustModel
> > 
> > We have done most of that in Seahorse when you go to the properties of a
> > key. Or does it not do what you were expecting.
> 
> I just need to convince myself that the private key is physically
> secure.  That is what I would recommend to non-technical users.
> 
> > 
> > > is what I'm interested in.
> > > 
> > > Is someone working on it or can I help out?
> > 
> > Helping out is always welcome :)
> > 
> [snip]
> > Jim Campbell is working on creating some Mallard documentation for
> 
> I will take a look at Mallard then.
> 
> > seahorse, and if you're interested in working on part of that he would
> > be the one to get in touch with.
> 
> He's CC'd.
> 
> > 
> > Cheers,
> > 
> > Stef
> -- 
> --gh


It's been a couple of weeks since I've done work on this, but here is
the current branch:

https://gitorious.org/seahorse-help/seahorse-help

I last updated it on November 20th.  

Mallard ( http://projectmallard.org/ ) is not too difficult to learn. It
is XML-based (which some people don't like), but it was designed by
people who write documentation, so it is not overly complex. Also,
because it is XML-based, it integrates with our existing doc-rendering
and translation toolchains.

I'll send a follow-up note about the docs current status by this
weekend, if not sooner. I welcome feedback and contributions.

Thanks!

Jim