Discussion:
Connection of password protected WM2003 device
Philip Aston
2008-09-13 00:27:02 UTC
Permalink
Hi Mark, you may remember helping me out (that's an understatement) with
ipaq/evolution synchronization some months ago. I said I'd draft out a
wiki and still intend to. I have a few little hints that could prove
useful- eg keeping the ./synce and ./multisync directories clear of
redundant files, and proving the connection with calendar and tasks
before bringing the contacts in- but I'd like to iron out a few problems
first.

Appreciating that there probably aren't too many wm2003 devices still in
use and that those who still insist on keeping them- and using Linux-
are usually able to connect as root, it's not imperative to enable users
to do so without root or sudo privileges. However, Scott remarked that
there may be a tweak in udev/hotplug that would make this connection
available to users, and that he had a script that might help- if it's
viable for me I'll look into it. I am a little puzzled by the fact that
other devices can be mounted for general use, but these pda's seem to
require quite different methods!

Alternatively, if synce-serial-start is in /etc/rc.local, and the device
is connected before booting up, the user might get a one-time
opportunity to sync. Not an elegant solution.

Second problem is the password. If the device is password protected:

"synce_info_from_odccm: Failed to get a connection for Pocket_PC: Not
authenticated, you need to call ProvidePassword with the correct
password."

That sounds like a few minutes' work editing a line in a config file...
but I don't know where to look.

vdccm allows password entry but it is then impossible to run pstatus and
synce-matchmaker -or, once again, do I need to edit something to make
vdccm run? I have seen Guido's ubuntu page, and this discusses
passwords, but it is for WM5 and 6- his WM3 page provides some
instructions, but not for passwords. Using Debian, I have no trouble
with multisync.On the assumption that any data travelling around in
pda's, usbsticks, etc, needs to be protected, it would be good to get
the password issue sorted before I try writing this up.

Thanks and regards -Philip
Adam Williamson
2008-09-13 07:28:55 UTC
Permalink
Post by Philip Aston
Hi Mark, you may remember helping me out (that's an understatement) with
ipaq/evolution synchronization some months ago. I said I'd draft out a
wiki and still intend to. I have a few little hints that could prove
useful- eg keeping the ./synce and ./multisync directories clear of
redundant files, and proving the connection with calendar and tasks
before bringing the contacts in- but I'd like to iron out a few problems
first.
Appreciating that there probably aren't too many wm2003 devices still in
use and that those who still insist on keeping them- and using Linux-
are usually able to connect as root, it's not imperative to enable users
to do so without root or sudo privileges. However, Scott remarked that
there may be a tweak in udev/hotplug that would make this connection
available to users, and that he had a script that might help- if it's
viable for me I'll look into it. I am a little puzzled by the fact that
other devices can be mounted for general use, but these pda's seem to
require quite different methods!
I don't mean to sound rude, but you're a while out of date here. :)
We've moved on from the synce-serial stuff. synce-hal handles WM2003
devices very similarly to WM5+ devices; there's no need for all the
synce-serial crap any more, they just work when they're plugged in. With
synce-hal , HAL triggers hal-dccm to load, and it works fine with WM2003
devices.

I'm not sure of the status on password protection, though. I haven't
tried that.
--
adamw
Mark Ellis
2008-09-13 07:54:54 UTC
Permalink
Post by Adam Williamson
Post by Philip Aston
Hi Mark, you may remember helping me out (that's an understatement) with
ipaq/evolution synchronization some months ago. I said I'd draft out a
wiki and still intend to. I have a few little hints that could prove
useful- eg keeping the ./synce and ./multisync directories clear of
redundant files, and proving the connection with calendar and tasks
before bringing the contacts in- but I'd like to iron out a few problems
first.
Appreciating that there probably aren't too many wm2003 devices still in
use and that those who still insist on keeping them- and using Linux-
are usually able to connect as root, it's not imperative to enable users
to do so without root or sudo privileges. However, Scott remarked that
there may be a tweak in udev/hotplug that would make this connection
available to users, and that he had a script that might help- if it's
viable for me I'll look into it. I am a little puzzled by the fact that
other devices can be mounted for general use, but these pda's seem to
require quite different methods!
I don't mean to sound rude, but you're a while out of date here. :)
We've moved on from the synce-serial stuff. synce-hal handles WM2003
devices very similarly to WM5+ devices; there's no need for all the
synce-serial crap any more, they just work when they're plugged in. With
synce-hal , HAL triggers hal-dccm to load, and it works fine with WM2003
devices.
Adam is right on the money there, forget everything you knew before :)
and install synce-hal. You'll need to remove vdccm or odccm, or at least
stop them running.
Post by Adam Williamson
I'm not sure of the status on password protection, though. I haven't
tried that.
--
Install synce-trayicon, it'll pick up the password requirement and ask
you to enter one.

