Custom Query (26254 matches)


Show under each result:

Results (148 - 150 of 26254)

Ticket Resolution Summary Owner Reporter
#30312 user disappeared Tor Relay Guide / DebianUbuntu Nusenu siggi

This instruction doesn't match the file:

#change the nickname "myNiceRelay" to a name that you like Nickname myNiceRelay ORPort 443

these lines aren't there:

ExitRelay 0 SocksPort 0 ControlSocket 0

ContactInfo is changeable:

# Change the email address bellow and be aware that it will be published ContactInfo tor-operator@your-emailaddress-domain

  • what should happen after this command:

systemctl restart tor@default

I get no responce!

#30445 user disappeared some suggestions to the tor relay guide Nusenu caioau

Hello, I have some suggestions that I did in my relays to be listed in the relay guide, they are:

  1. create a non root user add that user to sudo group: root acess should be disabled from ssh, so we need to create another user, the set PermitRootLogin no in the sshd_config
  1. ssh hardening

2.1 get new ssh host keys:

delete old keys (we cannot be sure if new keys were generated, so its good to generate new keys)

sudo -s
cd /etc/ssh
rm ssh_host_*
ssh-keygen -t rsa -b 4096 -f ssh_host_rsa_key
ssh-keygen -t ed25519 -f ssh_host_ed25519_key

2.2 disable insecure ssh ciphers: openssh uses some insecure ciphers, se in

just put the followings lines in the sshd_config



2.3 disable password authentication and only use public key authentication:

in your machine run:

ssh-keygen -t ed25519 -o -a 300 -f ~/.ssh/key

then copy to the server:

ssh-copy-id -i ~/.ssh/key user@server

then try login in with the key ( -i points to the keyfile)

then make sure that on the sshd_config has this settings:

PubkeyAuthentication yes
PasswordAuthentication yes
PermitEmptyPasswords no

2.4 (optional) change the default port, there are alot of bots trying to get in , so changing the port makes sense to make their job more difficult

run: to get an random port number

python -c 'from random import SystemRandom as r; print(r().randint(49152,65535))'

the change it in the Port setting in the sshd_config

2.5 limit the brute force, you can use fail2ban, but I find it simpler to use ufw and instead of allowing ssh use the limit.

3.1 enable swap, sometimes when linux is out of memory then it kills the tor process, so creating swap prevents that, or even better use zram.

#4032 fixed HTTPS Everywhere breaks "see all videos" and "large window" in YouTube OsamaK Alan_De_Smet

(The links below might not be safe for work, there is some swearing. It happens to be the pages I was looking at when I identified HTTPS Everywhere as the trigger.)

When viewing a specific YouTube video (eg ) There is in the bottom right of the video sub-window arrows pointing right and down; clicking it makes the video portion of the web page larger (but not full screen). When HTTP Everywhere is enabled, this no longer works.

When looking at a user page (eg ) in the upper right portion of the page is an icon of a three by three grid of boxes; it changes the page to show all of a user's videos in a grid. When HTTP Everywhere is enabled, this no longer works.

I am not using any custom rulesets. For both cases, I have NOT enabled the YouTube rule, which defaults to off since it's buggy. I have tried turning all of the Google related rules (API, Search, Images, and Services) and restarting Firefox, that doesn't help. Disabling HTTPS Everyhwere entirely and restarting Firefox fixes the problem. I disabled all of my other add-ons and re-confirmed both the working and non-working cases.

Firefox 6.0.2 HTTPS Everywhere 1.0.1 Linux (Ubuntu 11.04)

If there is other information I can provide that will help, please let me know.

Note: See TracQuery for help on using queries.