I try the following in my home directory on the institution server:

the last line in particular logs me in (it ssh's itself) due to public key authentication setup (oops)

This is the first time I've ever tried to make or use a proxy.

My instructor for a course I'm taking gave me the directions to use this. It appears I'm the only one having trouble with this and he doesn't know what I'm doing wrong.

FYI for browser use what browser on linux works the best for use a proxy.

Hi,

so you've created the proxy. Next step is to use it. Eg

If this is not the information you are looking for please state what problem you are having.

Cheers,

Evo2.

It didn't work. I used as extra flag but I don't remember what. I think it may be cause I only have access to my account on the servers, so what would it be then?

When I tried the localhost command it didn't give me any errors on the server side. But it requires I keep the ssh session going from what I saw.

Is public key authentication necessary to connect to a proxy a password protected account on another account?

Hi,
Make sure that all running instances of chromium have been stopped before launching it with the proxy option.
You only need access to your account.

Hi,
Not sure what "localhost command" you are refering to.

You don't normally need need any authentication to connect to a proxy. However you will need some sort of authentication to create the proxy.

Just to be clear this is what you should do. Open two terminals and then, in one of them do:
This will create the proxy and give you a shell on the remote server. After this leave that terminal alone with the shell connection open (other options can be passed to ssh to make it quietly go into the background be we can do that once we know we can get it to work).

In another terminal lauch your webbrowser after first making sure it is not running already:
If it "does not work" please be explicit about what happens.

Evo2.

1 members found this post helpful.

When I did the proxy command it actually logged me into the server.

I did this on my mac at home:
which sent me to the server and logged me in like a normal ssh session.

I tried using it on mac:

I got this in the error page in google chrome:

-------

Your examples are really confusing. When I tried making a proxy at localhost, I did that on the server. The server doesn't have a browser installed. I need a proxy on the server to access local network webpages that I can't normally access offsite.

EDIT: I tried
On the server side and that also didn't work

Hi,
Which is exactly what I said would happen.

Good.
Um, hang on, is this "mac" the same machine on which you created the proxy with the ssh command? Also, that is not the correct argument. It shold be

You seem not to be following them.
Why did you do that on the server? Just open the two shells on your client machine and run the two commands as I instructed in my last post. Change "me@server.somewhere" to whatever it needs to be, change 6667 to whatever high port number you like, do NOT change "localhost".

Evo2.




Evo2.

1 members found this post helpful.

@Evo: From what I've gather after reading his comments 2 times... The mac is the client machine he want's connected to his network machine.. :P He just seems to be a bit confused of what actually happens when he runs those commands

@jddancks: What actually happens is that the SOCKS proxy is your personal mac machine (don't worry, the connection still gets routed via ssh on your workplace machine -- that's what the -D option does) and that's why you need to enter --proxy-server=socks://localhost:8888" (like Evo2 already told you to)...
It only seems weird because you're confusing the actual ssh connection with the socks proxy connection... You should think of them as two different things..

Basically, when running:
you are instructing your local (so, only localhost) machine to listen to incoming SOCKS4 or SOCKS5 connections on port 8888 that gets forwarded to me@server.edu:22
You will get connected and you need to keep this connection active (exiting will close the connection)

You then need to instruct your browser to connect to this localhost connection:

There is no need to run any kind of special command on the server side..

1 members found this post helpful.

I couldn't get it to work with chrome but I got it to work with firefox (and the debian version of firefox).

Thanks to both evo2 and smokey_justme