http://bugzilla.moblin.org/show_bug.cgi?id=3604
syncevolution-issues <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |syncevolution-iss...@moblin | |.org --- Comment #18 from syncevolution-issues <[email protected]> 2009-09-06 13:01:38 --- (In reply to comment #16) > current probable passwords I can imagine: > 1)SyncML server account and password: > auxiliary information: server name, user name > 2)Proxy Password: > auxiliary information: server name, user name > 3)Passwords possibly in backend: > currently possible evolution password, auxiliary information: user name > 4)Connection related password: > such as bluetooth connection authentication, auxiliary information: possibly > device name Let me rephrase my question: with which keys would you store each of these passwords in the GNOME keyring? The keys have to be unique enough so that different passwords don't end up having the same key. At the same time the keys should not be too specific, because then irrelevant differences (http vs https) force reentering the password. How do the functions decide which keys they are to use? The "descr" string might be used in askPassword(), but then we have to document which description is used for which password. savePassword() doesn't have something like this, making it unsuitable for use with more than just the main account password. (In reply to comment #17) > current I leave parameters of 'askPassword' and 'savePassword' unchanged > except > 'ConfigNode'. Which one would be passed if these functions are called for source passwords? Always the one for the SyncClientConfig properties? The code doesn't document this. > Patrick, could you check my branch again? Much better, but I think the handling of all passwords should be implemented before merging it. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
