Re: [Opensync-users] Some success with Nokia6680 SyncML via Bluetooth

[Daniel G. <dg...@su...>]

On Sunday 30 July 2006 16:16, Daniel Pittman wrote:
> Hrm. =A0Small problem: that includes all the contact details for people in
> my phone, some of which I can't make available to the general public.
>
> Is there any easy way to address that issue without rendering the trace
> files completely useless?
Yes. I committed today a feature to toggle the privacy level of the trace=20
function. This require that you update opensync to the latest revision. To=
=20
toggle the privacy level that none sensitive information leaks - use:

export OSYNC_TRACE=3D/tmp/osync_trace/;
export OSYNC_PRIVACY=3D1;

Please check the trace file if any private information is leaking before=20
sending. This is quite new and not well tested yet.

>
>
> Also, on a not-unrelated note, is there any easy way to reset the sync
> group without needing to delete and recreate it? =A0In testing this I had
> OpenSync duplicate a bunch of calendar data, which is a minor PITA.
There is a tool called "osyncdump" which can reset the database with the=20
mappings.

>
> > Also interesting would be the information in which format the vcal or
> > vtodo is stored. Use the --dumpinfo paramter of the syncml-obex-client
> > if you use the syncml obex connection.
>
> I hope these are the right details, as follows. =A0I have included the
> summary from the Contact stuff, and a subset of the objects reported
> with the Calendar data. =A0Let me know if you need more and I will send it
> directly.

So far the entries seems to be correct. I cannot imagine that the detector =
was=20
not able to detect them... so let us see if the trace files are helping ;)