Spacebridge Tunnel requesting pubkey,password


#1

Hi,

I am using a Hologram SIM card in a MOXA oncell G3150A Gateway. I set up this gateway to allow inbound communications. After running the following command:

ssh -p 999 -L 5000:link{mylink}:22 -N -i spacebridge.key htunnel@tunnel.hologram.io

I open a different terminal and I run

ssh pi@127.0.0.1 -p 5000 -v

I get the following:

OpenSSH_6.9p1, LibreSSL 2.1.8
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: /etc/ssh/ssh_config line 56: Applying options for *
debug1: Connecting to 127.0.0.1 [127.0.0.1] port 5000.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /Users/manuelgodoy/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/manuelgodoy/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/manuelgodoy/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/manuelgodoy/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/manuelgodoy/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/manuelgodoy/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/manuelgodoy/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/manuelgodoy/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.9
debug1: Remote protocol version 2.0, remote software version dropbear_0.53
debug1: no match: dropbear_0.53
debug1: Authenticating to 127.0.0.1:5000 as 'pi’
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-sha1 none
debug1: kex: client->server aes128-ctr hmac-sha1 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Server host key: ssh-rsa SHA256:1ow0IB4rgGG5+qgNQV+CRXpc1JtklJvETYWaL/7ImrA
debug1: Host ‘[127.0.0.1]:5000’ is known and matches the RSA host key.
debug1: Found key in /Users/manuelgodoy/.ssh/known_hosts:26
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/manuelgodoy/.ssh/id_rsa
debug1: Trying private key: /Users/manuelgodoy/.ssh/id_dsa
debug1: Trying private key: /Users/manuelgodoy/.ssh/id_ecdsa
debug1: Trying private key: /Users/manuelgodoy/.ssh/id_ed25519
debug1: Next authentication method: password
pi@127.0.0.1’s password:

When I type my pi’s password it gives me this error:

debug1: Authentications that can continue: publickey,password
Permission denied, please try again.

So it looks like I need to give it a publickey. I tried copying and pasting the spacebridge.key.pub but no luck. Same problem would happen if I run the Spacebridge Tunnel Client software. Could you help me solve this?


#2

You should be able to login using whatever method you normally use to login to your pi. If you haven’t changed your password yet, the default is “raspberry”


#3

Hi Reuben,

Thanks for your reply. Typing my password is not working. As you can see it looks like it is expecting a publickey along with the password:

debug1: Authentications that can continue: publickey,password
Permission denied, please try again.


#4

Yeah that’s normal for SSH. It’s usually configured to try a public key but that doesn’t mean that the key actually exists. Are you able to ssh into your pi from the local network over ethernet or wifi? What do you use to do that?


#5

Here’s an example from my own pi:

debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/pi/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/pi/.ssh/id_dsa
debug1: Trying private key: /home/pi/.ssh/id_ecdsa
debug1: Trying private key: /home/pi/.ssh/id_ed25519
debug1: Next authentication method: password
pi@reuben-pi's password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
pi@reuben-pi's password:
debug1: Authentication succeeded (password).
Authenticated to reuben-pi ([192.168.11.110]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug1: Sending environment.
debug1: Sending env LANG = en_GB.UTF-8
Linux reuben-pi 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

When I type my password wrong I get the same message as you about publickey being allowed, but then when I type it correct I am logged in.


#6

Yes I am able to do it locally. I have done it hundreds of times. But hmm that’s interesting, why would it not take my password this time? I also tried raspberry just to see.

I use ssh pi@{pi_ipaddress}


#7

Hmm very strange. Usually if there’s a spacebridge issue then you won’t even get the password prompt. Not sure what would be going on that it wouldn’t connect at all.

Does the server host key match in that output between the spacebridge connection and the local one?


#8

This topic was automatically closed after 30 days. New replies are no longer allowed.