Opened 11 months ago

Last modified 11 months ago

#25978 new defect

UseEntryGuards 0 disables EntryNodes

Reported by: tortrac Owned by:
Priority: Very Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Trivial Keywords: easy, doc
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


UseEntryNodes {se} should allow UseEntryGuards 0

But UseEntryGuards 0 breaks UseEntryNodes unless it can find a GuardNode which is against the purpose of UseEntryNodes in TORRC.

Child Tickets

Change History (10)

comment:1 Changed 11 months ago by teor

Keywords: easy doc added; EntryNodes EntryGuards removed
Milestone: Tor: 0.3.4.x-finalTor: unspecified
Priority: ImmediateMedium
Severity: CriticalNormal
Summary: I found a Critial error.......When set in TORRC UseEntryNodes only picks a guard node and fails otherwiseDocument that UseEntryGuards 0 disables EntryNodes
Version: Tor: unspecified

Tor is working as designed.

UseEntryGuards 0 disables all entry guards, including EntryNodes restrictions.

We already explain in the man page that UseBridges 1 disables EntryNodes restrictions.
We should explain that UseEntryGuards 0 does a similar thing.

comment:2 Changed 11 months ago by tortrac

Your just a crazy fascist changing everything I write......

comment:3 Changed 11 months ago by tortrac

It makes no sense that that is what they should be, or by original design. UseEntryGuards 0 should not break EntryNodes.....

It should be changed to the term UseEntryGuards versus UseEntryNodes otherwise your just a crazy fascist who thinks he knows english too well.

It isn't documented because it isn't supposed to be that way......

comment:4 Changed 11 months ago by tortrac

It is perfectly obvious Bridges would break UseEntryNodes

But UseEntryNodes should not be broken because of not using Guards????????

comment:5 Changed 11 months ago by tortrac

Priority: MediumImmediate
Severity: NormalCritical
Summary: Document that UseEntryGuards 0 disables EntryNodesUseEntryGuards 0 disables EntryNodes

UseEntryNodes should NOT break when using UseEntryGuads 0

comment:6 Changed 11 months ago by nickm

Hey, please don't call people names. That's not the kind of software project we want to be. If you want to discuss the relationship between different options, that's cool, but it's not cool to attack people while you do it.

comment:7 Changed 11 months ago by nickm

Priority: ImmediateMedium
Severity: CriticalNormal

comment:8 Changed 11 months ago by tortrac

Ok, instead of making something work it seems much easier to just write 3 words in the "Manual" stating it does not work as opposed to doing real work to make something work. It is ok I get it, which is why I will come off how you do not usually see me.

Consensus does not make set in stone "perfect" so don't fall into that trap in programming. Only real work breaking out of the "Mold" will help you develop outside the "Frameworks" of the fascists.

Of course this is the tool of the fascists, but the Germans didn't develop the first Tank either. But they made the first Assault Rifle and First working Front Line Jet Aircraft. They however worked indepedent of the fascist system to succeed despite it.

The USA failed the Space Race against the superiour Soviet Russians, but textbooks write some fairytail fascists dreams of "winning" much like Trump dreams on twitter probably using Tor too.

The USA shut down Von Braun from working on the space race and rockets, to hand off to an American indigenous fascist Navy group to take credit, but they were too incompetent.

The only reason America develop further was because Von Braun and his team of Germans kept working independently of the fascist system they were a part of and suceed in develping the Saturn V rocket, but now no one ever questions that history could ever have been different??????


comment:9 Changed 11 months ago by tortrac

Priority: MediumImmediate
Severity: NormalCritical

i KNOW "WORK" is scary................

comment:10 Changed 11 months ago by tortrac

Priority: ImmediateVery Low
Severity: CriticalTrivial

Ok, figured it out through more work arounds.......

Connections get cut using only 1 Guard with EntryNodes set, but setting NumEntryGuards to above 3 works great as intended. Better in fact than UseEntryGuards 0 was doing (better peers).

Setting NumEntryGuards is the same as what I want.

Last edited 11 months ago by tortrac (previous) (diff)
Note: See TracTickets for help on using tickets.