On Mon, 2011-06-27 at 17:37 +0200, Ove Kåven wrote:
> Den 26. juni 2011 20:06, skrev Patrick Ohly:
> > On Sun, 2011-06-26 at 18:14 +0200, Ove Kåven wrote:
> >> Den 26. juni 2011 16:59, skrev Patrick Ohly:
> >> Besides, the ability to override these
> >> paths from SyncEvolution would be nice anyway.
> >
> > The problem is that the Neon API has no easy way to provide a path to
> > certs.
>
> I'd write a quick "for (all regular files in dirs) {
> ne_ssl_trust_cert(ne_ssl_cert_read(file)); }" patch, but I'm primarily a
> C programmer and not sure what the current best-practice C++ way to
> iterate over files in a directory is (or to split colon-separated
> directory lists).
Isn't there a combined file of all certs already? Debian maintains such
a file as part of installing individual certs.
> Otherwise, I suppose I'd have to make the GUI disable SSL checks...
That might be the best short-term solution.
> > Attached is a patch which might solve the problem. It passes all of my
> > tests here, but I don't have a setup where the code is relevant. Please
> > let me know if it works for you.
>
> Well, didn't seem to work correctly, I sent logs in separate mail.
The patch did update the UID, but it set an empty value. This might be
due to a different bug that I introduced recently in the whole
UID/revision string tracking. I'm not at all happy with the solution
that I arrived at now. I'll probably rip it out and replace it with
something simpler. May I ask you to try again in a day or two?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
