Re: [tor-bugs] #8001 [Tor]: obfsproxy makes tor warn when one bridge is down

[Tor Bug Tracker & Wiki]

#8001: obfsproxy makes tor warn when one bridge is down
--+
 Reporter:  arma  |  Owner:  isis
 Type:  defect| Status:  assigned
 Priority:  Low   |  Milestone:  Tor:
Component:  Tor   |  0.2.9.x-final
 Severity:  Normal|Version:
 Keywords:  tor-client tor-bridge tor-pt  | Resolution:
Parent ID:|  Actual Points:
 Reviewer:| Points:  small
  |Sponsor:  SponsorS-can
--+
Changes (by nickm):

 * keywords:  tor-client tor-bridge => tor-client tor-bridge tor-pt
 * severity:   => Normal
 * sponsor:   => SponsorS-can


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #8001 [Tor]: obfsproxy makes tor warn when one bridge is down

[Tor Bug Tracker & Wiki]

#8001: obfsproxy makes tor warn when one bridge is down
+---
 Reporter:  arma|  Owner:  isis
 Type:  defect  | Status:  assigned
 Priority:  minor   |  Milestone:  Tor: 0.2.8.x-final
Component:  Tor |Version:
   Resolution:  |   Keywords:  tor-client tor-bridge
Actual Points:  |  Parent ID:
   Points:  small   |Sponsor:
+---
Changes (by isis):

 * status:  new => assigned
 * cc: isis (added)
 * priority:  normal => minor
 * keywords:  tor-client => tor-client tor-bridge
 * points:   => small
 * milestone:  Tor: 0.2.??? => Tor: 0.2.8.x-final
 * owner:   => isis


Comment:

 I think we want [NOTICE] level instead of [INFO], because nobody ever sees
 the latter and a bridge being unreachable is probably something that the
 user should know about. If it's just a level change, then this is easy. As
 asn points out above, it we actually want to log only when no bridge are
 reachable, then we need some bigger changes.

 FWIW, I'll take this.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #8001 [Tor]: obfsproxy makes tor warn when one bridge is down

[Tor Bug Tracker Wiki]

#8001: obfsproxy makes tor warn when one bridge is down
+--
 Reporter:  arma|  Owner:
 Type:  defect  | Status:  new
 Priority:  normal  |  Milestone:  Tor: 0.2.???
Component:  Tor |Version:
   Resolution:  |   Keywords:  tor-client
Actual Points:  |  Parent ID:
   Points:  |
+--
Changes (by nickm):

 * milestone:  Tor: 0.2.6.x-final = Tor: 0.2.???


--
Ticket URL: https://trac.torproject.org/projects/tor/ticket/8001#comment:6
Tor Bug Tracker  Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #8001 [Tor]: obfsproxy makes tor warn when one bridge is down

[Tor Bug Tracker Wiki]

#8001: obfsproxy makes tor warn when one bridge is down
+---
 Reporter:  arma|  Owner:
 Type:  defect  | Status:  new   
 Priority:  normal  |  Milestone:  Tor: 0.2.5.x-final
Component:  Tor |Version:
 Keywords:  tor-client  | Parent:
   Points:  |   Actualpoints:
+---
Changes (by nickm):

  * milestone:  Tor: 0.2.4.x-final = Tor: 0.2.5.x-final


-- 
Ticket URL: https://trac.torproject.org/projects/tor/ticket/8001#comment:4
Tor Bug Tracker  Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #8001 [Tor]: obfsproxy makes tor warn when one bridge is down

[Tor Bug Tracker Wiki]

#8001: obfsproxy makes tor warn when one bridge is down
+---
 Reporter:  arma|  Owner:
 Type:  defect  | Status:  new   
 Priority:  normal  |  Milestone:  Tor: 0.2.4.x-final
Component:  Tor |Version:
 Keywords:  tor-client  | Parent:
   Points:  |   Actualpoints:
+---

