[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: freedesktop.org single sign-on project
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2008-10-03 7:27:11
Message-ID: 200810030127.12130.aseigo () kde ! org
[Download RAW message or body]


On Friday 03 October 2008, Michael Leupold wrote:
> On Friday 03 October 2008, Aaron J. Seigo wrote:
> > > What do you think about the general itinerary I should take? Do you
> > > think adopting keyring is a "no-go" or a valid option once certain
> > > circumstances are met?
> >
> > which certain circumstances are you thinkg about?
>
> Pretty much the same you brought up:
> * quality
> * KDE interface
> * dependencies
> * integrates smoothly (GUI parts)
> * probably ask them to strip GNOME out of the name :)
> * possibility to provide binary compatibility with applications using the
> wallet interface (so we don't have to provide 2 daemons as long as KDE4 is
> around)
> * ...
>
> > > Personally I think having a common daemon should be the way to go. I
> > > wouldn't object to keyring and I'd even help working on it and getting
> > > it to where we need it.
> >
> > what dependencies does it bring other than glib when built from source?
> > what dependencies does it bring other than glib when installed from
> > binary packages on major distributions?
>
> According to configure.in it looks for:
> - glib (gthread, gobject, gio)

gio? hm. i wonder if that's for the UI bit or if it actually uses it for the 
daemon ... 

> - gtk for the gui part asking for the password (this is an askpass binary
> of its own)

obviously this could be replaced

> - gconf

this should be avoided; i wonder if it's required by the GUI or the daemon?

> - dbus
> - hal
> - pam (for a pam module auto-unlocking the wallet on login)
> - gcrypt
> - libtasn

these are fine

> Some of those dependencies are optional. I'm also not proposing to jump at
> it right away. I have some features I'd like implemented first (like being
> able to unlock the wallet with a smartcard or a fingerprint). I'm also not
> 100% sure if everything will work out fine. But trying to work it out will
> be more comforting if I know if anyone really wants the results.

/me nods...

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech


["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]