Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.security.ssh > #113

Re: Not a RSA1 key file when connecting to port 443

From Nico Kadel-Garcia <nkadel@gmail.com>
Newsgroups comp.security.ssh
Subject Re: Not a RSA1 key file when connecting to port 443
Date 2011-06-11 19:45 -0700
Organization http://groups.google.com
Message-ID <ac25310a-e19f-46fd-aa0d-8649e5ca324d@32g2000vbe.googlegroups.com> (permalink)
References <827ac64c-4888-4f8f-8f95-434a6635796d@d19g2000prh.googlegroups.com>

Show all headers | View raw


On Jun 2, 12:52 pm, Clodoaldo Neto <clodoaldo.pi...@gmail.com> wrote:
> When I ssh from a Fedora 15 client to a Centos 5 server at port 22 it
> works perfectly. But when I try to connect to port 443 I get this:
>
> $ ssh -vvv ck -p 443
> OpenSSH_5.6p1, OpenSSL 1.0.0d-fips 8 Feb 2011
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: Applying options for ck
> debug1: Applying options for *
> debug2: ssh_connect: needpriv 0
> debug1: Connecting to ck [1.2.3.4] port 443.
> debug1: Connection established.
> debug3: Not a RSA1 key file /home/cpn/.ssh/id_rsa.
> debug2: key_type_from_name: unknown key type '-----BEGIN'
> debug3: key_read: missing keytype
> debug3: key_read: missing whitespace
> ...
> debug3: key_read: missing whitespace
> debug2: key_type_from_name: unknown key type '-----END'
> debug3: key_read: missing keytype
> debug1: identity file /home/cpn/.ssh/id_rsa type 1
> debug1: identity file /home/cpn/.ssh/id_rsa-cert type -1
> debug3: Not a RSA1 key file /home/cpn/.ssh/id_dsa.
> debug2: key_type_from_name: unknown key type '-----BEGIN'
> debug3: key_read: missing keytype
> debug3: key_read: missing whitespace
> ...
> debug3: key_read: missing whitespace
> debug2: key_type_from_name: unknown key type '-----END'
> debug3: key_read: missing keytype
> debug1: identity file /home/cpn/.ssh/id_dsa type 2
> debug1: identity file /home/cpn/.ssh/id_dsa-cert type -1
>
> Any hints?
>
> Regards, Clodoaldo

Please look at the "/etc/services" file on your machine. It will show
that 22 is the SSH port, 80 is the HTTP port, and 443 is the HTTPS
port. A stack of people use 443 for their SSH servers, because few
corporate firewalls block it, while many do block port 22 as a matter
of policy. But unless your target server is running SSH on that port,
don't be surprised.

By the way, you can use "nc" on most systems more efficiently to see
what a port says when you connect, rather than burdening the test with
ssh clients.

Back to comp.security.ssh | Previous | NextPrevious in thread | Find similar


Thread

Not a RSA1 key file when connecting to port 443 Clodoaldo Neto <clodoaldo.pinto@gmail.com> - 2011-06-02 09:52 -0700
  Re: Not a RSA1 key file when connecting to port 443 jeff@sdsc.edu (Jeff Makey) - 2011-06-02 19:59 +0000
    Re: Not a RSA1 key file when connecting to port 443 Clodoaldo Neto <clodoaldo.pinto@gmail.com> - 2011-06-03 05:31 -0700
  Re: Not a RSA1 key file when connecting to port 443 Nico Kadel-Garcia <nkadel@gmail.com> - 2011-06-11 19:45 -0700

csiph-web