Comment #12 on issue 12351 by [email protected]: Password management -- depend on gnome-password? dbus? http://code.google.com/p/chromium/issues/detail?id=12351
After much discussion, here's what I believe our current situation is. We have implementations (currently commented out) that use gnome-keyring via its library and kwallet via dbus-glib. Ubuntu Hardy provides no 32-bit version of either library on 64-bit, so we currently can't use either. In a world where we didn't have to worry about our insane 64-bit build issues, I think we: 1) Don't want to depend on gnome-keyring anyway. (They might be moving to a dbus- based API?) 2) Could be ok with using dbus, but there's worry that dbus-glib runs into the same threading issues with glib we've hit before. It might mean we should use dbus directly and not via dbus-glib. Another approach is to use helper binaries: simple "native" binaries that speak via stdin/out to us. The hard part here is that we'd need to invent yet another IPC mechanism for this -- the password-management APIs involve passing sets of strings around, and we can't reuse base's implementation of JSON or Pickle because we'd then need a 64-bit build of base. At that point, it almost makes sense to use dbus as the IPC mechanism because that will be natively spoken by kwallet already, leaving us just needing to write a dbus wrapper for gnome-keyring. I could go either way on this. In any case, we need some sort of local fallback for people who don't use these systems, and I think that means our current, unencrypted system. I am going to remove the NOTIMPLEMENTED() bits from it and call it done for now; I'm closing this bug since there's no real resolution of it. The existing bugs for password management cover our lack of integration. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
