- Apr 14, 2016
-
-
sajolida authored
Conflicts: onioncircuits
- Apr 01, 2016
-
-
Alan authored
This should make the window resizeable to any size. Will-fix: #11192
-
Alan authored
-
Alan authored
When using a bridge, the first node in the path doesn't have a ServerDescriptor. We now handle this case gracefully.
-
Alan authored
-
Alan authored
Make sure that onioncircuits can still display useful results without tor-geoipdb installed. Based on the patch from Sascha Steinbiss <sascha@steinbiss.name>
-
- Mar 31, 2016
- Mar 30, 2016
-
-
sajolida authored
'stream' is the internal Tor terminology but 'connection' is a more common term.
-
sajolida authored
-
sajolida authored
These labels are probably not really needed...
-
sajolida authored
Onion Circuits is probably simple enough not to need an extra description of what it is about here.
-
sajolida authored
I don't like introducing the 'path' terminology to mean 'circuit or stream' and clicking on both a circuit or a stream produce the same effect, so let's simplify this here.
-
sajolida authored
-
sajolida authored
- We shouldn't make a difference between "connected to Tor" and "connected to Tor daemon" as this probably doesn't make sense to most users. Also, both things are meant to occur simultaneously. See also #11290. - Remove the second sentence as reconnecting automatically is what you expect from Onion Circuits and you also have no agency on this.
-
- Mar 28, 2016
-
-
sajolida authored
-
- Mar 25, 2016
-
-
intrigeri authored
-
intrigeri authored
-
intrigeri authored
The way we use Transifex, we need to point Tor people to a POT file in Git that they can regularly pull. I see that Onion Circuits has no such file in Git. It's a bit sad to store such auto-generated files in Git, but it's even more sad to ship software without translations. refs: Tails#11173
-
- Feb 18, 2016
-
-
Alan authored
-
Alan authored
Thanks to Sascha Steinbiss <sascha@steinbiss.name>.
-
Alan authored
This prevents a PyGIWarning on startup
-
Alan authored
-
Alan authored
-
Alan authored
-
Alan authored
With bad network conditions, stem sometimes sends the circuit closed event twice. When recieving the 2nd of these events, Tor Monitor used to add the circuit that had beeen removed from the list by the 1st. Will-fix: 10517
-
- Jan 04, 2016
- Nov 16, 2015
-
-
Alan authored
Should-fix: #10516
-
- Oct 24, 2015
-
-
Alan authored
-
- Sep 14, 2015
-
-
Alan authored
It often happens that more space than half of the window is needed to display the circuit names. This commit makes the panes non homogeneous in width and remove the scrollbar from the left pane so that it adapts to the required width.
-
- Sep 10, 2015
-
-
Alan authored
For every stream, tor will send something like: 650 STREAM 3709 NEW 0 www.example.org:80 SOURCE_ADDR=127.0.0.1:42592 PURPOSE=USER 650 STREAM 3709 SENTCONNECT 95 www.example.org:80 650 STREAM 3709 REMAP 95 93.184.216.34:80 SOURCE=EXIT 650 STREAM 3709 SUCCEEDED 95 93.184.216.34:80 650 STREAM 3709 CLOSED 95 93.184.216.34:80 REASON=DONE If we update the target when we receive the REMAP event, then we replace the hostname by its IP. In this commit we only update the stream status, but keep the old target.
-
Alan authored
We used to compare the new circuit ID with the old stream ID, which obviously was always false.
-
- Sep 04, 2015
-
-
Alan authored
-
- Aug 17, 2015
-
-
Tails developers authored
-
Tails developers authored