PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Tor onion service: wo ist hostname Datei?



nisa
19.07.16, 18:01
Hallo,
Ich habe folgendes Problem: ich habe 1. apache installiert 2. Tor richtig konfiguriert.
Aber wo ist die hostname Datei? Die dateisuche zeigt mir sämtlich hostname Dateien, aber die richtige finde ich nicht :(
Oder steht onionshare im weg? Als verzeichniss habe ich /var/www/html angegeben.

Nils

florian0285
19.07.16, 20:05
/etc/hostname

Newbie314
19.07.16, 22:32
Ne, unter /etc liegt es sicher nicht.

Laut dieser Anleitung hier https://www.torproject.org/docs/tor-hidden-service.html.en sollte es die Datei sein die in dem Verzeichnis das du bei der Konfiguration unter HiddenServiceDir in deine torrc Datei eingetragen hast liegt. Mit dem Namen in der Datei solltest du deinen Server erreichen.

nisa
20.07.16, 18:39
Dort ist diese Datei nicht :(
Ich bin mir sicher, das Tor alle nötigen Zugriffsrechte hat.
Übrigens benutze ich Ubuntu 16.4 . in einer frischen Ubuntu Installation klappt es auch nicht :(

EDIT: Hier ist torrc:
## Configuration file for a typical Tor user
## Last updated 22 September 2015 for Tor 0.2.7.3-alpha.
## (may or may not work for much older or much newer versions of Tor.)
##
## Lines that begin with "## " try to explain what's going on. Lines
## that begin with just "#" are disabled commands: you can enable them
## by removing the "#" symbol.
##
## See 'man tor', or https://www.torproject.org/docs/tor-manual.html,
## for more options you can use in this file.
##
## Tor will look for this file in various places based on your platform:
## https://www.torproject.org/docs/faq#torrc

## Tor opens a SOCKS proxy on port 9050 by default -- even if you don't
## configure one below. Set "SOCKSPort 0" if you plan to run Tor only
## as a relay, and not make any local application connections yourself.
#SOCKSPort 9050 # Default: Bind to localhost:9050 for local connections.
#SOCKSPort 192.168.0.1:9100 # Bind to this address:port too.

## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SOCKSPolicy is set, we accept
## all (and only) requests that reach a SOCKSPort. Untrusted users who
## can access your SOCKSPort may be able to learn about the connections
## you make.
#SOCKSPolicy accept 192.168.0.0/16
#SOCKSPolicy accept6 FC00::/7
#SOCKSPolicy reject *

## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many Log lines as
## you want.
##
## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
##
## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
#Log notice file /var/log/tor/notices.log
## Send every possible message to /var/log/tor/debug.log
#Log debug file /var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
#Log notice syslog
## To send all messages to stderr:
#Log debug stderr

## Uncomment this to start the process in the background... or use
## --runasdaemon 1 on the command line. This is ignored on Windows;
## see the FAQ entry if you want Tor to run as an NT service.
#RunAsDaemon 1

## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
#DataDirectory /var/lib/tor

## The port on which Tor will listen for local connections from Tor
## controller applications, as documented in control-spec.txt.
#ControlPort 9051
## If you enable the controlport, be sure to enable one of these
## authentication methods, to prevent attackers from accessing it.
#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701A D684053EC4C
#CookieAuthentication 1

############### This section is just for location-hidden services ###

## Once you have configured a hidden service, you can look at the
## contents of the file ".../hidden_service/hostname" for the address
## to tell people.
##
## HiddenServicePort x y:z says to redirect requests on port x to the
## address y:z.

HiddenServiceDir /var/www/html/
HiddenServicePort 8080 127.0.0.1:8080

#HiddenServiceDir /var/lib/tor/other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServicePort 22 127.0.0.1:22

################ This section is just for relays #####################
#
## See https://www.torproject.org/docs/tor-doc-relay for details.

## Required: what port to advertise for incoming Tor connections.
#ORPort 9001
## If you want to listen on a port other than the one advertised in
## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as
## follows. You'll need to do ipchains or other port forwarding
## yourself to make this work.
#ORPort 443 NoListen
#ORPort 127.0.0.1:9090 NoAdvertise

## The IP address or full DNS name for incoming connections to your
## relay. Leave commented out and Tor will guess.
#Address noname.example.com

## If you have multiple network interfaces, you can specify one for
## outgoing traffic to use.
# OutboundBindAddress 10.0.0.5

## A handle for your relay, so people don't have to refer to it by key.
#Nickname ididnteditheconfig

## Define these to limit how much relayed traffic you will allow. Your
## own traffic is still unthrottled. Note that RelayBandwidthRate must
## be at least 20 kilobytes per second.
## Note that units for these config options are bytes (per second), not
## bits (per second), and that prefixes are binary prefixes, i.e. 2^10,
## 2^20, etc.
#RelayBandwidthRate 100 KBytes # Throttle traffic to 100KB/s (800Kbps)
#RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB (1600Kb)

## Use these to restrict the maximum traffic per day, week, or month.
## Note that this threshold applies separately to sent and received bytes,
## not to their sum: setting "40 GB" may allow up to 80 GB total before
## hibernating.
##
## Set a maximum of 40 gigabytes each way per period.
#AccountingMax 40 GBytes
## Each period starts daily at midnight (AccountingMax is per day)
#AccountingStart day 00:00
## Each period starts on the 3rd of the month at 15:00 (AccountingMax
## is per month)
#AccountingStart month 3 15:00

## Administrative contact information for this relay or bridge. This line
## can be used to contact you if your relay or bridge is misconfigured or
## something else goes wrong. Note that we archive and publish all
## descriptors containing these lines and that Google indexes them, so
## spammers might also collect them. You may want to obscure the fact that
## it's an email address and/or generate a new address for this purpose.
#ContactInfo Random Person <nobody AT example dot com>
## You might also include your PGP or GPG fingerprint if you have one:
#ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>

## Uncomment this to mirror directory information for others. Please do
## if you have enough bandwidth.
#DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised in
## DirPort (e.g. to advertise 80 but bind to 9091), you can do it as
## follows. below too. You'll need to do ipchains or other port
## forwarding yourself to make this work.
#DirPort 80 NoListen
#DirPort 127.0.0.1:9091 NoAdvertise
## Uncomment to return an arbitrary blob of html on your DirPort. Now you
## can explain what Tor is if anybody wonders why your IP address is
## contacting them. See contrib/tor-exit-notice.html in Tor's source
## distribution for a sample.
#DirPortFrontPage /etc/tor/tor-exit-notice.html

## Uncomment this if you run more than one Tor relay, and add the identity
## key fingerprint of each Tor relay you control, even if they're on
## different networks. You declare it here so Tor clients can avoid
## using more than one of your relays in a single circuit. See
## https://www.torproject.org/docs/faq#MultipleRelays
## However, you should never include a bridge's fingerprint here, as it would
## break its concealability and potentially reveal its IP/TCP address.
#MyFamily $keyid,$keyid,...

## A comma-separated list of exit policies. They're considered first
## to last, and the first match wins.
##
## If you want to allow the same ports on IPv4 and IPv6, write your rules
## using accept/reject *. If you want to allow different ports on IPv4 and
## IPv6, write your IPv6 rules using accept6/reject6 *6, and your IPv4 rules
## using accept/reject *4.
##
## If you want to _replace_ the default exit policy, end this with either a
## reject *:* or an accept *:*. Otherwise, you're _augmenting_ (prepending to)
## the default exit policy. Leave commented to just use the default, which is
## described in the man page or at
## https://www.torproject.org/documentation.html
##
## Look at https://www.torproject.org/faq-abuse.html#TypicalAbuses
## for issues you might encounter if you use the default exit policy.
##
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down.
##
## For security, by default Tor rejects connections to private (local)
## networks, including to the configured primary public IPv4 and IPv6 addresses,
## and any public IPv4 and IPv6 addresses on any interface on the relay.
## See the man page entry for ExitPolicyRejectPrivate if you want to allow
## "exit enclaving".
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports on IPv4 and IPv6 but no more
#ExitPolicy accept *:119 # accept nntp ports on IPv4 and IPv6 as well as default exit policy
#ExitPolicy accept *4:119 # accept nntp ports on IPv4 only as well as default exit policy
#ExitPolicy accept6 *6:119 # accept nntp ports on IPv6 only as well as default exit policy
#ExitPolicy reject *:* # no exits allowed

## Bridge relays (or "bridges") are Tor relays that aren't listed in the
## main directory. Since there is no complete public list of them, even an
## ISP that filters connections to all the known Tor relays probably
## won't be able to block all the bridges. Also, websites won't treat you
## differently because they won't know you're running Tor. If you can
## be a real relay, please do; but if not, be a bridge!
#BridgeRelay 1
## By default, Tor will advertise your bridge to users through various
## mechanisms like https://bridges.torproject.org/. If you want to run
## a private bridge, for example because you'll give out your bridge
## address manually to your friends, uncomment this line:
#PublishServerDescriptor 0

Ausgabe von "sudo tor":

Jul 20 18:47:38.713 [notice] Tor v0.2.7.6 (git-605ae665009853bd) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2g-fips and Zlib 1.2.8.
Jul 20 18:47:38.714 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jul 20 18:47:38.714 [notice] Read configuration file "/etc/tor/torrc".
Jul 20 18:47:38.717 [warn] Permissions on directory /var/www/html/ are too permissive.
Jul 20 18:47:38.717 [warn] Failed to parse/validate config: Failed to configure rendezvous options. See logs for details.
Jul 20 18:47:38.717 [err] Reading config failed--see warnings above.

florian0285
20.07.16, 19:45
See log for Details

/var/log/tor/

die Berechtigungen für html sind auch zu freizügig. Es sollte nur der Tor-Service Zugriff haben und ggf die Gruppe.

Newbie314
20.07.16, 21:07
## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
#DataDirectory /var/lib/tor

Du hast "DataDirectory" nicht auskommentiert (also den # nicht entfernt) also ist es nicht aktiv. Wenn du den Text drüber liest wirst du sehen dass in dem Nutzerverzeichnis des Nutzers unter dem du die ganze Sache installiert hast ein .tor (verstecktes) Directory sein muss in dem die ganzen Dateien zu finden sein sollten.

Mir fällt bei deiner Datei eh auf dass gar nichts auskommentiert ist, d.h. dein Tor Dienst läuft mit den Standardeinstellungen. Wenn er läuft.

Newbie314
20.07.16, 21:27
Edit: ich wurde gerade von "Black Adder" ausgelacht weil ich das nicht gesehen habe:



## Once you have configured a hidden service, you can look at the
## contents of the file ".../hidden_service/hostname" for the address
## to tell people.
##
## HiddenServicePort x y:z says to redirect requests on port x to the
## address y:z.

HiddenServiceDir /var/www/html/
HiddenServicePort 8080 127.0.0.1:8080

ist eine massive Sicherheitslücke. Bitte nimm den Apache vom Netz und lies dich solange ein bis dir klar wird warum das keine gute Idee war. Erst dann solltest du den Tor Dienst neu aufsetzen- so ist das kein anonymer Dienst sondern eher eine Art Selbstbedienungsladen.

nopes
20.07.16, 21:43
Aber es geht doch genau darum eine Seite im Darknet zu hosten oder ich kapiere es nicht ;)

Newbie314
20.07.16, 22:27
Mit Namensschild dran- und private Key damit jemand Anderer unter dem eigenen Namen Straftaten begehen kann?

Ich glaube nicht dass nisa das in der Form vorhat. Wenn ja: lass die Kiste ruhig laufen, da finden sich bestimmt Interessenten.

florian0285
20.07.16, 22:29
Würd auch gern wissen was an der Config ein Einfallstor ist?

nopes
20.07.16, 22:58
Also nur für den Fall, dass du wirklich eine Seite im Onion-Netz betreiben willst - https://www.torproject.org/docs/tor-hidden-service.html.en gleiche deine Konfiguration mit "Step 2" von denen ab, prüfe auch noch mal "Step 1", weil https://www.reddit.com/r/onions/comments/1hft2m/how_can_i_host_a_website_on_the_tor_network/ da insbesondere https://www.reddit.com/r/onions/comments/1hft2m/how_can_i_host_a_website_on_the_tor_network/caty83e -> also schon mit bedacht vorgehen

Falls du einfach nur Browsen willst, stimme ich den Einwand zu -> weg damit

Wie auch immer viel Erfolg.

Newbie314
20.07.16, 23:18
Man kann per http seinen private key downloaden.

http => IP => er ist nicht mehr anonym.
Private Key: irgendein Gauner kann unter seiner ID eine Verbrecherseite aufmachen. Durch den IP Fehler würde die Polizei bei ihm anklopfen. Da hätte er erstmal ne Menge Ärger bis klar wäre warum er fälschlich in Verdacht geriet.

Daher mein Rat den Server stillzulegen und nochmal in aller Ruhe nachzulesen.

Ich betreibe übrigens keinen Server im www, mein Apache darf nur stundenweise unter meiner Aufsicht ins www während gerade Familienmitglieder Fotos von Familienfete auf meinen PC laden. Senkt den Blutdruck wenn man keinen Server 24/7 im www hat.

nopes
20.07.16, 23:27
Jein, man muss natürlich dafür sorgen, dass der private Schlüssel nicht vom HTTP-Server ausgeliefert wird, wie ich sagte mit bedacht - Auszug aus deren Doku dazu:
HiddenServiceDir is a directory where Tor will store information about that hidden service. In particular, Tor will create a file here named hostname which will tell you the onion URL. You don't need to add any files to this directory. Make sure this is not the same directory as the hidserv directory you created when setting up thttpd, as your HiddenServiceDir contains secret information!Also ruhig Blut, mit bedacht halt, dass was "geservt" wird soll doch ganz ausdrücklich in einem anderen Verzeichnis liegen ;)

[edit]Dann etwas tiefer:
Now save the torrc and restart your tor.

If Tor starts up again, great. Otherwise, something is wrong. First look at your logfiles for hints. It will print some warnings or error messages. That should give you an idea what went wrong. Typically there are typos in the torrc or wrong directory permissions (See the logging FAQ entry (https://www.torproject.org/docs/faq.html.en#Logs) if you don't know how to enable or find your log file.)When Tor starts, it will automatically create the HiddenServiceDir that you specified (if necessary), and it will create two files there.

private_key
First, Tor will generate a new public/private keypair for your hidden service. It is written into a file called "private_key". Don't share this key with others -- if you do they will be able to impersonate your hidden service.

hostname
The other file Tor will create is called "hostname". This contains a short summary of your public key -- it will look something like duskgytldkxiuqc6.onion. This is the public name for your service, and you can tell it to people, publish it on websites, put it on business cards, etc.
If Tor runs as a different user than you, for example on OS X, Debian, or Red Hat, then you may need to become root to be able to view these files.

Now that you've restarted Tor, it is busy picking introduction points in the Tor network, and generating a hidden service descriptor. This is a signed list of introduction points along with the service's full public key. It anonymously publishes this descriptor to the directory servers, and other people anonymously fetch it from the directory servers when they're trying to access your service.

Try it now: paste the contents of the hostname file into your web browser. If it works, you'll get the html page you set up in step one. If it doesn't work, look in your logs for some hints, and keep playing with it until it works.
Also wirklich, was nen "gebashe" (sorry), ist doch angeblich alles richtig konfiguriert -> keine Gefahr für deinen privaten Schlüssel soweit ich das blicke ;)

florian0285
20.07.16, 23:49
Naja doch... wenn der Apache auf den HiddenServiceDir zeigt wäre der Inhalt theoretisch sichtbar. Davon abgesehen startet Apache als www-data und tor als root. Da ein private key i. R. mit den Rechten 600 angelegt wird sollte ihn niemand lesen können. Trotzdem hat Newbie recht der HiddenServiceDir sollte in einen localen leeren Ordner zeigen.
Den Zugriff auf /var/www regelt man dann durch apache.

nopes
20.07.16, 23:51
jupp brain.exe ist gefordert - wie ich schon geschrieben habe: mit bedacht (auch an die in "Step 1" erwähnten Meldungen vom Web-Server usw. denken ;))

florian0285
20.07.16, 23:53
Ich sehe aber immer noch keine logfiles?

nisa
21.07.16, 06:54
Also soll HiddenServiceDir nicht nach /var/www/html/ zeigen sondern z.B. nach /var/onion/
zeigen und die hostname datei ist dann also in /root/.tor ?
Ich glaub ich verstehe... Ich werde heute nachmittag mal nachgucken.

Newbie314
21.07.16, 08:12
Tor sollte soweit ich gelesen habe auch nicht als root laufen. Evtl. eigenen User einrichten.

florian0285
21.07.16, 11:09
Ne die ist dann in /var/onion/hostname