Opened 3 years ago

Closed 3 years ago

Last modified 9 months ago

#18539 closed defect (worksforme)

Add Exception is finicky

Reported by: arlolra Owned by:
Priority: High Milestone:
Component: Archived/Tor Messenger Version:
Severity: Normal Keywords:
Cc: sukhbir Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Since removing the SPI root cert, users are forced to add an exception when joining OFTC. Apart from that being undesirable on its own, some users have raised the issue that the process doesn't work consistently (or even at all). It "works for me" but the number of reports leads me to believe we should investigate further.

Child Tickets

Change History (3)

comment:1 Changed 3 years ago by arlolra

Priority: MediumHigh

There's a workaround (sorta) described here: https://blog.torproject.org/comment/reply/1151/162533

  • Connect
  • Add the exception
  • When connecting fails, right click (context menu) and cancel the reconnection
  • Close the accounts window
  • Reopen the accounts windows
  • Connect again

but that's really untenable (and I'm not sure it even works on Windows).

Raising the priority.

comment:2 Changed 3 years ago by arlolra

Resolution: worksforme
Status: newclosed

Testing storing exceptions again, and on Windows, I've had no issues.

Also, since OFTC is now using Let's Encrypt, the experience should be much improved.

There's a workaround (sorta) described here

Some of the initial confusion around the exception not storing was probably that they had a different cert. for each server, and you'd be directed to a different one at each connection attempt.

comment:3 Changed 9 months ago by traumschule

<+sukhe> hello. yes, I think it's fine to close the tickets. thanks for doing what we should done earlier :)

sad but true:
https://blog.torproject.org/sunsetting-tor-messenger

luckily there are alternatives:
https://blog.torproject.org/tor-heart-onion-messaging

.. and maybe someday

Note: See TracTickets for help on using tickets.