> On 8 Jul 2015, at 08:06 , l.m wrote:
>
> Sounds like access control gone wrong. An older version works but a newer
> version fails. Permissions on the filesystem look fine from mount output. So
> do you use access control, apparmor, selinux, grsecurity, fsprotect, bilibop,
> etc? In particu
Sounds like access control gone wrong. An older version works but a
newer version fails. Permissions on the filesystem look fine from
mount output. So do you use access control, apparmor, selinux,
grsecurity, fsprotect, bilibop, etc? In particular the tor package
which is mentioned in your ticket i
On 07/07/2015 09:26 PM, Cristobal wrote:
> This summer I'll be working on a Relay Web Dashboard as part of Tor's
> Summer of Privacy [1]. The goal of this project is to develop a web
> application to monitor Tor relays. A good part of the back-end code
> will be based on what nyx [2] currently does
Hello everyone,
This summer I'll be working on a Relay Web Dashboard as part of Tor's
Summer of Privacy [1]. The goal of this project is to develop a web
application to monitor Tor relays. A good part of the back-end code
will be based on what nyx [2] currently does (using stem [3]).
You can take
Hi devs,
User here. teor send me over from IRC. It's regarding to this
trac-ticket https://trac.torproject.org/projects/tor/ticket/16518
After upgrading from 0.2.5.12 (git-3731dd5c3071dcba) to 0.2.6.9
(git-145b2587d1269af4) an error occured.
I'm on Debian Jessie (stable) on an AMD Athlon 64 X2. To
Hello people,
I just wanted to let you know that this summer I'll be working in
improving the current GetTor. I've wrote about this before here [0] and
I detailed my plan for the summer here [1]. Thanks to the nice will of
the people running this program and my mentors, I'm starting with a
differe