Mark
Philip Aston
2008-09-14 22:35:44 UTC
Permalink
Thanks. The box I'm using here doesn't have the old packages so it's a
clean start. I'm staying with Debian (Testing) package handler if I can.
Post by Mark Ellis
Post by Adam Williamson
We've moved on from the synce-serial stuff. synce-hal handles WM2003
devices very similarly to WM5+ devices; there's no need for all the
synce-serial crap any more, they just work when they're plugged in. With
synce-hal , HAL triggers hal-dccm to load, and it works fine with WM2003
devices.
Search on "synce" provided a list and it seemed clear enough what to
install: synce-hal, synce-multisync-plugin, synce-trayicon,
opensync-plugin-synce (that included odccm), opensync-plugin-evolution,
and synce-kpm. I'm assuming that synce-serial is now redundant- but
would it still be necessary to use synce-matchmaker to control
partnerships? Not essential in my case, but interesting to know.
Post by Mark Ellis
Adam is right on the money there, forget everything you knew before :)
and install synce-hal. You'll need to remove vdccm or odccm, or at least
stop them running.
removal of odccm as a package requires removal of opensync-plugin-synce
and sync-sync-engine, so I left them and disabled odccm in /etc/rc. As
you say, the pda is detected and paired, as indicated on the pda itself;
and it can be removed and reconnected. So far so good.

Multisync can't detect the pda. I guess that's an old application- is
kitchensync the best one to use now? Hit a problem when configuring
kitchensync: "unable to read from plugin 'synce-opensync-plugin'; unable
to open /usr/share/opensync/defaults/synce-opensync-plugin for reading-
no such file or directory"
The directory contains only evo2-sync and file-sync. Perhaps I'm missing
a plugin?
Post by Mark Ellis
Install synce-trayicon, it'll pick up the password requirement and ask
you to enter one.
Didn't get any prompt- at the moment I have simple numeric protection.
As I say, I think I'm connected OK, so I don't think this is going to be
a problem.


Thanks- Philip
Adam Williamson
2008-09-15 05:26:36 UTC
Permalink
Post by Philip Aston
Thanks. The box I'm using here doesn't have the old packages so it's a
clean start. I'm staying with Debian (Testing) package handler if I can.
Post by Mark Ellis
Post by Adam Williamson
We've moved on from the synce-serial stuff. synce-hal handles WM2003
devices very similarly to WM5+ devices; there's no need for all the
synce-serial crap any more, they just work when they're plugged in. With
synce-hal , HAL triggers hal-dccm to load, and it works fine with WM2003
devices.
Search on "synce" provided a list and it seemed clear enough what to
install: synce-hal, synce-multisync-plugin, synce-trayicon,
opensync-plugin-synce (that included odccm), opensync-plugin-evolution,
and synce-kpm. I'm assuming that synce-serial is now redundant- but
would it still be necessary to use synce-matchmaker to control
partnerships? Not essential in my case, but interesting to know.
Current synce-trayicon SVN can create partnerships with WM2003 devices.
Otherwise, yes, you need synce-matchmaker.
Post by Philip Aston
Post by Mark Ellis
Adam is right on the money there, forget everything you knew before :)
and install synce-hal. You'll need to remove vdccm or odccm, or at least
stop them running.
removal of odccm as a package requires removal of opensync-plugin-synce
and sync-sync-engine, so I left them and disabled odccm in /etc/rc. As
you say, the pda is detected and paired, as indicated on the pda itself;
and it can be removed and reconnected. So far so good.
Multisync can't detect the pda. I guess that's an old application- is
Multisync has a 0.2 and 0.3 branch in SVN. The current 0.2 branch does
actually work, if you have the right plugins. But so does kitchensync.

