[horde] Changes in Signature reset by ActiveSync

[Michael J Rubinsky]

Quoting Michael Menge <michael.menge at zdv.uni-tuebingen.de>:

> Hi Michael,
>
>
> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>
>> Quoting Michael Menge <michael.menge at zdv.uni-tuebingen.de>:
>>
>>> Hi Michael,
>>>
>>>
>>> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>>>
>>>> Quoting Michael Menge <michael.menge at zdv.uni-tuebingen.de>:
>>>>
>>>>> Hi,
>>>>>
>>>>> one of our users had a problem that he could not change his mail  
>>>>> signature.
>>>>> "The next Morning" the Signature was reset to the old signature.
>>>>>
>>>>> After a few days of debugging I discovered that the signature  
>>>>> was restored
>>>>> by Samsung S10 every few minutes via ActiveSync (the Change was  
>>>>> not visible
>>>>> for the users as the signature was cached)
>>>>
>>>> Can you provide a sync log showing whatever you are seeing being  
>>>> sent to the S10 to "restore" the signature? ActiveSync doesn't do  
>>>> anything with the user's signature.  The signature set in Horde  
>>>> should have no bearing on what is used on the device - that's a  
>>>> device setting.
>>>>
>>>
>>> the user has some concerns about personal data contained in the Logs,
>>> so I can't provide you with the logs.
>>>
>>> To clarify the situation. The Signature was Change by the user using the
>>> the normal dynamic view editing the preferences and by me using an  
>>> "UPDATE horde_prefs"
>>> SQL statment on the PostgreSQL Database.
>>>
>>> I watched the Database for changes of the identity pref of the  
>>> user. The change correlated
>>> with the ActiveSync activity of the Samsung S10 shown in the  
>>> apache access log.
>>
>> ActiveSync doesn't contain any mechanism to change this, so it's  
>> not from the ActiveSync client. It could be that the prefs are  
>> cached and changing them directly in the database isn't reflected  
>> on the front end, but I have no idea what is causing it to be saved.
>>
>
> As the problem persisted i did monitor the changes to the identity  
> of the user.
> I was able to pinpoint the change to a 2 minute time frame. As the  
> ActiveSync Log
> does not contain any personal information in that timeframe the user  
> allowed me
> to forward you the logs.
>
> this time the reset was triggered by an other device SAMSUNGSMT805.
> Also the user disable ActiveSync on this device and changed the  
> signature again.
> But there was still a php process running with a connection for that  
> device. I suspect that it
> did reset the signature at the end

These logs don't show anything other than normal requests. What makes  
you think this is the request resetting the signature? As I said,  
ActiveSync has nothing to do with the email signature set in the  
user's Horde preferences. The protocol doesn't contain a mechanism to  
change it or fetch it, and the code doesn't attempt to write anything  
to the identity system at all.  We DO use identity in a few places to  
honor the From address of the user's selected identity, but even so,  
these specific requests wouldn't even hit that code.

If this is 100% proven to be from an activesync request, I would start  
looking at the code that instantiates the identity system or the prefs  
system. Maybe there's some bug in the redis driver or issue with  
caching the prefs?  However, I'm unable to reproduce this.

> We use redis as hastable/session store
>
> Tell me if you need more Informations to help to debug the problem
>
> Thanks for your help
>
>    Michael
>
> --------------------------------------------------------------------------------
> Michael Menge                          Tel.: (49) 7071 / 29-70316
> Universität Tübingen                   Fax.: (49) 7071 / 29-5912
> Zentrum für Datenverarbeitung          mail:  
> michael.menge at zdv.uni-tuebingen.de
> Wächterstraße 76
> 72074 Tübingen



-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 9272 bytes
Desc: PGP Public Key
URL: <https://lists.horde.org/archives/horde/attachments/20200922/9c54cc43/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 851 bytes
Desc: PGP Digital Signature
URL: <https://lists.horde.org/archives/horde/attachments/20200922/9c54cc43/attachment.sig>