Tails

#1 Updated by emmapeel 2016-08-27 03:11:14

• Status changed from New to Confirmed

#2 Updated by intrigeri 2016-08-27 09:31:37

• Assignee set to emmapeel

Please provide the exact steps that will allow me to reproduce this bug, and then I’m happy to have a look :)

#4 Updated by emmapeel 2016-08-27 09:58:37

• Assignee deleted (emmapeel)

#5 Updated by intrigeri 2016-08-28 02:48:23

• Type of work changed from Discuss to Research

#6 Updated by intrigeri 2016-09-10 08:06:44

• Assignee set to emmapeel
• Target version set to Tails_3.0
• QA Check deleted (Info Needed)
• Type of work changed from Research to Test

At first glance, I see two problems here, and both are in monkeysign:

• if I got this report right, monkeysign apparently does not provide sufficient feedback about what’s going on, so the user gets confused and thinks that the whole thing is stalled;
• monkeysign lacks support for using a SOCKS5h proxy for its outgoing SMTP connections, so we have to use the Very Big Hammer (torsocks) approach, and then all kinds of things can behave in a weird way. torsocks 2.2 and AllowOutboundLocalhost 2 might fix the specific issue this ticket is about, though (one could confirm that by checking the firewall logs while reproducing the UX problem this ticket is about). We can easily retry once it’s released and in Stretch (with a Tails ISO built from feature/stretch).

emmapeel: at this point, I see two options, that are compatible with each other. You could take these issues to monkeysign upstream. And you could test again in Tails/Stretch once it has torsocks 2.2, after setting AllowOutboundLocalhost 2 in its configuration file. I’ll assume we go for the latter, since it’s easier and could very well be good enough.

#7 Updated by intrigeri 2016-09-10 08:07:24

• related to Feature #8054: Add support for SOCKS proxy to check-mirrors added

#10 Updated by intrigeri 2017-02-01 13:55:33

• related to Bug #12205: Confusing error message when (successfully) cloning Git repos over HTTPS added

#11 Updated by emmapeel 2017-03-18 09:49:19

• Assignee changed from emmapeel to intrigeri

It works!

Using Tails 3.0beta2, after changing `AllowOutboundLocalhost` from 1 to 2, when running:

torsocks monkeysign -u emma.peel@riseup.net —smtp=smtp.riseup.net:587 —smtpuser=emma.peel [fingerprint of key to be signed]

I don’t receive the weird errors anymore.

I still receive them without doing the change, though…

#12 Updated by intrigeri 2017-03-18 10:36:19

• Status changed from Confirmed to In Progress
• Assignee deleted (intrigeri)
• Priority changed from Low to Normal
• Target version changed from Tails_3.0 to Tails_2.12
• % Done changed from 0 to 10
• Type of work changed from Test to Code

So we’ll set AllowOutboundLocalhost 2 in 2.12.

#13 Updated by intrigeri 2017-03-18 10:37:30

• Subject changed from Torsocks complains when used with Monkeysign, but works anyway to torsocks complains when used with Monkeysign, but works anyway

#14 Updated by intrigeri 2017-03-18 10:45:03

• related to deleted (Bug #12205: Confusing error message when (successfully) cloning Git repos over HTTPS)

#15 Updated by intrigeri 2017-03-18 10:45:14

• blocks Bug #12205: Confusing error message when (successfully) cloning Git repos over HTTPS added

#16 Updated by Anonymous 2017-03-18 11:18:07

• Feature Branch set to tails:feature/11736_torsocks_config

#17 Updated by intrigeri 2017-03-18 11:18:21

• blocked by deleted (Bug #12205: Confusing error message when (successfully) cloning Git repos over HTTPS)

#18 Updated by Anonymous 2017-03-18 11:26:36

• Assignee set to intrigeri
• Feature Branch changed from tails:feature/11736_torsocks_config to tails:feature/11736_add_torsocks_config

#19 Updated by Anonymous 2017-03-18 11:27:39

• Assignee changed from intrigeri to anonym
• QA Check set to Ready for QA

I’ve added a configuration file for torsocks. It’s basically the same file as in feature/stretch, except that it’s using a different value, in order to resolve this bug.

#21 Updated by anonym 2017-04-03 18:05:47

• Assignee changed from anonym to intrigeri
• QA Check changed from Ready for QA to Info Needed

With this configuration change in Tails 2.x, I still see the Unable to resolve errors and experience a long delay. IMHO: let’s forget about this for Tails 2.x, and call it fixed in Tails 3.0. Thoughts?

#22 Updated by intrigeri 2017-04-03 18:39:23

• Assignee changed from intrigeri to anonym
• QA Check changed from Info Needed to Ready for QA

> With this configuration change in Tails 2.x, I still see the Unable to resolve errors and experience a long delay.

Interesting. I thought that u had tested this change before proposing it. Anyway:

> IMHO: let’s forget about this for Tails 2.x, and call it fixed in Tails 3.0. Thoughts?

ACK!

#23 Updated by anonym 2017-04-04 08:25:24

• Target version changed from Tails_2.12 to Tails_3.0

#25 Updated by intrigeri 2017-04-18 15:27:05

• Target version changed from Tails_3.0 to Tails_3.0~rc1

#26 Updated by anonym 2017-04-20 14:37:45

• Status changed from In Progress to Fix committed
• Assignee deleted (anonym)
• % Done changed from 10 to 100
• QA Check changed from Ready for QA to Pass

u wrote:
> Weird, i’ve tested that and it worked.

Whatever, let’s forget about it.

> Is it normal that I don’t see the file here: https://labs.riseup.net/code/projects/tails/repository/revisions/406f924ae3fc7a915ba17b2590e3a7e113ba3169?

It’s normal. That commit is a merge commit, and it will only list files for which there was conflicts.

#27 Updated by intrigeri 2017-05-23 09:08:12

• Status changed from Fix committed to Resolved