New answers tagged

0

Considering torrc default onion port is 80 and your nginx is configured to listen on port 8080, you should change the option HiddenServicePort to reflect that HiddenServicePort VIRTPORT [TARGET] Configure a virtual port VIRTPORT for a hidden service. You may use this option multiple times; each time applies to the service using the most recent ...


0

No one else should be able to know the guard node of an onion service, but in practice this is not always the case. This is known as a guard discovery attack, and a few of these are described in academic literature. One good example is "Dropping on the Edge: Flexibility and Traffic Confirmation in Onion Routing Protocols".


0

The spec for the v3 onion services, starting with section 2.2, explains it rather well: 2.2. Locating, uploading, and downloading hidden service descriptors [HASHRING] To avoid attacks where a hidden service's descriptor is easily targeted for censorship, we store them at different directories over time, and use shared random values to prevent those ...


0

If the video hosting is inside the Tor network, i.e. via dot-onion address - it's totally OK and suffers no performance implication if the server is set up as it should be. Take a look at IPFS and ZeroNet - it can also help. The only possible problem can be a live video stream, so as in a clearnet Internet


0

The document that you're reading is the original Tor paper from around 2004. It's still useful for getting a basic understanding of the network, but a lot of the specifics have changed. The "authorization cookie" that it refers to acts as a client password. The hidden service can require that the client provide this cookie in order to allow them to ...


2

None of the 3 languages is perfectly safe. All of them have vulnerabilities that if an application is not developed following good programming practices, they can allow an attacker to exploit different weak points and gain access to the application and its data. You can use any language you want, but you have to consider checking your application to see if ...


0

Usually - no, but in rare insecure cases - yes. The service hardening is basically the service owner's sole task. For Tor the website, SSH, VPN or anything else is basically a tunnel. So - use latest TLS and if you need more security - a client and server certificates served separately and off the Tor network: EmerCoin is a great alternative to do so easily, ...


0

Well, if you achieve something - you're always paying for that. Tor provides you an alternative routing way for the cost of speed, so - even serving a static pages out of Memcached+NGinx will pay it's toll for anonymity if the Tor routing chain is laggy. If you have to serve your fully static site fast - take a look at ZeroNet and IPFS - they're much more ...


0

Well, the SEO topic is a big one, and that's my approach to it since 2000: Make a website really useful for the people, not tuned up for search bots Use all the matters possible to represent your content like tags suggests you It's OK to make some records in HTTP headers and HTML markup both: I've never experienced the problem regarding to this, only a ...


0

Well, you can easily utilize HTTP proxy from tor: it's been a while as it was added and built-in. For connecting to your server's services you can basically use anything you wish, but if you're about to have a very tunable playground for yourself - here is my advice how to build the things up: VirtualBox or ProxMox as a basement. If you don't need a ...


Top 50 recent answers are included