Opened 6 months ago

Last modified 6 months ago

#30248 new defect

2 Bugs (possibly related) - Mozilla addon Search & Cardbook CardDav-server connection issue

Reported by: jovi234 Owned by: sukhbir
Priority: Medium Milestone:
Component: Applications/TorBirdy Version: Tor: 0.3.5.8
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

When torbirdy is active and working, for the first time if you try and connect Cardbook to a carddav server - it fails with "validation failed"
If you disable torbirdy - the connection to a carddav server from Cardbook works perfectly and connects successfully.
Looking at the logs of Cardbook, i have filed a similar bug on Cardbook issue tracker.
Please see here: https://gitlab.com/CardBook/CardBook/issues/573

It seems as if there is a secure connection issue "Connection status : Failed : SecurityUnsupportedTLSVersionError"

There is also a second bug that COULD be related to the carddav server bug.

When attempting to search in the addons search for any addon such as "Cardbook", it returns an error on Mozilla page with "Oops! We had an error. We'll get to fixing that soon." Now you would think this is a Mozilla issue, but its not. If you disable torbirdy it then returns search results successfully. This issue has been on-going for about 4 months now

PLEASE can you fix these two issues, especially the carddav secure connection issue.

I also tried contacting you on @tor but you were not available.

Child Tickets

Change History (3)

comment:1 Changed 6 months ago by arma

Component: - Select a componentApplications/TorBirdy
Owner: set to sukhbir
Severity: CriticalNormal

comment:2 Changed 6 months ago by sukhbir

Thanks for reporting. I will have a look over the weekend.

comment:3 Changed 6 months ago by jovi234

sukhbir, i have fix the issue with Cardbook. I updated the nginx server's TLS 1.0 to 1.2 and 1.3 and it worked. I have no idea why previously it didnt connect with torbirdy but without it, it connected.

The only issue left to solve is the "Oops! We had an error. We'll get to fixing that soon." page, on Mozilla addons search. That bug, as i said has been around for few months now. If you can fix that, id appreciate it.

Note: See TracTickets for help on using tickets.