I can't help with the plugins, I don't know anything about the Debian
packages. All I can tell you is that there are two synce <-> opensync
plugins. One comes *with synce* (sync-engine, actually): that one is
good for Windows Mobile 5+ devices (i.e. not yours). The other comes
*with opensync* (from the opensync site, the tarball
libopensync-plugin-synce-0.22.tar.gz ). That one is good for only
Windows Mobile 2003 and earlier devices. So that's the one you want. I
don't know if it's packaged for Debian.
--
adamw
Mark Ellis
2008-09-15 09:32:14 UTC
Permalink
Post by Philip Aston
Thanks. The box I'm using here doesn't have the old packages so it's a
clean start. I'm staying with Debian (Testing) package handler if I can.
The debian stuff isn't quite up to date, but it should work.
Post by Philip Aston
Post by Mark Ellis
Post by Adam Williamson
We've moved on from the synce-serial stuff. synce-hal handles WM2003
devices very similarly to WM5+ devices; there's no need for all the
synce-serial crap any more, they just work when they're plugged in. With
synce-hal , HAL triggers hal-dccm to load, and it works fine with WM2003
devices.
Search on "synce" provided a list and it seemed clear enough what to
install: synce-hal, synce-multisync-plugin, synce-trayicon,
opensync-plugin-synce (that included odccm), opensync-plugin-evolution,
and synce-kpm. I'm assuming that synce-serial is now redundant- but
would it still be necessary to use synce-matchmaker to control
partnerships? Not essential in my case, but interesting to know.
Post by Mark Ellis
Adam is right on the money there, forget everything you knew before :)
and install synce-hal. You'll need to remove vdccm or odccm, or at least
stop them running.
removal of odccm as a package requires removal of opensync-plugin-synce
and sync-sync-engine, so I left them and disabled odccm in /etc/rc. As
you say, the pda is detected and paired, as indicated on the pda itself;
and it can be removed and reconnected. So far so good.
opensync-plugin-synce is for later devices, as is synce-sync-engine, you
don't need them, but your solution is fine. synce-kpm also won't work
with wm2003. synce-serial is indeed redundant.

Does synce-pls work ?
Post by Philip Aston
Multisync can't detect the pda. I guess that's an old application- is
kitchensync the best one to use now? Hit a problem when configuring
kitchensync: "unable to read from plugin 'synce-opensync-plugin'; unable
to open /usr/share/opensync/defaults/synce-opensync-plugin for reading-
no such file or directory"
The directory contains only evo2-sync and file-sync. Perhaps I'm missing
a plugin?
You can use the old multisync (0.82) or the "other" opensync plugin with
the newer stuff. I don't know if the other plugin is packaged in debian
though.
Post by Philip Aston
Post by Mark Ellis
Install synce-trayicon, it'll pick up the password requirement and ask
you to enter one.
Didn't get any prompt- at the moment I have simple numeric protection.
As I say, I think I'm connected OK, so I don't think this is going to be
a problem.
Doesn't sound like you're connected properly.

