Re: [SailfishDevel] Troubleshooting *DAV

2017-01-05 Thread Kimmo Lindholm
openssl requires full chain bundles, it can’t do discoveries on the fly, like 
browsers do.

From: Devel [mailto:devel-boun...@lists.sailfishos.org] On Behalf Of E.S. 
Rosenberg
Sent: 5. tammikuuta 2017 22:03
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] Troubleshooting *DAV

Hi Chirs et al,
Sorry it took me a while had another look today.
Through your instructions I found the following line:
Jan 05 21:38:41 Sailfish carddav-client[2705]: [W] 
CardDav::sslErrorsOccurred:451 - void CardDav::sslErrorsOccurred(const 
QList&) SSL errors occurred, aborting: ("The issuer certificate of a 
locally looked up certificate could not be found", "No certificates could be 
verified")

This reminded me of the fact that SSL checkers had pointed out that I was not 
using the fullchain cert, though browsers seemed (both on Jolla and desktop 
Linux) to still trust my server it seems the carddav client did need the full 
chain, after turning that on it started working.
Side question:
Will changes I make server side to my contacts sync back into my phone or 
should I edit my contacts on the phone only? (I recall there are 2 contact dbs 
one that only root can edit and the other one 'overlays' it)
Thanks!
Eli

2016-12-21 2:35 GMT+02:00 Chris Adams 
<chris.ad...@jolla.com<mailto:chris.ad...@jolla.com>>:
Hi Eli,

Sorry for top posting but I'm on OWA which doesn't handle quoting unfortunately.
Please see 
https://sailfishos.org/wiki/CalDAV_and_CardDAV_Community_Contributions#Sync_Logs
 for information about collecting debug output from the C*DAV plugins.

Your issue sounds a lot like https://bugs.merproject.org/show_bug.cgi?id=1689 
although it may not be due to a captive portal in your case but instead some 
particular SSL response case which we may not handle correctly.

Best regards,
Chris.


From: Devel 
[devel-boun...@lists.sailfishos.org<mailto:devel-boun...@lists.sailfishos.org>] 
on behalf of E.S. Rosenberg 
[es.rosenberg+sailfishos@gmail.com<mailto:es.rosenberg%2bsailfishos@gmail.com>]
Sent: Wednesday, December 21, 2016 8:12 AM
To: Sailfish OS Developers
Subject: [SailfishDevel] Troubleshooting *DAV

Hi everyone,
This is mainly to the gals and girls working on the *DAV support.

Can anyone give me some pointers on how to trouble shoot on the Jolla side?


Problem details:
I set up a sogo 3 (nightly) server to have something to sync my
calander and contacts against.

When I create the *DAV account it allows me to save but then it
immediately after that when it tries to sync fails with "Account needs
to be updated" (new password).

On the server side I see the following 4 requests come in while I am
creating the account:
 [ip] "PROPFIND /SOGo/dav/[user] HTTP/1.1" 401 0/85 0.198 - - 0
 [ip] "PROPFIND /SOGo/dav/[user] HTTP/1.1" 207 324/85 0.274 - - 0
 [ip] "PROPFIND /SOGo/dav/[user] HTTP/1.1" 207 364/120 0.203 - - 0
 [ip] "PROPFIND /SOGo/dav/[user]/Calendar/ HTTP/1.1" 207 473/273 0.213
2124 77% 0

After which no further requests are seen *ever*, not after I enter a
new password or anything else.

Connection (jolla): 3/4G (carrier grade NAT)
Server side: https, allowing only TLS >= 1.0 and strong ciphers.

So any suggestions on how to further troubleshoot this are very welcome.

Thanks!
Eli
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org<mailto:devel-unsubscr...@lists.sailfishos.org>
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to 
devel-unsubscr...@lists.sailfishos.org<mailto:devel-unsubscr...@lists.sailfishos.org>

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Troubleshooting *DAV

2017-01-05 Thread E.S. Rosenberg
Hi Chirs et al,

Sorry it took me a while had another look today.
Through your instructions I found the following line:
Jan 05 21:38:41 Sailfish carddav-client[2705]: [W]
CardDav::sslErrorsOccurred:451 - void CardDav::sslErrorsOccurred(const
QList&) SSL errors occurred, aborting: ("The issuer certificate
of a locally looked up certificate could not be found", "No certificates
could be verified")

This reminded me of the fact that SSL checkers had pointed out that I was
not using the fullchain cert, though browsers seemed (both on Jolla and
desktop Linux) to still trust my server it seems the carddav client did
need the full chain, after turning that on it started working.

Side question:
Will changes I make server side to my contacts sync back into my phone or
should I edit my contacts on the phone only? (I recall there are 2 contact
dbs one that only root can edit and the other one 'overlays' it)

Thanks!
Eli

2016-12-21 2:35 GMT+02:00 Chris Adams <chris.ad...@jolla.com>:

> Hi Eli,
>
> Sorry for top posting but I'm on OWA which doesn't handle quoting
> unfortunately.
> Please see https://sailfishos.org/wiki/CalDAV_and_CardDAV_Community_
> Contributions#Sync_Logs for information about collecting debug output
> from the C*DAV plugins.
>
> Your issue sounds a lot like https://bugs.merproject.org/
> show_bug.cgi?id=1689 although it may not be due to a captive portal in
> your case but instead some particular SSL response case which we may not
> handle correctly.
>
> Best regards,
> Chris.
>
> 
> From: Devel [devel-boun...@lists.sailfishos.org] on behalf of E.S.
> Rosenberg [es.rosenberg+sailfishos@gmail.com]
> Sent: Wednesday, December 21, 2016 8:12 AM
> To: Sailfish OS Developers
> Subject: [SailfishDevel] Troubleshooting *DAV
>
> Hi everyone,
> This is mainly to the gals and girls working on the *DAV support.
>
> Can anyone give me some pointers on how to trouble shoot on the Jolla side?
>
>
> Problem details:
> I set up a sogo 3 (nightly) server to have something to sync my
> calander and contacts against.
>
> When I create the *DAV account it allows me to save but then it
> immediately after that when it tries to sync fails with "Account needs
> to be updated" (new password).
>
> On the server side I see the following 4 requests come in while I am
> creating the account:
>  [ip] "PROPFIND /SOGo/dav/[user] HTTP/1.1" 401 0/85 0.198 - - 0
>  [ip] "PROPFIND /SOGo/dav/[user] HTTP/1.1" 207 324/85 0.274 - - 0
>  [ip] "PROPFIND /SOGo/dav/[user] HTTP/1.1" 207 364/120 0.203 - - 0
>  [ip] "PROPFIND /SOGo/dav/[user]/Calendar/ HTTP/1.1" 207 473/273 0.213
> 2124 77% 0
>
> After which no further requests are seen *ever*, not after I enter a
> new password or anything else.
>
> Connection (jolla): 3/4G (carrier grade NAT)
> Server side: https, allowing only TLS >= 1.0 and strong ciphers.
>
> So any suggestions on how to further troubleshoot this are very welcome.
>
> Thanks!
> Eli
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscribe@lists.
> sailfishos.org
> ___
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscribe@lists.
> sailfishos.org
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Troubleshooting *DAV

2016-12-20 Thread Chris Adams
Hi Eli,

Sorry for top posting but I'm on OWA which doesn't handle quoting unfortunately.
Please see 
https://sailfishos.org/wiki/CalDAV_and_CardDAV_Community_Contributions#Sync_Logs
 for information about collecting debug output from the C*DAV plugins.

Your issue sounds a lot like https://bugs.merproject.org/show_bug.cgi?id=1689 
although it may not be due to a captive portal in your case but instead some 
particular SSL response case which we may not handle correctly.

Best regards,
Chris.


From: Devel [devel-boun...@lists.sailfishos.org] on behalf of E.S. Rosenberg 
[es.rosenberg+sailfishos@gmail.com]
Sent: Wednesday, December 21, 2016 8:12 AM
To: Sailfish OS Developers
Subject: [SailfishDevel] Troubleshooting *DAV

Hi everyone,
This is mainly to the gals and girls working on the *DAV support.

Can anyone give me some pointers on how to trouble shoot on the Jolla side?


Problem details:
I set up a sogo 3 (nightly) server to have something to sync my
calander and contacts against.

When I create the *DAV account it allows me to save but then it
immediately after that when it tries to sync fails with "Account needs
to be updated" (new password).

On the server side I see the following 4 requests come in while I am
creating the account:
 [ip] "PROPFIND /SOGo/dav/[user] HTTP/1.1" 401 0/85 0.198 - - 0
 [ip] "PROPFIND /SOGo/dav/[user] HTTP/1.1" 207 324/85 0.274 - - 0
 [ip] "PROPFIND /SOGo/dav/[user] HTTP/1.1" 207 364/120 0.203 - - 0
 [ip] "PROPFIND /SOGo/dav/[user]/Calendar/ HTTP/1.1" 207 473/273 0.213
2124 77% 0

After which no further requests are seen *ever*, not after I enter a
new password or anything else.

Connection (jolla): 3/4G (carrier grade NAT)
Server side: https, allowing only TLS >= 1.0 and strong ciphers.

So any suggestions on how to further troubleshoot this are very welcome.

Thanks!
Eli
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

[SailfishDevel] Troubleshooting *DAV

2016-12-20 Thread E.S. Rosenberg
Hi everyone,
This is mainly to the gals and girls working on the *DAV support.

Can anyone give me some pointers on how to trouble shoot on the Jolla side?


Problem details:
I set up a sogo 3 (nightly) server to have something to sync my
calander and contacts against.

When I create the *DAV account it allows me to save but then it
immediately after that when it tries to sync fails with "Account needs
to be updated" (new password).

On the server side I see the following 4 requests come in while I am
creating the account:
 [ip] "PROPFIND /SOGo/dav/[user] HTTP/1.1" 401 0/85 0.198 - - 0
 [ip] "PROPFIND /SOGo/dav/[user] HTTP/1.1" 207 324/85 0.274 - - 0
 [ip] "PROPFIND /SOGo/dav/[user] HTTP/1.1" 207 364/120 0.203 - - 0
 [ip] "PROPFIND /SOGo/dav/[user]/Calendar/ HTTP/1.1" 207 473/273 0.213
2124 77% 0

After which no further requests are seen *ever*, not after I enter a
new password or anything else.

Connection (jolla): 3/4G (carrier grade NAT)
Server side: https, allowing only TLS >= 1.0 and strong ciphers.

So any suggestions on how to further troubleshoot this are very welcome.

Thanks!
Eli
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org