It's a big probability that it was a clock skew: on reboot many OS'es and distro's are updating the local time using NTP protocol, so - once you've got rebooted you had an accurate time and was able to join the network successfully.
This isn't the correct installation method for you to follow.
These instructions are for people who are already familiar with basic usage of OpenPGP
You're not following the instructions at all.
If you are doing the verification for the first time, download the Tails signing key and import it in your keyring. If you are working from ...
No. Your relay will lose some of its flags if it's offline for a period of time, but simply restarting doesn't seem to affect its consensus status.
I'm not sure if the consensus deteriorates if your relay is off for too long, but your relay shouldn't "reset" unless it's private key gets reset, or is off for long enough to get removed from the consensus.
You may have to run the installation program as Administrator. Right click on the program icon and choose "Run as Administrator". Works on Vista if you are running a 32 bit program via the 64 bit platform.
The tor package available through apt-get isn't needed or related to using Tor Browser.
As such the steps you performed as root won't affect the steps you performed to install Tor Browser, assuming you followed the steps given on the Tor Project site, e.g.:
# Download Tor Browser and it's signature
You have different possibilities to download Tor. Each comes with different advantages or disadvantages:
HTTP: This is the default method which is offered through the Tor website. Usually HTTP works for most users. Packages are digitally signed so the package manager can check if the correct version was downloaded.
HTTPS: If you use HTTPS, it might be a ...
Amnesic in terms of, for example Tails (The Amnesic Incognito Live System) it is the same as is meant by the medical term. From Wikipedia: "Anterograde amnesia is the inability to transfer new information from the short-term store into the long-term store."
Tails has a long-term memory, which is the basis of the operating system and stored on the live media ...
Your clock is wrong. Tor requires an accurate time, date, and timezone to work.
Given that your time is almost exactly 9 hours off, most likely the time on your computer looks correct, but you have incorrectly configured your timezone. Set the timezone correctly. This will most likely screw up the time. Fix the time after the timezone is correct.
Do not try to install Tor Browser into global directories, these require Administrator permissions to write to.
Instead install it to somewhere that your user account owns, like your Desktop or a similar location, this avoids the requirement for administrator privileges. Nothing about using Tor Browser should require administrator privileges and it would be ...
Welcome to the community and definitely thank you for using Tor =D
I just realized you mentioned Kali linux.
I'm also going to assume you meant you downloaded the Tor Browser Bundle?
With Kali Linux, you are logged in as root user(default but not the only option).
Tor Browser Bundle DOES NOT run with root permissions, it will let you know that if you ...
There may be several error due to the configuration.
1) run tor in terminal. Check the output. If it says cannot bind tor, there may be another instance of tor is running. try stop the tor service by:
sudo service stop tor
2) After running tor successfully, check what configuration file is read by tor. Maybe you have edited the wrong configuration file. ...
Works here, either the servers were down (unlikely) or you can't access them because they are blocked (e.g. Firewall)
You can import the key manually like this:
gpg --import PATH_TO_KEY
gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
You can get the key here
You're in the wrong directory.
The screenshot shows you running the command from your home directory (~) but the file exists in your Downloads directory (~/Downloads).
run cd Downloads then tar vJxf tor-browser-linux64-7.0a2-hardened-All.tar.xz
run tar vJxf ~/Downloads/tor-browser-linux64-7.0a2-hardened-All.tar.xz
You could also just open the ...
I believe from your explanation you may have only removed shortcuts to the application, and the source files still remain.
Method 1 - Windows
On Control Panel, go to Uninstall a Program and ensure there is no entry for TOR. If there is, uninstall from there.
1.Click the search bar at the bottom right of the screen
2.Type Control Panel and click ...
it is neither advised to use an outdated version of Tor nor an old OS! - they are deprecated (mostly) for a reason resp. not supported any more by security concerned software.
a possible solution could be a VM with a supported OS, but as long as your host is outdated and potentially insecure this is NOT a good idea! everything depending on insecure software ...
Remove, comment out or set to 0 the DisableNetwork line in your torrc config file.
When this option is set, we don’t listen for or accept any connections other than controller connections, and we close (and don’t reattempt) any outbound connections. Controllers sometimes use this option to avoid using the network until Tor is fully ...
The message itself comes from the start script. It checks if the current user has the id 0 (which is the root user) and exits with the message:
The Tor Browser Bundle should not be run as root. Exiting.
In general it is considered good security practise that one should not run software as root. Especially when one browses the web there are quite some ...
After skimming what I believe is the TorRequests source code, it looks like you either need to
properly point TorRequests at Tor Browser's ControlPort and SocksPort, or
add tor.exe to your path so TorRequests can launch Tor itself.
Option 1 is easier.
The example in the README tells you how to specify the socks and control port to use.
Tor Browser opens ...
Can that person be comfortable in assuming that their completely Anonymous when, using Tor or is there new steps or programs someone should use with Tor, or extra precautions they should take. I just cant honestly believe it can just be as simple as using a different browser, at least no stay that simple for long.
No, it's not and the Tor Project explicitly ...
You can also get the "No public key" error if you have imported an old version of the Tails signing key.
gpg --check-sigs A490D0F4D311A4153E2BB7CADBB802B258ACD84F
pub 4096R/58ACD84F 2015-01-18 [expired: 2017-01-11]
uid [ expired] Tails developers (offline long-term identity key) <firstname.lastname@example.org>
sig!3 58ACD84F 2015-01-18 Tails ...
As to Tiny Core Linux, I can't give specific instruction.
The Tor Project Wiki provides a guide on how to build Tor Browser.
The Tor Browser build process uses a system called Gitian for creating reproducible builds. To follow this method, since you don't have a pre-existing Ubuntu 14.04 installation or virtual machine, you'd be following the vagrant build ...
There are at least two questions lurking in your post, so let me try and sort them out.
Could the size of the thing you installed be different from the size
described on the torproject.org site?
How do you know whether the Tor program you have is really the one
that was made by the Tor project? (Note that I have plagiarized this
question from the Tor ...
The list of recommended versions contains 0.2.7.6, so it is not officially outdated.
If you want to use a newer version of Tor with Ricochet, just copy or link the Tor binary to the directory where Ricochet lives and start the software. Below you see a screenshot of Ricochet's settings which tells you that it runs with Tor version 0.2.8.8. I used the method ...
It's hard to tell exactly what might be causing this issue, since OSX is not giving a precise error message, but I have seen "operation timed out" errors with other dmg files when there is a problem with permissions.
I no longer use OSX, so this is just from memory; please bear with me if the layout or anything like that has changed!
Launch Disk Utility ...
Try using: gpg --keyserver pool.sks-keyservers.net --recv A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 instead. The server at keys.gnupg.net no longer exists.
So the new command should be:
gpg --keyserver pool.sks-keyservers.net --recv A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89
gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
Generally speaking, HTTPS is better than HTTP. But in case of the deb-packages it actually makes no sense at all : all the packages are digitally signed by the publisher's key. And - regardless of the safety of transport they were obtained - using a package manager enforces preliminary signature check. So if it was tampered with - it will fail, regardless of ...