#ONION TOR VIEWER INSTALL#

Copy the public key: $ cat /tmp/k1.pub.key Public key $ openssl pkey -in /tmp/k1.prv.pem -pubout | grep -v ' PUBLIC KEY' | base64pem -d | tail -bytes=32 | base32 | sed 's/=//g' > /tmp/k1.pub.key Private key $ cat /tmp/k1.prv.pem | grep -v ' PRIVATE KEY' | base64pem -d | tail -bytes=32 | base32 | sed 's/=//g' > /tmp/k1.prv.key If you get an error message, something has gone wrong and you cannot continue until you've figured out why this didn't work. Generate a key using the algorithm x25519: $ openssl genpkey -algorithm x25519 -out /tmp/k1.prv.pem

#ONION TOR VIEWER INSTALL#

To manually generate the keys, you need to install openssl version 1.1+ and basez. Following the instructions described in the section Setup will automatically create this directory.Ĭlient authorization will only be enabled for the service if tor successfully loads at least one authorization file.įor now, you need to create the keys yourself with a script (like these written in Bash, Rust or Python) or manually. To configure client authorization on the service side, the /authorized_clients/ directory needs to exist. Configuring v3 Onion Services Service side If no authorization is configured, the service will be accessible to anyone with the onion address. Note: Once you have configured client authorization, anyone with the address will not be able to access it from this point on. The service side is configured with a public key and the client can only access it with a private key. It requires Tor clients to provide an authentication credential in order to connect to the Onion Service.įor v3 Onion Services, this method works with a pair of keys (a public and a private).

Client authorization is a method to make an Onion Service private and authenticated.

Onion tor viewer