Mark
Philip Aston
2008-10-01 09:19:11 UTC
Permalink
Post by Mark Ellis
Post by Philip Aston
Search on "synce" provided a list and it seemed clear enough what to
install: synce-hal, synce-multisync-plugin, synce-trayicon,
opensync-plugin-synce (that included odccm), opensync-plugin-evolution,
and synce-kpm. I'm assuming that synce-serial is now redundant- but
would it still be necessary to use synce-matchmaker to control
partnerships? Not essential in my case, but interesting to know.
Post by Mark Ellis
Adam is right on the money there, forget everything you knew before :)
and install synce-hal. You'll need to remove vdccm or odccm, or at least
stop them running.
Does synce-pls work ?
result:"(process:5538): WARNING **: synce_info_from_odccm: Failed to get
devices: The name org.synce.odccm was not provided by any .service files
./synce-pls: Could not find configuration at path '(Default)'"
Post by Mark Ellis
You can use the old multisync (0.82)
runs but never connects with the pda, ie there is no "change detected"
message and the sync button is ineffective
Post by Mark Ellis
or the "other" opensync plugin with
the newer stuff. I don't know if the other plugin is packaged in debian
though.
Packaged 0.92 with automatically installed menu entry multisync-gui,
indicates that opensync plugin is "ready" but, on sync, returns "error
while connecting" and "the previous connections was unclean,
slow-syncing" however doesn't sync.
Post by Mark Ellis
Post by Philip Aston
Post by Mark Ellis
Install synce-trayicon, it'll pick up the password requirement and ask
you to enter one.
Gives option to change communications daemon between odccm, hal, vdccm.
I have stopped odccm, and the device is I believe connecting through hal
(dmesg indicates connected, ps shows that hal-dccm starts when the
device is plugged in,and there is a pc icon in the pda's taskbar).
Post by Mark Ellis
Doesn't sound like you're connected properly.
There is a problem- if there is a password on the device, the pc
connection icon disappears from the pda after either 3 seconds if
trayicon is running or about 15-30 seconds if not. dmesg doesnt show
that the device is disconnected. if there is no password, the trayicon
shows "not connected" but the connection icon stays on the pda.

_Phil
Post by Mark Ellis
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
Mark Ellis
2008-10-04 21:36:39 UTC
Permalink
Post by Philip Aston
Post by Mark Ellis
Post by Philip Aston
Search on "synce" provided a list and it seemed clear enough what to
install: synce-hal, synce-multisync-plugin, synce-trayicon,
opensync-plugin-synce (that included odccm), opensync-plugin-evolution,
and synce-kpm. I'm assuming that synce-serial is now redundant- but
would it still be necessary to use synce-matchmaker to control
partnerships? Not essential in my case, but interesting to know.
Post by Mark Ellis
Adam is right on the money there, forget everything you knew before :)
and install synce-hal. You'll need to remove vdccm or odccm, or at least
stop them running.

Does synce-pls work ?
result:"(process:5538): WARNING **: synce_info_from_odccm: Failed to get
devices: The name org.synce.odccm was not provided by any .service files
./synce-pls: Could not find configuration at path '(Default)'"
If this doesn't work, then nothing sync related will work.
Post by Philip Aston
Post by Mark Ellis
You can use the old multisync (0.82)
runs but never connects with the pda, ie there is no "change detected"
message and the sync button is ineffective
Post by Mark Ellis
or the "other" opensync plugin with
the newer stuff. I don't know if the other plugin is packaged in debian
though.
Packaged 0.92 with automatically installed menu entry multisync-gui,
indicates that opensync plugin is "ready" but, on sync, returns "error
while connecting" and "the previous connections was unclean,
slow-syncing" however doesn't sync.
Post by Mark Ellis
Post by Philip Aston
Post by Mark Ellis
Install synce-trayicon, it'll pick up the password requirement and ask
you to enter one.
Gives option to change communications daemon between odccm, hal, vdccm.
I have stopped odccm, and the device is I believe connecting through hal
(dmesg indicates connected, ps shows that hal-dccm starts when the
device is plugged in,and there is a pc icon in the pda's taskbar).
Post by Mark Ellis
Doesn't sound like you're connected properly.
There is a problem- if there is a password on the device, the pc
connection icon disappears from the pda after either 3 seconds if
trayicon is running or about 15-30 seconds if not. dmesg doesnt show
that the device is disconnected. if there is no password, the trayicon
shows "not connected" but the connection icon stays on the pda.
To use synce-hal, make sure odccm and vdccm are not running. Try
plugging in the device with no password first. synce-pls should work at
this point, and synce-trayicon should light up.

Mark

Loading...