Tickets :: [#4802] SyncML : sessionID is too long (>32) for the database

6.0.0-beta1

7/25/25

Summary	SyncML : sessionID is too long (>32) for the database
Queue	Synchronization
Type	Bug
State	Resolved
Priority	1. Low
Owners	karsten (at) horde (dot) org
Requester	patrick.abiven (at) apitech (dot) fr
Created	12/19/2006 (6793 days ago)
Due
Updated	01/22/2007 (6759 days ago)
Assigned	01/14/2007 (6767 days ago)
Resolved	01/22/2007 (6759 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

01/22/2007 05:00:35 PM	Jan Schneider	State ⇒ Resolved

01/14/2007 09:09:53 PM	Karsten Fourmont	Comment #2 State ⇒ Feedback	Reply to this comment
Right. I changed it to use md5(DevInfo.deviceID). Change is in cvs now.

12/19/2006 09:45:12 PM	Chuck Hagenbuch	State ⇒ Assigned Assigned to Karsten Fourmont

12/19/2006 10:01:07 AM	patrick (dot) abiven (at) apitech (dot) fr	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ SyncML : sessionID is too long (>32) for the database Queue ⇒ Synchronization State ⇒ Unconfirmed	Reply to this comment
Hello Using the Synthesis SyncML client with PalmOS (DeviceInfo v5.2.1.0 deviceID = 35 caracters) generates a SessionId key which is too long (> 32 char) for the SessionHandler database. So the SyncML process fails. The SessionID is generated with 'syncml' + DevInfo.deviceID. How can we enforce sessionID that are compatible with the database ? In SyncHdr.php , the establishState() function seems to be the place where SessionID is generated ?! Regards Patrick