Comment(by asn):

 (Note (to self): implementation-wise, this does not look like a trivial
 change. The ''Proxy Client'' error message is currently coming from
 `connection_read_proxy_handshake()` which is completely isolated and has
 no way to know whether tor successfully connected to the rest of the
 bridges.)

-- 
Ticket URL: https://trac.torproject.org/projects/tor/ticket/8001#comment:3
Tor Bug Tracker  Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #8001 [Tor]: obfsproxy makes tor warn when one bridge is down

[Tor Bug Tracker Wiki]

#8001: obfsproxy makes tor warn when one bridge is down
+---
 Reporter:  arma|  Owner:
 Type:  defect  | Status:  new   
 Priority:  normal  |  Milestone:  Tor: 0.2.4.x-final
Component:  Tor |Version:
 Keywords:  tor-client  | Parent:
   Points:  |   Actualpoints:
+---

Comment(by dcf):

 The way it works now, warning immediately for every failed bridge, is what
 I expect to happen. Is the problem that it makes the Message button blink
 in Vidalia? Do you suggest that the bridge down message be [info], with
 a [warn] only if all bridges for all transports fail, i.e., if we have no
 connectivity at all?

-- 
Ticket URL: https://trac.torproject.org/projects/tor/ticket/8001#comment:1
Tor Bug Tracker  Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #8001 [Tor]: obfsproxy makes tor warn when one bridge is down

[Tor Bug Tracker Wiki]

#8001: obfsproxy makes tor warn when one bridge is down
+---
 Reporter:  arma|  Owner:
 Type:  defect  | Status:  new   
 Priority:  normal  |  Milestone:  Tor: 0.2.4.x-final
Component:  Tor |Version:
 Keywords:  tor-client  | Parent:
   Points:  |   Actualpoints:
+---

Comment(by arma):

 Replying to [comment:1 dcf]:
  Do you suggest that the bridge down message be [info], with a [warn]
 only if all bridges for all transports fail, i.e., if we have no
 connectivity at all?

 That is what I was thinking, yes.

 Quoting from
 https://trac.torproject.org/projects/tor/wiki/doc/TorFAQ#WhatloglevelshouldIuse
 :
 warn: something bad happened, but we're still running. The bad thing
 might be a bug in the code, some other Tor process doing something
 unexpected, etc. The operator should examine the message and try to
 correct the problem.

 If the operator had selected these bridges herself, I could see a warn
 here. But since they come prechosen, and there are many of them exactly to
 tolerate some being down, it doesn't seem like something the user needs to
 know about.

 That said, there's a messy race condition here: if the down one is the
 first one we try, there aren't any working at the time, so we would end up
 warning anyway. I'm not sure how to fix.

-- 
Ticket URL: https://trac.torproject.org/projects/tor/ticket/8001#comment:2
Tor Bug Tracker  Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #8001 [Tor]: obfsproxy makes tor warn when one bridge is down

[Tor Bug Tracker Wiki]

#8001: obfsproxy makes tor warn when one bridge is down
+---
 Reporter:  arma|  Owner:
 Type:  defect  | Status:  new   
 Priority:  normal  |  Milestone:  Tor: 0.2.4.x-final
Component:  Tor |Version:
 Keywords:  tor-client  | Parent:
   Points:  |   Actualpoints:
+---
 When you run the fancy new flashproxy/obfsproxy bundle:
 https://blog.torproject.org/blog/combined-flash-proxy-pyobfsproxy-browser-
 bundles
 you get
 {{{
 Jan 19 15:09:17.120 [Warning] Proxy Client: unable to connect to
 208.79.90.242:55564 (server rejected connection)
 }}}

 That's because that bridge is down currently.

 When a bridge fails, we should probably only [warn] if no bridges have
 succeeded.

-- 
Ticket URL: https://trac.torproject.org/projects/tor/ticket/8001
Tor Bug Tracker  Wiki https://trac.torproject.org/
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs