On Sat, Aug 10, 2013 at 12:48 PM, PCMan <[email protected]> wrote: > On Sat, Aug 10, 2013 at 12:18 PM, .. ink .. <[email protected]> wrote: >> >>> Name: lxqt-keyring >>> >>> Implementation detail: >>> I studied the source code of gnome-keyring and libgcr today. >>> Actaully, it's only gcr-ui and gcr that requires gtk+. >>> The gnome developers carefully separated UI and non-UI parts. >>> The non-UI parts gcr-base and gck are not linked to gtk+. >>> Gcr-ui is a lib used to develop other keyring associated programs. >>> Gnome-keyring itself does not rely on it that much. >>> So, I think porting gnome-keyring to Qt is a faster approach. >>> Besides, gnome-keyring is well-tested and is a proven solution. >>> Since its developers separated UI and non-UI parts already, we can use it. >>> I'm interested in doing this, too. >>> >> >> can you point to the repository with gcr sources? i looked but couldnt find >> them. > > https://git.gnome.org/browse/gcr > Please see if you can take some useful code from them. > >> I already set up a repository[1]. creation of a wallet and testing if a >> wallet key is correct works.I will just continue for my own amusement if you >> guys go with gnome-keyring. > > It's me that want to try gnome-keyring. I'm not sure about others. > The advantage of this approach is, gnome-keyring only uses minimal > gtk+ and libgcr-base is UI independent. > But the problem is in management UI. > The UI used to manage the keyring is seashore, which is full of gtk+. > > The same problem exists for kwallet. > The kwallet daemon and backends seem to be mostly pure Qt. > The configuration UI, however, is totally full of KDE APIs and is > tight to KDE libs. > They're part of KDE runtime and it's not very easy to make it a > standalone component. > >> isnt gnome-keyring deprecated?[2],i dont think its wise basing future work >> on it. > > Thank you for the info! > I still see active development from their git. (mainly the gcr repo) > It's hard to imagine that an actively developed project is deprecated. > Then I probably need to see what they're doing with libsecret and not > touch gnome-keyring for now. > > For keeping the password, I'd suggest that you try KeepPassX, yet > aother Qt-based wallet program. > It stores and encrypt all your passwords and it's a pure Qt program. > What I like from gnome-keyring is, it has integration with PAM, so > after login your desktop session, the keyring is decrypted > automatically. It has ssh agent and others, so we don't have to type > the password sometimes. > KeepPassX does not do this and only provides password storage and a > complete configuration UI. > It, however, provides a good password generator with a nice UI. Maybe > you can take some code from KeepPassX. > > BTW, since gnome-keyring and KWallet both expose their functions via > dbus, it will be better if > you can implement the dbus iface so other programs can access your wallet. > Unfortunately, their dbus API are different. :-( > > Good luck with your wallet thing. I'll follow up your progress. :) > >> [1] https://github.com/mhogomchungu/lxqt_wallet >> [2] https://wiki.gnome.org/GnomeGoals/LibsecretMigration
Well, we were wrong. Gnome-keyring is not deprecated. It's libgnome-keyring that's deprecated, not the daemon. They replace libgnome-keyring with libsecret, and libsecret still talks to gnome-keyring. Gnome-keyring is composed of several parts, gnome-keyring-daemon, gnome-keyring command line tool, and libgnome-keyring, which is a wrapper lib around its dbus interface. The real work is done by libgcr, which is required by gnome-keyring-daemon. So, gnome-keyring is still actively developed. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
