|
|
Post by pharrisire on Mar 10, 2012 14:54:54 GMT -5
What, and where, are the commands/instructions for
the newly included Tor and Privoxy?
|
|
|
|
Post by Kevin McAleavey on Mar 10, 2012 20:30:53 GMT -5
What, and where, are the commands/instructions for the newly included Tor and Privoxy? Pretty painless indeed here. We don't recommend using privoxy although the executable is there after being installed by TOR. The reason why we don't recommend it is that it sets up a listening server and that's a potential security hole. Instead, you'll need to go get a firefox addon called "FoxyProxy" and install it. It'll be saved with KNOS_PREFS once you do so and back that up so you only have to do this once. Install FoxyProxy and reload Firefox after you've installed it. You'll notice the FoxyProxy fox up on the Firefox address bar between where you type in URL's and the search entry place up top there. Click it to open Foxyproxy after it's been installed and configure it to "Add new proxy" at 127.0.0.1 and select port 9050. Do this as a "manual proxy configure" in the "Details" tab and be sure to select SOCKS Proxy and check SOCKS v5 for the highest safety. If you don't want to bother physically selecting specific URL's, let it default to "use for all URL's. Up on the top there, you'll be able to select between "use FoxyProxy for all URL'S" or completely disable FoxyProxy when you're not using TOR. That's how I do it. You're welcome to play with and customize it yourself if you wish, when you back up app settings the right way, these will all be stored for you by KNOS for future use. Once you have that configured, you can then use TOR. Open up a terminal by selecting Applications, Accessories, and finally Terminal. When the terminal opens, just type in tor and hit enter. You can watch tor set itself up and when it's 100% completed, MINIMIZE the terminal and you're using TOR. Tor will remain running until you hit ctrl-C in that terminal to make it exit or close the terminal to kill tor. When you're NOT running Tor, you need to go into FoxyProxy and turn off the proxy by selecting "completely disable FoxyProxy" and you're back to normal surfing again. Be sure to disable java, javascript, cookies and all that stuff in Firefox if you want your tor session to be completely private, or use "private browsing" in Firefox. To VERIFY that TOR is working once you're all lit up, surf to: check.torproject.org/It will verify your TOR status ... |
|
|
|
Post by pharrisire on May 5, 2012 10:34:26 GMT -5
Got FoxyProxy set up as instructed, but Tor will not
start up,
and even though I followed your instructions
for "Backup app settings" all settings are lost on reboot -
KNOS_PREFS does not exist anywhere
so I am starting from scratch again.
["KNOS_PREFS64" for desktop
and "KNOS_PREFS" for Lenovo,
Toshiba is still hopeless]
|
|
|
|
Post by pharrisire on May 5, 2012 10:50:07 GMT -5
Here's where it hangs on both Lenove and desktop:
[KNOS@KNOS-32 ~]$ tor
May 05 11:39:23.495 [notice] Tor v0.2.2.33 (git-8522652d8e9213d4). This is experimental software. Do not rely on it for strong anonymity. (Running on FreeBSD i386)
May 05 11:39:23.515 [notice] Initialized libevent version 2.0.13-stable using method kqueue. Good.
May 05 11:39:23.518 [notice] Opening Socks listener on 127.0.0.1:9050
May 05 11:39:23.553 [notice] Parsing GEOIP file /usr/local/share/tor/geoip.
May 05 11:39:24.195 [notice] OpenSSL OpenSSL 0.9.8q 2 Dec 2010 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
May 05 11:39:24.687 [notice] Bootstrapped 5%: Connecting to directory server.
May 05 11:39:24.689 [notice] I learned some more directory information, but not enough to build a circuit: We have no network-status consensus.
May 05 11:39:24.799 [notice] Bootstrapped 10%: Finishing handshake with directory server.
May 05 11:39:25.450 [notice] Bootstrapped 15%: Establishing an encrypted directory connection.
May 05 11:39:25.706 [notice] Bootstrapped 20%: Asking for networkstatus consensus.
May 05 11:39:26.033 [warn] Received directory with skewed time (server '212.112.245.170:443'): It seems that our clock is behind by 4 hours, 1 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
May 05 11:39:26.051 [notice] I learned some more directory information, but not enough to build a circuit: We have no network-status consensus.
May 05 11:39:26.645 [notice] Bootstrapped 25%: Loading networkstatus consensus.
May 05 11:39:29.028 [warn] Received directory with skewed time (server '208.83.223.34:80'): It seems that our clock is behind by 4 hours, 1 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
May 05 11:39:29.155 [warn] Our clock is 3 hours, 20 minutes behind the time published in the consensus network status document (2012-05-05 15:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 05 11:39:29.155 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
|
|
|
|
Post by Kevin McAleavey on May 5, 2012 23:45:10 GMT -5
We've got the preferences problem solved, but on the stick you're booting from (looking at old diagnostics) there's a problem with it and the system it's starting from on that desktop. We've redone the SCSI code, so hopefully that's fixed now.
As to your backup app settings, where were you saving them to? You should be able to go to that device and see KNOS_PREFS.tar.gz or KNOS_PREFS64.tar.gz on it (depending on whether 32 or 64 KNOS) and be able to open it by doubleclicking on it. We've redone that code as well but going by your old diagnostics, didn't see any sign of a personal area on your boot stick nor any other stick plugged in when you booted up. The file has to be plugged in when you boot up for KNOS to read it.
As for TOR, looks like your computer's clock is off and so a couple of questions in order to correct that so TOR will work (we've also redone TOR and replaced it with "Vidalia" to control it on the main menu in the release version). Check what time is displayed up top. If it is correct, then we'll need to set up your time/date settings. But first, is the time in the upper right corner correct? If so, it would mean that Windows has set your time to "local time" instead of the proper GMT time that TOR is looking for, and in addition, we'll have to set local proper time for KNOS and that will solve the TOR complaint. It's being told that you're in one time zone, but system time does not agree and that's why it's complaining.
|
|
|
|
Post by pharrisire on May 7, 2012 13:53:49 GMT -5
""As to your backup app settings, where were you saving them to?""
On both Lenovo32(KNOS_PREFS.tar.gz) and desktop64(KNOS_PREFS64.tar.gz) I saved the prefs
in BOTH the KNOS folder And the desktop,
and on both machines neither location survived reboot.
|
|
|
|
Post by Kevin McAleavey on May 8, 2012 4:34:55 GMT -5
""As to your backup app settings, where were you saving them to?"" On both Lenovo32(KNOS_PREFS.tar.gz) and desktop64(KNOS_PREFS64.tar.gz) I saved the prefs in BOTH the KNOS folder And the desktop, and on both machines neither location survived reboot. Aha! NOW we're getting somewhere. Both of those locations are within the archive that gets backed up. So there's no way that we can read in anything from there. The data has to be backed up onto a drive that's readable as KNOS is booting! If KNOS were installed on a hard drive, then there would be space available there to find the file. If you're booting from a 4GB USB stick, then there isn't room for a personal area there but there IS on a stick that's 8GB or larger. Only remaining option would be to have a second USB stick that people use to store files and data from KNOS on plugged in along with the other one or booted from a DVD. If you have a second stick, that's where you'd want to save the file. It cannot be saved internally on KNOS because security won't permit that, and putting it inside what it's backing up won't work either since the entire "lockbox" from there is saved as the archive, including that file you're saving inside it. None of that gets read until after the desktop is started ... There's the problem!  I'll be sure to mention that in our user manual - never occured to me that we would be confusing folks with that. |
|
|
|
Post by pharrisire on May 8, 2012 12:37:03 GMT -5
Lenovo is ~30G drive. In the previous versions the extra space has shown in the file browser, but now it only shows -KNOS -Desktop -File System -Network and -Trash Attachments:
|
|
|
|
Post by Kevin McAleavey on May 8, 2012 23:59:48 GMT -5
Lenovo is ~30G drive. In the previous versions the extra space has shown in the file browser, but now it only shows -KNOS -Desktop -File System -Network and -Trash Yep ... see my other response here: knosproject.proboards.com/index.cgi?action=gotopost&board=9rc&thread=179&post=839Somehow your install onto the hard drive didn't go correctly. You should have a personal space there and you don't. The reply I just did in the "sleep/Lenovo" thread shows what to do in order to get that working for you ... |
|
|
|
Post by pharrisire on May 10, 2012 14:55:26 GMT -5
"" Check what time is displayed up top. If it is correct, then we'll need to set up your time/date settings. But first, is the time in the upper right corner correct? If so, it would mean that Windows has set your time to "local time" instead of the proper GMT time that TOR is looking for, and in addition, we'll have to set local proper time for KNOS and that will solve the TOR complaint. It's being told that you're in one time zone, but system time does not agree and that's why it's complaining. "" Yes, the time shown is correct. When I right-click the time and go to preferences and try to click 'set system time' it pops up "Privileges are required to change the system time", but nothing happens when I click the 'Authenticate' button. And even though there is no Windows on this machine its still messing things up?  ? |
|
|
|
Post by Kevin McAleavey on May 14, 2012 0:20:22 GMT -5
"" Check what time is displayed up top. If it is correct, then we'll need to set up your time/date settings. But first, is the time in the upper right corner correct? If so, it would mean that Windows has set your time to "local time" instead of the proper GMT time that TOR is looking for, and in addition, we'll have to set local proper time for KNOS and that will solve the TOR complaint. It's being told that you're in one time zone, but system time does not agree and that's why it's complaining. "" Yes, the time shown is correct. When I right-click the time and go to preferences and try to click 'set system time' it pops up "Privileges are required to change the system time", but nothing happens when I click the 'Authenticate' button. And even though there is no Windows on this machine its still messing things up? ? Once again, so close ... because time setting is considered a critical security matter, and requires the most fleeting of opening of our security to permit the change to be made, it's all about timing on that "authenticate" window. Have faith that for the shortest time possible, the authentication DID go through but the window closed before you got to the button. Click it once, and then go up to the top right corner and click the close button. An new icon will appear up on the top by the volume control that looks like a keypad in our default theme - IIRC, it may look like a padlock in the one you've chosen. Click that and it will disappear and your system clock will be set. Unix systems are fussy about this becaus time stamps are considered a legal record and thus security is imposed on the system time. That should do it. You can also click on the time/date thing up on top and edit your local time zone after you've done this because what you'll be doing is setting your system to the proper GMT time. Windows does things backwards and the reason why the time error was complained about is that the time was originally set in Windows to display local time correctly. Unix runs on GMT so that everybody's on the same time across the planet. That's what TOR was complaining about. What I'd suggest right now though is wait until you get your copy of the retail release - should be out hopefully tomorrow night. We're in the process of shipping it to manufacturing now as I type. You may not need to do this with the actual release, but if the same complaint comes up again on the final release, this is what you'll need to do in order to fix that. Be happy to help further if you need it. In the release version, there will be an icon in the Internet group of apps on the main menu marked "Vidalia" ... this will be what you'll be using to run TOR instead of our trial using the terminal, all nice and neat ... so hang on before doing anything until you're running our actual release. You might not have to do anything! |
|
?