--nextPart5281719.0pzA621tbS
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Aaron J. Seigo wrote:
>as others have said, this already exists just as you describe. it's
> already useful to KDE, but it could be made useful to GNOME and others
> as well. if you were to document the storage and protocol in the manner
> of a freedesktop.org draft it would be welcome and discussed there by a
> number of us there.
>
>if you'd be up to the task, i'd be willing to help as a coach/advisor if
>desired (though i don't personally have the time to do the authoring of
> the draft due to the impending releases)

I don't think here the file format needs to be common. All that is=20
required is a common interface to the daemon/program that does the=20
password handling.

With DCOP, it works for all KDE apps. What I think it would be most useful=
=20
is that we prepare a D-BUS specification of the calls required to access=20
the password server. A well-known-service under org.freedesktop.* should=20
be mapped for that instance.

The user would then be able to load whichever manager he prefers -- or=20
none at all, in which case no password saving would happen.

=2D-=20
  Thiago Macieira  -  thiago (AT) macieira (DOT) info
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

1. On frumscafte, hwonne time_t w=C3=A6s n=C3=A1ht, se scieppend =C3=BEone =
circolwyrde=20
wundorcr=C3=A6ftl=C3=ADge cennede and seo eor=C3=B0e w=C3=A6s idel and hit =
w=C3=A6s g=C3=B3d.

--nextPart5281719.0pzA621tbS
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQBByKO6M/XwBW70U1gRAsDTAJ9yMaQ+v0LU+pyELWFETT5ANckGfwCfSrzA
yeQ5AaMimArxrcJljoeJiaM=
=8B3r
-----END PGP SIGNATURE-----

--nextPart5281719.0pzA621tbS--