Re: Not a RSA1 key file ...key_read: no key found

From: Darren Tucker (dtucker@dodgy.net.au)
Date: 04/04/03 

From: dtucker@dodgy.net.au (Darren Tucker)
Date: Thu, 03 Apr 2003 23:26:01 GMT

In article <fc42b9fa.0304031120.63d6234b@posting.google.com>,
Werner Stolz <wlstolz@earthlink.net> wrote:
>We have what I am told is a generic proxy on the server named
>inetproxy, which redirects all traffic sent to port 4001 to the
>appropriate port and the appropriate external server. This is why I
>am using port 4001.
>
>root@betty:/home/wstolz# /usr/local/bin/ssh -vvv -p 4001 -l testuser
>inetproxy
[snip]
>ssh_exchange_identification: read: Connection reset by peer

Your "generic proxy" is probably broken. Try "telnet inetproxy 4001"
and see if you get a SSH banner.

>If I use puTTY, I can connect successfully, but I do not use port
>4001. Instead, I specify the correct host name and port in the
>Session window, but in the Connection:Proxy window, I specify
>inetproxy on port 80 and a proxy type of HTTP.
>
>So, does anyone have a clue why puTTY works without using the generic
>proxy and openSSH does not work when it does use the proxy?

They're using different proxy types on the "inetproxy" host and one
doesn't seem to work.

>Also, I have done some research from the man pages, www.openssh.org
>and the Book "SSH, The Secure Shell: The Definitive Guide", but I
>cannot figure out how to get openSSH to ignore the 4001 proxy and
>duplicate whatever puTTY is doing.

PuTTY is using a HTTP proxy rather than your generic proxy. To get
OpenSSH do do that you need to download and install "connect"
(http://www.taiyo.co.jp/~gotoh/ssh/connect.html) and use it as ssh's
ProxyCommand, eg add the following to $HOME/.ssh/config or ssh_config:

ProxyCommand /usr/local/bin/connect -H inetproxy %h %p 

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

Relevant Pages

  • Re: Transparent proxy failing
    ... machine A as the gateway on the network, and A takes requests to port ... The squid machine, A, doesn't handle HTTPS blocking. ... up a website, it goes right to the website, no filtering. ... IE on the client to specifically use the proxy setting of B's ip ...
    (Ubuntu)
  • Re: SSH Tunneling, view web site as though I am in the USA
    ... $ ssh -D 1080 me@us_server ... And then set your local web browser to proxy using socks 4 to server ... HTTP Proxy: localhost Port: 1080 ... Not http proxy, SOCKS 4 proxy. ...
    (comp.security.ssh)
  • Re: Fehlercode 502
    ... Wenn ich den Proxy umgehe, ... In der ISA Server Hilfe habe ich leider keine Infos gefunden, ... Gruß Detlef ... >> Port 8443). ...
    (microsoft.public.de.german.isaserver)
  • Re: Webproxy Konfiguration auf einem ISA 2006 Standard
    ... dann ist der Client noch SecureNAT Client?! ... Dann geht es auch ohne Proxy ... Hierbei habe ich die einzelne IP als Quelle angegeben und den ISA ... Freigegeben sind Port 80/443/8080. ...
    (microsoft.public.de.german.isaserver)
  • Re: bypassing employers proxy to surf anonymously
    ... When using SSH through the local proxy, it might be an idea to run the ... port 443, so it's harder to distinguish from an https server. ... Also, in case you're not aware, a proxy server on the other side ... Another method of tunneling would be through DNS. ...
    (Pen-Test)
Loading