<div dir="ltr"><br><br><div class="gmail_quote">On Mon, Sep 22, 2008 at 4:04 PM, Paul Hummer <span dir="ltr"><<a href="mailto:paul@eventuallyanyway.com">paul@eventuallyanyway.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d"> > Bonus question: if you forward local port 80 to the ssh server, would<br> > that essentially encrypt all local web traffic without setting up a<br> > socks proxy?<br> ><br> <br> </div><br>Yes, in fact, that's how many people use wireless securely without a vpn.</blockquote><div><br>Okay, this didn't work. When I do<br><br>ssh -D 8080 -p 5151 <a href="mailto:user@host.com">user@host.com</a><br> <br>It connects just fine and pulls in the private key from .ssh, asks for the key's password and then authenticates. This works. However, when I do<br><br>sudo ssh -D 80 -p 5151 <a href="mailto:user@host.com">user@host.com</a><br> <br>It asks for the sudo password (have to use sudo for privileged ports) then tries to make the connection but returns an error about permission denied. Is there any reason why using sudo would prevent it from using the proper key? It doesn't even prompt for the key's password. I also tried using<br> <br>sudo ssh -L 50 ...<br><br>But it didn't like that. It said something about improver or invalid local port. Anyway, any ideas?<br><br>@Scott - thanks for the info. I get it and will give it a try.<br><br>Thanks.<br> </div></div><br>-- <br>Jim (Ubuntu geek extraordinaire)<br>----<br>Please avoid sending me Word or PowerPoint attachments.<br>See <a href="http://www.gnu.org/philosophy/no-word-attachments.html">http://www.gnu.org/philosophy/no-word-attachments.html</a><br> </div>