http://bugzilla.moblin.org/show_bug.cgi?id=3604
--- Comment #4 from yongsheng zhu <[email protected]> 2009-08-31 19:54:09 --- (In reply to comment #2) > (In reply to comment #1) > > fixed in the branch 'origin/bug3604'. waiting for review. > > This patch moves the handling of the keyring into the configuration system > inside libsyncevolution. Perhaps I should have been more explicit about this: > the *command line* should access the keyring, not the *core engine*. > > The rationale is that there might be multiple, front-end specific ways of > storing passwords (KDE keyring anyone?). We can't support all of them in the > core engine and keep it front-end agnostic at the same time. > > Putting GNOME keyring access into the "syncevolution" binary is already > stretching the concept a bit. I can imaging that we'll end up with > --keyring=GNOME and --keyring=KDE at some point, possibly with loadable plugin > modules which do the platform specific keyring access. > > That's overkill right now, but i'll be easier to fix if it is not encoded > inside the core engine itself. > > What you need to do is implement your own CmdlineSyncClient, derived from > EvolutionSyncClient, and then override the askPassword() method. This only allows it to retrieve password. Actually 'askPassword' won't change any code in the configuration system. I'll write CmdlineSyncClient class to copy current askPassword implementation in this class. thanks. However, the root cause is to store password in keyring. We have to write a new class to derive from EvolutionSyncConfig to keep config tree away from keyring. For EvolutionSyncConfig is used to hold all properties including original settings and new settings in command line on the fly and configuration and then is flushed to files. In this way, we have to check 'password' property many places in EvolutionSyncConfig for it operates config tree heavily. Any suggestions? -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
