https://bugs.freedesktop.org/show_bug.cgi?id=76273
--- Comment #19 from Patrick Ohly <[email protected]> --- I just had some spare cycles and tried it myself. My environment is Debian Wheezy. activesyncd 0.92+20140218+SE+4613c97-1 and SyncEvolution 1.4 from syncevolution.org. I created a test user and cleaned its home directory before doing a "sudo su - tester". Then I created a keyring as discussed: $ mkdir -p ~/.gnome2/keyrings/ $ echo default >~/.gnome2/keyrings/default $ cat >~/.gnome2/keyrings/default.keyring <<EOF [keyring] display-name=default lock-on-idle=false lock-after=false EOF # gnome-keyring-daemon expects .cache to exist. $ mkdir ~/.cache $ mkdir ~/.config $ dbus-session.sh bash $ gconftool-2 --set --type=string /apps/activesyncd/accounts/${EXCHANGE_MAILADDR}/username "$EXCHANGE_USER" $ gconftool-2 --set --type=string /apps/activesyncd/accounts/${EXCHANGE_MAILADDR}/serverUri "$EXCHANGE_URL" $ gconftool-2 --set --type=string /apps/activesyncd/accounts/${EXCHANGE_MAILADDR}/password "$EXCHANGE_PASSWORD" tester@pohly-mobl1:~$ find ~/ /home/tester/ /home/tester/.gconf /home/tester/.gconf/apps /home/tester/.gconf/apps/activesyncd /home/tester/.gconf/apps/activesyncd/%gconf.xml /home/tester/.gconf/apps/activesyncd/accounts /home/tester/.gconf/apps/activesyncd/accounts/[email protected] /home/tester/.gconf/apps/activesyncd/accounts/[email protected]/%gconf.xml /home/tester/.gconf/apps/activesyncd/accounts/%gconf.xml /home/tester/.gconf/apps/%gconf.xml /home/tester/.gnome2 /home/tester/.gnome2/keyrings /home/tester/.gnome2/keyrings/default /home/tester/.gnome2/keyrings/default.keyring /home/tester/.config /home/tester/.cache /home/tester/.cache/dconf /home/tester/.cache/dconf/user /home/tester/.cache/keyring-KfZAwm /home/tester/.cache/keyring-KfZAwm/control /home/tester/.bash_history $ EAS_DEBUG_FILE=activesyncd.log EAS_DEBUG=5 /usr/libexec/activesyncd & $ SYNCEVOLUTION_DEBUG=1 syncevolution --daemon=no --print-databases username=${EXCHANGE_MAILADDR} backend=eas-events ... eas-events: Calendar (1) <default> The password was copied to the keyring: $ cat ~/.gnome2/keyrings/default.keyring [keyring] display-name=default ctime=0 mtime=0 lock-on-idle=false lock-after=false [1] item-type=1 display-name=ActiveSync Server Password for [email protected]@https://mail11.123together.com/Microsoft-Server-ActiveSync secret=XXXXXXX mtime=1395326548 ctime=0 [1:attribute0] name=server type=string value=https://mail11.123together.com/Microsoft-Server-ActiveSync [1:attribute1] name=user type=string [email protected] $ cat ~/.gconf/apps/activesyncd/accounts/patrick.ohly\@eas-testing.syncevolution.org/%gconf.xml <?xml version="1.0"?> <gconf> <entry name="contact_folder" mtime="1395326570" type="string"> <stringvalue>2</stringvalue> </entry> <entry name="calendar_folder" mtime="1395326570" type="string"> <stringvalue>1</stringvalue> </entry> <entry name="policy_key" mtime="1395326570" type="string"> <stringvalue>1578705214</stringvalue> </entry> <entry name="password" mtime="1395326414" type="string"> <stringvalue>XXXXXXXXX</stringvalue> </entry> <entry name="serverUri" mtime="1395326413" type="string"> <stringvalue>https://mail11.123together.com/Microsoft-Server-ActiveSync</stringvalue> </entry> <entry name="username" mtime="1395326413" type="string"> <stringvalue>[email protected]</stringvalue> </entry> </gconf> $ grep password activesyncd.log (process:14026:0x1d3ae00): DEBUG:password changed: [XXXXX] (process:14026:0x1d488a0): libeas-WARNING **:Found password in GConf, writing it to Gnome Keyring (process:14026:0x1d3ae00): libeas-DEBUG:mainloop_password_store++ (process:14026:0x1d3ae00): libeas-DEBUG:mainloop_password_store-- (process:14026:0x1d3ae00): libeas-DEBUG:mainloop_password_fetch++ (process:14026:0x1d3ae00): libeas-DEBUG:mainloop_password_fetch-- (process:14026:0x1d488a0): libeas-DEBUG:Found password in Gnome Keyring (process:14026:0x1d488a0): DEBUG:password changed: [XXXXXX] -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
_______________________________________________ Syncevolution-issues mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution-issues
