Am Don, 2003-09-11 um 04.16 schrieb Henry Jen:

> Thank Eike for taking time to answer my question regarding to scp/sftp.
> It's a bumpy road for me to finally get OZ <-> evolution up and running,
> once I get it running, I think it's great. 

Just realized that I sent my original answer to you only, so for
everyone else who was interested why opie_sync uses sftp instead of scp:
It originally used scp but scp versions prior to the one included in
OpenSSH 3.6 don't give a proper return value (i.e. always zero) while
sftp does. Obviously this would wreak havoc with the syncing, as
opie_sync would always "think" that the syncing was successful. Tom
kindly went along with my suggestion to use sftp as that provides proper
return values.

> Problem 1. After setup sftp options with correct port, password, I
> cannot connect to the server.

> Cause: My Zaurus is using password authentication, Multisync somehow
> cannot connect even though I provided password in setting. After look
> into the code of opie plugin, I found it uses sftp  in batch mode and I
> don't think the password provided is used. 

> Solution: My solution is to use public key authentication by coping my
> public key to authorized_keys on Zaurus. This allow multisync works
> perfectly.

Hm, you really should have taken a look at the README for opie_sync,
which points to http://multisync.sourceforge.net/opie_sync/testing.html
where you can see that sftp only works with host keys :)

> Problem 2. When I first failed to connect, I thought it was caused by
> the port setting, therefore I try to leave the port filed empty. My
> guess is that this should be using default port. Click on sync, the log
> shows everything is OK, no changes are detected. But this caused my
> contacts in Evolution all gone.

> Cause: When leave the port as blank, the program will store the setting
> as port 0. In OPIE plugin, port 0 will cause the plugin not to download
> file from Zaurus, and the upload will fail.
 
> Suggestion: I think this is definitely a bug. The program should detect
> fail to connect at first place.

You are of course right. I'll take a look at this in the next couple of
days and see if I can come up with a patch for Tom to include.

> Just throw out something I experienced, if you have come this far, I
> would like to apologize for my crappy English. :)

No need to apologize, really. Considering that English is more or less
forced upon people who use international mailing lists, news groups,
etc. (although I personally am quite fond of that language) any English
that gets your point across without people having to know your native
language in order to understand it is fine. 

Regards,
Eike

-- 
Eike M. Lang <[EMAIL PROTECTED]>



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Multisync-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/multisync-devel

Reply via email to