[tor-dev] Revisiting exit node notification page
Heya! While I re-built my server and my exit node, I took some time in order to get a fancier notification page for the exit node: https://tor.tengu.ch/ It might be good/interesting to provide something a bit better than the default HTML in the package (at least debian package). The current page I got is based on bootstrap and, thus, might have some license issue if this has to be included in a package, but I'm pretty sure we might get something independent. Would you, the dev team, be interested in such a new look for this page? If so, I might take some time in order to provide html/css stuff without any dependence on some other stuff (though, on my page, all is included locally). Cheers, C. ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] Revisiting exit node notification page
On Sat, Jan 17, 2015 at 3:18 PM, CJ t...@tengu.ch wrote: Heya! While I re-built my server and my exit node, I took some time in order to get a fancier notification page for the exit node: https://tor.tengu.ch/ This page isn't loading for me right now, just fyi. Would you, the dev team, be interested in such a new look for this page? If so, I might take some time in order to provide html/css stuff without any dependence on some other stuff (though, on my page, all is included locally). Personally, I would be interested in improvements to the language first and the style second. I'd prefer a page that can be served via DirPortFrontPage (so, no external resources, not even images) and there should definitely be no JavaScript whatsoever. zw ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] Revisiting exit node notification page
On 18/01/15 01:48, Zack Weinberg wrote: On Sat, Jan 17, 2015 at 3:18 PM, CJ t...@tengu.ch wrote: Heya! While I re-built my server and my exit node, I took some time in order to get a fancier notification page for the exit node: https://tor.tengu.ch/ This page isn't loading for me right now, just fyi. Fuu… Tor xen domU seems to make the whole dom0 crash in a weird way. Uncool at least :/. Would you, the dev team, be interested in such a new look for this page? If so, I might take some time in order to provide html/css stuff without any dependence on some other stuff (though, on my page, all is included locally). Personally, I would be interested in improvements to the language first and the style second. I'd prefer a page that can be served via DirPortFrontPage (so, no external resources, not even images) and there should definitely be no JavaScript whatsoever. Sure that. I'm not so good at English (not my mother tongue) — for the no image, it might be a bit austere… anyway, we might as well embed images as b64 encoded content, I already saw that. Regarding JS: sure. in my case it's just for the responsive part, but that's not really useful anyway. I'll try to understand *why* my tor VM makes xen crash first… Cheers, C. zw ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] torify/torsocks and TCP Fast Open
Hi, do you need any more information ? Tim Am Mittwoch, 14. Januar 2015, 16:53:58 schrieb Tim Ruehsen: On Wednesday 14 January 2015 09:01:40 David Goulet wrote: On 13 Jan (15:25:35), Tim Ruehsen wrote: Hi, I tried to torify my wget-like application (https://github.com/rockdaboot/mget) and after some struggling I found that TFO is enabled by default (where available). I guess, the problem is TFO not using connect() but sendto(). Please enlighten me, what I can do (despite turning off TFO). Is it worth a patch or do you think patching libtorsocks has pitfalls or unwanted side-effects ? Can you tell me the torsocks version you are using. Also, how can I reproduce this. Is TFO something you have to set to the socket or enable with a sysctl or... ? Hi David, Thanks for having a look at it. I am using Debian unstable, torsocks 2.0.0-3 Be aware that TFO is not using connect() but sendto() instead (and sendto has been removed from libtorsocks.so a while ago). see here for a good description http://edsiper.linuxchile.cl/blog/2013/02/21/linux-tcp-fastopen-in-your sockets/ To reproduce, you'll need a client that supports TFO. e.g. git clone https://github.com/rockdaboot/mget.git cd mget ./autogen.sh ./configure [Hint: mget currently does not use TFO with HTTPS, just with HTTP] Check your own IP src/mget -qO- checkip.dyndns.org|grep IP [Shows your current IP] Double check with wget wget -qO- checkip.dyndns.org|grep IP [Shows your current IP] Check torifying with TFO enabled (guess you have linux kernel = 3.6.1) torify src/mget -qO- checkip.dyndns.org|grep IP [Shows your current IP] Check torifying with TFO disabled torify src/mget -qO- --no-tcp-fastopen checkip.dyndns.org|grep IP [Shows a Tor IP] Applying my patch (posted to the list) to the latest git master, I use for testing: LD_PRELOAD=/home/tim/src/torsocks/src/lib/.libs/libtorsocks.so src/mget -qO- checkip.dyndns.org|grep IP [Shows a Tor IP, same with --no-tcp-fastopen] Tim signature.asc Description: This is a digitally signed message part. ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
