Bug 16581

Summary:	Request for generation of authentication project
Product:	freedesktop.org	Reporter:	Michael Leupold <lemma>
Component:	Project Creation Requests	Assignee:	fd.o Admin Massive <sitewranglers>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium	CC:	dottedmag, elreydetodo, jk, kevinverma, lakostis, rdieter, stef, vuntz
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Michael Leupold 2008-07-01 15:19:53 UTC

We're planning to work on a cross-desktop framework for storing per-user authentication information like passwords, certificates or pkk keys. Currently the teams consists of me (KDE Wallet maintainer) and Stef Walter (GNOME keyring maintainer).

As we're unsure on what to include we'd like to form a preliminary working group and invite people to discuss requirements, a roadmap and goals. Groups that might be interested in joining:
- Desktop environments
- Browsers
- Distributions (I was told some expressed interest)

While initially work will be about specification of a storage format and daemon/client communication other things are being considered:
- common library to operate the storage
- common daemon (maybe using D-Bus)
- Single Sign-On

We'd like to use the following fd.o facilities:
- mailinglist (authentication)
- web
- git repo (for a start only for drafts)

I'd be the preliminary lead contact for the working-group while it's still forming: Michael Leupold, lemma (at) confuego (dot) org

Thanks and kind regards,
Michael

Comment 1 Vincent Untz 2008-08-11 03:25:52 UTC

You can use the fd.o wiki for starting a web page now, fwiw.

Also, for specification drafts, would you be interested in having them hosted with other specifications? (I'm supposed to be working on one git repo for specs)

Comment 2 Michael Leupold 2008-08-11 15:40:31 UTC

Thanks for the hint with the wiki page. I'll try to get something setup asap.

I don't mind using a shared git repository for hosting the spec. As for the moment there's no spec yet the mailinglist is what we'd need most of all.

Comment 3 Benjamin Close 2008-08-14 21:23:17 UTC

got a prefered name for the mailing list?

Comment 4 Michael Leupold 2008-08-15 01:23:41 UTC

I have no real preferences as to the name. How about "authentication"?

Comment 5 Michael Leupold 2008-09-30 15:26:19 UTC

(I'm sorry, I don't want to sound overly impatient.)
Do you need any more information regarding this project or are there any concerns on your part?

Comment 6 Benjamin Close 2008-10-03 06:25:43 UTC

List created - you've been assigned admin of the list. We stil have concerns about the long term viability of this project but are willing to give it a go. For now we'll give you a mailing list and ask you use the fd.o wiki for your initial web page (Start by placing something under: http://www.freedesktop.org/wiki/Software). If you need more resources, please reopen this bug (or file a new refering to this bug) and we'll reasses things then.

(We're Not trying to put you off just want quality projects that's all).

Comment 7 Dan Kegel 2009-02-25 14:40:18 UTC

I see the mailing list is at
http://lists.freedesktop.org/archives/authentication/
but I don't see any activity there, nor any wiki pages.

Also, for reference, I think the current gnome keyring is
http://live.gnome.org/Seahorse

Comment 8 Vincent Untz 2009-02-25 14:44:55 UTC

(In reply to comment #7)
> Also, for reference, I think the current gnome keyring is
> http://live.gnome.org/Seahorse

No, it's http://live.gnome.org/GnomeKeyring

seahorse is the app to manage the content of the keyring, though.

Comment 9 Michael Leupold 2009-02-26 01:10:49 UTC

True. This project has been on hold from my side because I didn't quite get to do something about it and I was pretty much on my own. Recently I picked it up again and we're currently talking about a common protocol (probably DBus-based) on the gnome keyring mailinglist.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.