[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #30248 [- Select a component]: 2 Bugs (possibly related) - Mozilla addon Search & Cardbook CardDav-server connection issue
#30248: 2 Bugs (possibly related) - Mozilla addon Search & Cardbook CardDav-server
connection issue
--------------------------+--------------------------------------
Reporter: jovi234 | Owner: (none)
Type: defect | Status: new
Priority: Medium | Component: - Select a component
Version: Tor: 0.3.5.8 | Severity: Critical
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------+--------------------------------------
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.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30248>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs