According to the manual, there are two configuration options (i.e. things you put in your torrc):
HidServAuth is what can be used on the client. It allows you to provide authentication cookies for hidden services as in HidServAuth <onion-address> <auth-cookie>.
HiddenServiceAuthorizeClient is the server side companion.
A hidden service is truly hidden, this add another layer to discriminate clients.
In traditional HS, a hidden server publish in the tor network how to begin a communication with it (not its true location, tor uses a complex middle nodes link setup for bidirectional route anonymization, the server and client knows nothing about end point's location, same for ...
Your Tor is probably under the impression that it has already created one. (Maybe it did and you deleted it?)
Try the following:
Edit your torrc to set CookieAuthentication to 0
reset your Tor (kill -HUP or hit x twice in Arm)
Edit your torrc again to set CookieAuthentication back to 1
reset your Tor again.
You should now have a new control cookie.
how does it work?
Clients must authenticate to create a successful rendezvous circuit.
can it see the activity of my h.s.?
That depends what you mean by activity, they could track the publication of it's descriptor for example (with basic, less-so with stealth) but they'd be unable to make a successful rendezvous circuit.
Can this configuration ...
And easy description of how HS works. You HS server choose some random nodes, this nodes only relay info from the client to the HS if a client ask about the HS to them. Then the HS publish this info to the tor directory.
Before a client want to connect to a HS, first choose a ramdom node, this node (rendezvous node) will relay data from the HS to the ...
NTLM is disabled by intent, apparently due to an embargoed Mozilla bug (I.E. the details aren't public), this is done through patching. The change is hardcoded into the browser so editing preferences won't make any difference. It's applied through this patch.
The associated ticket for the patch can be found here: #12974.
(My suspicion is that this can lead ...
Locate the file control_auth_cookie
Enter hexdump -e '32/1 "%02x""\n"' $COOKIEFILE where $COOKIEFILE is the location of the file from step 1.
Copy the output
Open a shell and enter telnet 127.0.0.1 9151. If you can't get a connection check if Tor listens on that port. Other versions listens on port 9050.
When you see a prompt enter AUTHENTICATE $OUTPUTFROM2 ...
There's a great video example here from AdaFruit showing how to get it running on a Raspberry Pi. The links below the video have a load more useful links. It's insanely easy.