11:43 a.m.
Hello all,
here my first question to this mailing list after I trying to find a
solution otherwise...
I have a sync problem with my Nokia n900 running syncevolution to
connect to myFunambol where I already had an account for my old Nokia5800.
With the n900 the sync process stops after a minute unsuccessfully and a
message "No network connection" appears although internet is available.
My questions:
1) Did someone successfully established a sync between a Nokia n900
running syncevolution and myFunambol? If yes - how did you manage this?
2) The n900 is not listed in the available myFunambol device list - so
which phone to choose for Nokia n900 running syncevolution?
3) Are there other workaround you can imagine which could let me sync
the device over syncevolution to myFunambol?
Regards, Kyros
6:22 p.m.
Hello Kyros!
This is a Maemo specific question. Let me copy Ove, perhaps he has an
idea.
On Mo, 2010-02-15 at 00:43 +0000, Kyros Hariri wrote:
I have a sync problem with my Nokia n900 running syncevolution to
connect to myFunambol where I already had an account for my old Nokia5800.
With the n900 the sync process stops after a minute unsuccessfully and a
message "No network connection" appears although internet is available.
Did you verify that it is accessing the right URL? In a shell, use
"syncevolution --print-config -q funambol main" and look at the syncURL.
When it fails, can you access that URL in a browser? You should see some
version information about the server.
My questions:
1) Did someone successfully established a sync between a Nokia n900
running syncevolution and myFunambol? If yes - how did you manage this?
I haven't - no such device.
2) The n900 is not listed in the available myFunambol device list -
so
which phone to choose for Nokia n900 running syncevolution?
You don't need this. Just configure your device manually, then sync.
3) Are there other workaround you can imagine which could let me
sync
the device over syncevolution to myFunambol?
Let's investigate as suggested above.
--
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.
7:04 p.m.
Patrick Ohly skrev:
This is a Maemo specific question. Let me copy Ove, perhaps he has
an
idea.
I think Funambol is enabling IPv6. I've heard that the default libcurl
tries to use IPv6 even though the default kernel in Maemo doesn't
support it. Would perhaps be nice if syncevolution had a clean way of
disabling IPv6. I suppose I might have to hack in something to force IPv4...
7:27 p.m.
On Mo, 2010-02-15 at 08:04 +0000, Ove Kaaven wrote:
Patrick Ohly skrev:
> This is a Maemo specific question. Let me copy Ove, perhaps he has an
> idea.
I think Funambol is enabling IPv6. I've heard that the default libcurl
tries to use IPv6 even though the default kernel in Maemo doesn't
support it.
Some desktop users had the same issue. I just didn't know that Maemo was
also affected.
Would perhaps be nice if syncevolution had a clean way of
disabling IPv6.
Does libcurl have an option for it? Should SyncEvolution always disable
it or make it configurable? I suppose configurable and off by default
would be best.
I suppose I might have to hack in something to force IPv4...
Patches welcome ;-}
While you are at it, note that users have problems verifying Google's
SSL certificate:
http://talk.maemo.org/showthread.php?t=40278&page=6
There are --disable-ssl-certificate-check and --with-ca-certificates
configure options for this. The latter still depends on users importing
the right certificate - if that works at all.
--
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.
11:55 p.m.
Patrick Ohly skrev:
On Mo, 2010-02-15 at 08:04 +0000, Ove Kaaven wrote:
> I suppose I might have to hack in something to force IPv4...
Patches welcome ;-}
Surely simple hacks wouldn't be so welcome...?
curl_easy_setopt(handle, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4);
While you are at it, note that users have problems verifying
Google's
SSL certificate:
http://talk.maemo.org/showthread.php?t=40278&page=6
There are --disable-ssl-certificate-check and --with-ca-certificates
configure options for this. The latter still depends on users importing
the right certificate - if that works at all.
They can disable the certificate verification from the config file, I'm
not sure I see a reason to explicitly compile out the checking code.
I don't really know how to import certificates, I haven't needed to.
It's probably necessary for people to change the config file to point at
it. Perhaps if someone who actually needs SSL would provide any ideas
about a good default CA certificate path or something.
I'm wondering if it wouldn't be better to link against libsoup rather
than libcurl after all, though I'm not too sure what difference it would
make.
12:47 a.m.
New subject: [SyncEvolution] SSL support in Maemo package (was: Re: Sync problem: myFunambol -> Nokia n900 with syncevolution)
On Mo, 2010-02-15 at 12:55 +0000, Ove Kaaven wrote:
Patrick Ohly skrev:
> On Mo, 2010-02-15 at 08:04 +0000, Ove Kaaven wrote:
>> I suppose I might have to hack in something to force IPv4...
>
> Patches welcome ;-}
Surely simple hacks wouldn't be so welcome...?
curl_easy_setopt(handle, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4);
I was hoping for a somewhat more complete solution ;-) Something like
the one above might be suitable interim solution for the Maemo package.
> While you are at it, note that users have problems verifying
Google's
> SSL certificate:
> http://talk.maemo.org/showthread.php?t=40278&page=6
>
> There are --disable-ssl-certificate-check and --with-ca-certificates
> configure options for this. The latter still depends on users importing
> the right certificate - if that works at all.
They can disable the certificate verification from the config file, I'm
not sure I see a reason to explicitly compile out the checking code.
--disable-ssl-certificate-check only disables the default, the check is
still in the code. The main reason is that it helps that class of users
who will never figure out why SSL connections fail.
I don't really know how to import certificates, I haven't
needed to.
It's probably necessary for people to change the config file to point at
it.
The point of --with-ca-certificates is again that it changes the
platform-specific default location, ideally saving users from having to
figure out how to solve SSL problems.
The talk.maemo.org hints that changing that location together with
importing the SSL certificates via the Maemo settings GUI might work.
I'm not sure about it, because libcurl and libsoup expect a single file,
whereas the location mention apparently contains them as single files.
I'm wondering if it wouldn't be better to link against
libsoup rather
than libcurl after all, though I'm not too sure what difference it would
make.
Not much, I'm afraid. With libsoup it's actually even worse, the CA file
*has* to be specified by each app, whereas libcurl has a builtin
default. Some libsoup version also failed with certificates like the one
from Google (v1 root certificate, if I remember correctly).
--
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.
1:33 a.m.
New subject: [SyncEvolution] SSL support in Maemo package
Patrick Ohly skrev:
On Mo, 2010-02-15 at 12:55 +0000, Ove Kaaven wrote:
> They can disable the certificate verification from the config file, I'm
> not sure I see a reason to explicitly compile out the checking code.
--disable-ssl-certificate-check only disables the default, the check is
still in the code. The main reason is that it helps that class of users
who will never figure out why SSL connections fail.
OK, could do that if you think it's a good idea, though it's supposedly
less secure or something.
> I don't really know how to import certificates, I haven't
needed to.
> It's probably necessary for people to change the config file to point at
> it.
The point of --with-ca-certificates is again that it changes the
platform-specific default location, ideally saving users from having to
figure out how to solve SSL problems.
I know. I meant it's necessary for people to do that until someone
actually tells me about a good default path which I can set in the
package. Since nobody has, then for now, people do need to change the
config...
The talk.maemo.org hints that changing that location together with
importing the SSL certificates via the Maemo settings GUI might work.
I'm not sure about it, because libcurl and libsoup expect a single file,
whereas the location mention apparently contains them as single files.
Pretty sure at least libcurl can take a path (CURLOPT_CAPATH) in lieu of
the single-file approach (CURLOPT_CAINFO), when built against OpenSSL.
(Don't know about libsoup.) Probably the standard Maemo libcurl package
hasn't been compiled with a default builtin path (though at least it is
compiled against OpenSSL), so the app would need to provide one.
I'm not sure what such a path should be. There seem to be some
predefined certs in /etc/certs/common-ca and /etc/certs/trusted, but if
the user needs to install certs, I don't know where that would be saved.
Also not sure if CAPATH can even take multiple directories.
> I'm wondering if it wouldn't be better to link against
libsoup rather
> than libcurl after all, though I'm not too sure what difference it would
> make.
Not much, I'm afraid. With libsoup it's actually even worse, the CA file
*has* to be specified by each app, whereas libcurl has a builtin
default. Some libsoup version also failed with certificates like the one
from Google (v1 root certificate, if I remember correctly).
Right.
4:44 a.m.
On Mon, 2010-02-15 at 09:04 +0100, Ove Kaaven wrote:
I think Funambol is enabling IPv6.
myFUNAMBOL is hosted on Amazon EC2, so IPv6 support depends on Amazon
willingness to enable it. Last time I checked Amazon didn't support it
(and it's still the case, according to the answers given to this recent
thread
http://developer.amazonwebservices.com/connect/message.jspa?messageID=125517).
Cheers,
stef
--
Funambol :: Open Source Mobile Cloud Sync and Push Email
Community manager :: https://www.forge.funambol.org
Follow the tweets: http://twitter.com/funambol
Funambol Identi.ca group: http://identi.ca/group/funambol
5:02 a.m.
On Mo, 2010-02-15 at 17:44 +0000, Stefano Maffulli wrote:
On Mon, 2010-02-15 at 09:04 +0100, Ove Kaaven wrote:
> I think Funambol is enabling IPv6.
myFUNAMBOL is hosted on Amazon EC2, so IPv6 support depends on Amazon
willingness to enable it. Last time I checked Amazon didn't support it
(and it's still the case, according to the answers given to this recent
thread
http://developer.amazonwebservices.com/connect/message.jspa?messageID=125517).
If IPv6 is not enabled by Amazon, then why does the name server return
an IPv6 address?
$ host my.funambol.com
my.funambol.com has address 72.44.51.240
my.funambol.com has IPv6 address ::ffff:72.44.51.240
You shouldn't return an IPv6 address if that address can't be reached by
clients.
--
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.
11:52 a.m.
Hello Patrik!
Thank you for your answer.
Did you verify that it is accessing the right URL? In a shell, use
"syncevolution --print-config -q funambol main" and look at the syncURL.
When it fails, can you access that URL in a browser? You should see some
version information about the server.
Yes both myfunambol urls are accessible in the browser.
syncevolution --print-config -q funambol main" and look at the
syncURL
for this I get a "ERROR: Server 'funambol' has not been
configured yet.
Regards, Kyros
6:46 p.m.
New subject: [SyncEvolution] SSL support in Maemo package
On Mo, 2010-02-15 at 14:33 +0000, Ove Kaaven wrote:
Patrick Ohly skrev:
> On Mo, 2010-02-15 at 12:55 +0000, Ove Kaaven wrote:
>> They can disable the certificate verification from the config file, I'm
>> not sure I see a reason to explicitly compile out the checking code.
>
> --disable-ssl-certificate-check only disables the default, the check is
> still in the code. The main reason is that it helps that class of users
> who will never figure out why SSL connections fail.
OK, could do that if you think it's a good idea, though it's supposedly
less secure or something.
It depends on Maemo users. If they are capable enough to figure out that
they have a problem with SSL, they may be able to solve it themselves
(turn off checking or somehow import the certificates). I'm sure
everyone reading this list falls into that category.
I'm worried about the class of users who don't figure it out. Anyway,
you know the Maemo community better than I do. Your choice ;-}
--
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.
7:09 p.m.
New subject: [SyncEvolution] Sync problem: myFunambol -> Nokia n900 with syncevolution
Kyros Hariri skrev:
Hello Ove,
Thank you for proposing a solution.
> Surely simple hacks wouldn't be so welcome...?
>
> curl_easy_setopt(handle, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4);
Sorry for asking as a rookie, but in which file on the n900 or in the
this lines shall be inserted?
I already did it, just upgrade the package.
11:26 p.m.
On Mon, 2010-02-15 at 19:02 +0100, Patrick Ohly wrote:
You shouldn't return an IPv6 address if that address can't be
reached by
clients.
It's fixed now. Thanks for pointing out the issue.
/stef
--
Funambol :: Open Source Mobile Cloud Sync and Push Email
Community manager :: https://www.forge.funambol.org
Follow the tweets: http://twitter.com/funambol
Funambol Identi.ca group: http://identi.ca/group/funambol
9:24 a.m.
New subject: [SyncEvolution] Sync problem: myFunambol -> Nokia n900 with syncevolution
4596
days inactive
4598
days old
syncevolution@synevolution.org
14 comments
4 participants
participants (4)
-
Kyros Hariri -
Ove Kaaven -
Patrick Ohly -
Stefano Maffulli