On Wed, Nov 6, 2013 at 1:49 AM, Paul Wise <[email protected]> wrote: > On Wed, Nov 6, 2013 at 5:17 AM, Paweł Hajdan, Jr. wrote: >> Could you explain more how checking paths in the user’s home directory >> should work? > > You could either define a path in the chromium configuration directory > where the key will be stored, or use the freedesktop secrets API: > > http://freedesktop.org/wiki/Specifications/secret-storage-spec/
This could be a non-trivial engineering effort, and the spec seems to be still in progress. Is that part really needed, or is it more theoretical / nice to have? >> Do you have any recommendation for the system-wide API keys file location? >> Similarly, do you have a preference of the format of that file? JSON is one >> reasonable idea I think. > > Format; whatever is easiest to implement. Location in the package, > something like /usr/share/chromium/<somepath> but that path should be > compile-time configurable. This sounds reasonable, I think I can do that. Paweł -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CAATLsPZU9Zxjo�[email protected]
