[sync] fixes for m600i, SE K750i, and SymcML1.2 MD5 auth

Alex Masidlover alex.masidlover at axiomtech.co.uk
Fri Sep 29 06:00:33 PDT 2006


Hi Karsten,

> -implemented Alert NEXT_MESSAGE (222). This doesn't require any action
> that isn't done anyhow. Just a proper status response.

Seems to work for me.

> -fixed bug in SyncML1.2 MD5 authorization. Still a hack but should now
> work as described in Backend.php. Please note: you currently have to
> manually modify Backend.php to get this working.
> It would be great if someone could test this.

Also seems to work for me - have added a comment to this and the  
previous issue on bugs.horde.org

> 1) real syncml md5 auth:
> IMHO the only proper long term solution for the MD5 authorization is to
> create an "crypt-md5syncml" encryption scheme in the Auth module. This
> would then have to use the same encryption method as described in the
> SyncML spec. Doing so requires some additional changes to Auth.php as
> the way of building the hash is somewhat different (i.e. includes the
> username).

I started looking at this but came to the conclusion that its only  
going to be possible for auth backends that hold the password in  
plaintext since most crypted passwords are one way crypted. I've been  
able to find nothing about converting between them...

> 2) syncing more than one database at the same time
> this works for some phones (Synthesis) but not for others it seems. I
> still have to figure out what part of the data in a sync session is
> related to the whole session in which part related to an individual
> database. I think currently a few things are "global" in state.php
> which would have to be part of Sync.php (one database sync).
>
>
> 3) correct handling of maxmsgsize
> still have to look at this

I think based on my couple of weeks of having an m600i those last 3  
should complete support for the m600i.

Thanks,

Alex

-- 
Open Source Specialist
Axiom Tech Limited
W: http://www.axiomtech.co.uk
T: 0845 1270316 or +44 161 660 8009



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



More information about the sync mailing list