[Whonix-devel] Overstanding LATEG

[Spencer]

Hi,

> 
> Patrick Schleizer:
> Just to make sure we talk about the same thing.
> 1) documentation for advanced users in the wiki
> 2) asking questions in some form of greeter program
> 

Yep :)

> 
> Was the explanation not good or did your browser not get the right
> anchor?
> 

I was linked to the Tor Project FAQ section that talks about Entry 
Guards.

The explanation is not too clear, as it provides only the context in 
which Entry Guards exist in and not explicitly what an Entry Guard is.  
What an Entry Guard is can, however, be deduced from the text but only 
with a little bit of abductive reasoning :)

> 
> However, it's too much information for any Tails
> Greeter or Whonix Setup Wizard / Anon Connection Wizard or every boot
> question.
> 

That depends on the entirety of the experience.  I encourage you to 
think of the interface as a platform for people to teach themselves.  In 
this case, it isn't only "teach themselves" how to use the interface but 
also how the Tor Network works.

In this context, the information can become redundant for every boot, so 
much thought is needed to avoid simply sweeping difficulties under the 
'Advanced' rug.

> 
> I not following.
> 

My bad :)

I mean to say that the Tor Project (now) uses a single Entry Guard where 
Whonix provides an option to do the opposite: use many (or at least use 
one other than the Entry Guard the Tor Project has reduced the 
experience to).

> 
> 1) We might do better documenting this for advanced users.
> 

My experience has been that "Advanced" users often build for the network 
and "regular folk" simply use the network; both parties have varying 
levels of knowledge.

Having to communicate to this spectrum requires the same level of 
clarity.

> 
> 2) I don't think this can be explained in the some sort of greeter
> program. It's just too much information. And threat model specific.
> 

Yes, but this isn't a threat model that can be proven, for or against, 
so all people will benefit from knowing how things work.

> 
> "If you fear more, that your adversary hosts evil Tor entry guards and
> you want to stick to your existing ones, choose this."
> 
> "Otherwise, if you traveled since your last usage, and fear more, that
> your adversary tracks you by Tor entry guards, choose this."
> 
> Not great. And hard to compress further.
> 

Yes, but it isn't clear to me that the two are opposites, given the 
premise that elicits the limitation to a single guard.

I think that if what Entry Guards are is established prior to making a 
decision, even if in the preceding text, the options could read:

"Enter the network using a single preselected Guard."

                         [or]

"Enter the network using a randomly selected Guard."

> 
> How sajolida comes into this?
> 

I mentioned sajolida :)  The hyperlink jungle that is Tails 
documentation is arguably the clearest documentation I have ever 
experienced; I believe sajolida is responsible for much of this.

> 
> Please contribute.
> 

Will do!

Wordlife,
Spencer