Silk Road forums

Discussion => Off topic => Topic started by: helpmywife on July 28, 2013, 03:47 pm

Title: how to build a .onion website for free???
Post by: helpmywife on July 28, 2013, 03:47 pm
can someone help me, its going to be just 1page of information for ppl to read. Its just going to have lines of 1.5 spaced print and 2-3 small pics(maybe)
Title: Re: how to build a .onion website for free???
Post by: CannabisConsumer on July 28, 2013, 07:22 pm
Here is a clearnet tutorial, obviously put noscript on when on it.

http://www.makeuseof.com/tag/create-hidden-service-tor-site-set-anonymous-website-server/
Title: Re: how to build a .onion website for free???
Post by: helpmywife on July 28, 2013, 11:14 pm
should the "S!" in the left corner of iceweasel if the "S" does not have a line going through it that means in NOT forbidding scripts that i want to forbit right?
Title: Re: how to build a .onion website for free???
Post by: astor on July 29, 2013, 02:15 am
Yeah, the S should have the circle with the bar going through it -- ie the universal symbol for "no" :) -- on top of it, when scripts are blocked.
Title: Re: how to build a .onion website for free???
Post by: helpmywife on July 29, 2013, 03:42 am
why dont i want to block scripts always and just with clearnet?
Title: Re: how to build a .onion website for free???
Post by: astor on July 29, 2013, 08:19 am
That's mostly a myth perpetuated in onionland. I don't know where it started, but I first noticed it on the Hidden Wiki, where clearnet links were labeled with big warnings. Then people did it on this forum. For some reason, people believe clearnet sites are more dangerous than hidden services.

A hidden service could supply malicious scripts just as easily as a clearnet site, and a hidden service operator knows that his visitors don't want to be identified, so he may have more interest / reason to try to deanonymize them, whereas random clearnet sites don't give a shit about identifying proxy users. They just block them if they become a nuisance.

The likelihood of getting pwned by some random JavaScript is vanishingly small, while blocking scripts will break a lot of functionality on clearnet sites. I've been using Tor for years, mostly without blocking scripts, and it hasn't been a problem so far. Of course it could be, but the cost-benefit analysis doesn't make me worry about it.
Title: Re: how to build a .onion website for free???
Post by: helpmywife on July 29, 2013, 01:38 pm
but if you never put actual info in just "eye browsing" then what dif does it make? i assumed tails, and the bridges i use are enough?? also do you think it matters obfs bridges or reg ones?
Title: Re: how to build a .onion website for free???
Post by: mcguire39 on July 29, 2013, 02:36 pm
You might want to check out Freedom Hosting but you need an invite code http://xqz3u5drneuzhaeo.onion/

I assumed the clearnet warning was done so you'd know you'd be popping out a tor exit node if you click the link?
Title: Re: how to build a .onion website for free???
Post by: CannabisConsumer on July 31, 2013, 01:38 am
but if you never put actual info in just "eye browsing" then what dif does it make? i assumed tails, and the bridges i use are enough?? also do you think it matters obfs bridges or reg ones?
Noscript is just an extra layer of security. The basic idea would be that I am not(but most obviously could be) a government agent who is trying to send you to a honeypot link, just finding a random link on normal websites is more than likely not a honeypot link but I would never trust a link that I got from anyone on Tor.

It's just an extra safety precaution as websites can use tools such as javascript, flash, ect in order to identify you.

So say I was a government agent who signed up this account for the sole intent of investigating you. I could watch your threads and wait for you to ask for help, send you to a fake link which reveals your true IP or other identifying information.

Again as another guy said it's just paranoia but better safe than sorry, safe than sorry, safe than sorry, safe than sorry.