search

nicksieger / sheepsafe

Keep safe from FireSheep
MIT License
211 stars 11 forks source link

access has been blocked #13

Open mikeymicrophone opened 13 years ago

mikeymicrophone commented 13 years ago

I installed sheepsafe and configured it with my dreamhost ssh access. I added my current network as trusted. I am not able to access the web.

I ran sheepsafe proxy down and sheepsafe uninstall to no avail. When I open a new terminal it can still access the sheepsafe binary. (with which sheepsafe)

I looked in my ~/Library/LaunchAgents directory, and there does not appear to be a sheepsafe.plist.

I can still ssh into my dreamhost account and ping github from the command line. When I try to use a browser it returns the "can't connect" page immediately.

mikeymicrophone commented 13 years ago

here are a few remedies I've considered.

deleting the binary and restarting the mac

running the installer again

mikeymicrophone commented 13 years ago

I have deleted the gem and the binary and restarted, but my web access is still blocked. Any pointers would be appreciated.

mikeymicrophone commented 13 years ago

Does sheepsafe assume that you have password-less access to your ssh network?

nicksieger commented 13 years ago

Can you try with 0.2.6? There was a bug that made 0.2.5 unusable unless you had ssh_port set in your ~/.sheepsafe.yml.

jridgewell commented 13 years ago

It probably that you're still using the "untrusted" network in your network pane, which requires a ssh tunnel (which you don't have since you uninstalled). Try changing it to your "trusted" location ("Automatic" be default) and see if that resolves the problem.

PS. Uninstalling it just means sheepsafe won't run on startup, to completely remove sheepsafe you must run sudo gem uninstall sheepsafe

mikeymicrophone commented 13 years ago

Nick and J, thanks for your help but I'm not planning to test this further at this time. If I find a consultant who can help me get a better grip on all my installations then I will reconsider.