ng0 wrote:
> I am not 100% sure about the tor part, but OrangeWebsite[0] supports
> 2 kinds of coins.
> You could get in touch with support to ask about the tor part of the question.
I strongly advise against using orangewebsite: They rent "freshly
installed servers" with /root/.ssh/authorized_key
Ping! That issue was slashdot'ed yesterday:
http://apache.slashdot.org/story/16/01/30/1825256/sensitive-information-can-be-revealed-from-tor-hidden-services-on-apache
In February 2015, contact_...@nirgal.com wrote:
> Mirimir wrote:
>> On 02/06/2015 08:49 AM, contact_...@nirgal.com wrote:
>>> Do
Mirimir wrote:
> On 02/06/2015 08:49 AM, contact_...@nirgal.com wrote:
>> Documentation really should warn about this, IMHO:
>> https://www.torproject.org/docs/tor-hidden-service.html
>> and possibly a one line warning in the example torrc since
>> "HiddenServicePort 80 127.0.0.1:80" typically is a
Mirimir wrote:
>> When you have a website that is available from a tor secret service, how
>> do you forbid access to url restricted to ip=localhost?
>>
>> I'm thinking of apache default http://x.onion/server-status for example.
>>
>> Using "a2dismod status" is the obvious solution for that one
Hi
When you have a website that is available from a tor secret service, how
do you forbid access to url restricted to ip=localhost?
I'm thinking of apache default http://x.onion/server-status for example.
Using "a2dismod status" is the obvious solution for that one, but does
anyone had a mor
bm-2ctjsegdfzqngqwuqjswro6jrwlc9b3...@bitmessage.ch wrote:
> For debian 7.7, the only one that seems to actually force apt-get
> through tor is torsocks
>
> OPTION 1:
> sudo nano /etc/apt/apt.conf
> ADD THIS: Acquire::socks::proxy "socks5://127.0.0.1:9150";
> When using apt-get as normal, debian
