[Syncevolution-issues] [Bug 22937] Syncevolution --configure on PC does not correctly store password
https://bugs.meego.com/show_bug.cgi?id=22937
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|Undecided |Medium
Status|NEEDINFO |RESOLVED
Resolution| |FIXED
AssignedTo|syncevolution-bugs(a)meego.bu |patrick.ohly(a)intel.com
|gs |
Target Milestone|--- |1.2
--- Comment #6 from pohly <patrick.ohly(a)intel.com> 2011-09-14 13:13:15 UTC ---
I'm confident that this is fixed in the 1.2 release branch; confirmation would
be useful, I'm not sure yet whether I'll release 1.2 this week or another
pre-release.
commit 0b8a15362f0dd63f9b694c5af636dd36a6688941
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Wed Sep 14 13:21:59 2011 +0200
command line: also check password for --import/export/delete-items and the
source (BMC #21311, #22937)
The previous commit 7411f7e had the password check in the code branch
for --print-items. --import/export/delete-items still had the same
problem. Moved the code.
Source passwords must also be checked, in case that "backendPassword"
is set. Added.
commit 5c31de0812a5d43ba4e67c269b11ea96d82102a2
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Wed Sep 14 13:16:38 2011 +0200
source passwords: password lookup failed in HTTP server mode (BMC #22937)
When configuring sources for an HTTP server, the config name typically
is just the context (@foo). When using the config in the HTTP server,
the config name is the peer inside that context (client@foo). Because
the GNOME keyring lookup keys for the "databasePassword" (more
specifically, the object name) contained the full config name which
was different in both cases, looking up the saved password failed.
The solution is to normalize the config name (to accomodate for
different ways of spelling it) and use only the context, with @ as
before. This will break existing setups where the object name in the
keyring (incorrectly) includes the full config name. In that case just
configure the source again to set the password anew.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: Medium
Keywords:
Status: RESOLVED
Who: patrick.ohly(a)intel.com
Assigned To: patrick.ohly(a)intel.com
Target Build: 1.2
Flags:
Changed: Priority Status Resolution AssignedTo Target Milestone
--------
https://bugs.meego.com/show_bug.cgi?id=22937
--
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.