NaCl plugin exited with status code 255.

[noel...@gmail.com]

The environment:

- ASUS Chromebox CN60

- Chrome OS 59.0.3071.134

- Chrome Browser

- AWS EC2 instance using default user ec2-user

- am able to paste public IP address into browser and index.html is displayed

I get the following using the AWS user @public IP

and 'SSH Arguments":

-v -i MyEC2WebServerKeyPair.pem

Welcome to Secure Shell version 0.8.36.8.
Answers to Frequently Asked Questions: https://goo.gl/muppJj (ctrl+click on links to open)

[Pro Tip] Use 'Open as Window' to prevent Control-W from closing your terminal!
[Pro Tip] See https://goo.gl/muppJj for more information.

ChangeLog/release notes: https://goo.gl/YnmXOs
Connecting to ec2-...@54.174.210.194...
Loading NaCl plugin... done.
OpenSSH_7.5p1, OpenSSL 1.0.2k  26 Jan 2017
debug1: Connecting to 54.174.210.194 [54.174.210.194] port 22.
debug1: Connection established.
debug1: getpeername failed: No such file or directory
debug1: key_load_public: Bad file number
debug1: identity file MyEC2WebServerKeyPair.pem type -1
debug1: key_load_public: Bad file number
debug1: identity file MyEC2WebServerKeyPair.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.5
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1
debug1: match: OpenSSH_6.6.1 pat OpenSSH_6.6.1* compat 0x04000000
debug1: Authenticating to 54.174.210.194:22 as 'ec2-user'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve255...@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20...@openssh.com MAC: <implicit> compression: zl...@openssh.com
debug1: kex: client->server cipher: chacha20...@openssh.com MAC: <implicit> compression: zl...@openssh.com
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:0U3mJSXOJ9g4keHEIWpsTQ18bwQ55uPGkrCja7xsoDU
debug1: Host '54.174.210.194' is known and matches the ECDSA host key.
debug1: Found key in /.ssh/known_hosts:2
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: MyEC2WebServerKeyPair.pem
Load key "MyEC2WebServerKeyPair.pem": Bad file number
debug1: No more authentication methods to try.
Permission denied (publickey).

[Mike Frysinger]

i suspect MyEC2WebServerKeyPair.pem is not the path you want.  did you actually import that file ?  if so, it's under /.ssh/.

-mike

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/10c52d6e-dbcf-4813-b0cc-a7a862b37a73%40chromium.org.

[noel...@gmail.com]

Hope this is the correct forum.  I tried to connect without the key file and got the same message.

I am trying to connect to an AWS instance on my Chromebox.  I am able to connect to the same instance using Putty on W10.  

The SS screen launches and displays the error and is then in a "frozen" state.  

[Mike Frysinger]

if you mean you keep hitting "Permission denied (publickey)." and then the session dies, then that's not Secure Shell's problem, and it's WAI. you need to enter proper credentials to connect to the server in question. based on the error message, you need to import the right set of keys via the Identity box instead of manually entering -i options to the ssh connection settings.

-mike

--

You received this message because you are subscribed to the Google Groups "chromium-hterm" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/4803da50-281d-4203-b871-b128fc8a43d9%40chromium.org.

[Noel Dennis]

So I found an Ubuntu USB I previously made, booted my W10 PC using USB and generated a Public key file.  But, it appears not to care about the file anyway.

But still have a more fundamental problem.  When launching Secure Shell on my CHROMEBOX, I enter ONLY the user and IP address and select Open?  I get the permission denied message without having specified a file name.   I then am offered R, C, X.  No option to do ls, pwd, OR ANY command.

So I don't know what folder or file name it is looking at.  So, no filename, with filename it doesn't matter. 

Any suggestions for another way of doing SSH on Chromebox in Chrome OS?

Welcome to Secure Shell version 0.8.36.8.
Answers to Frequently Asked Questions: https://goo.gl/muppJj (ctrl+click on links to open)

[Pro Tip] Use 'Open as Window' to prevent Control-W from closing your terminal!
[Pro Tip] See https://goo.gl/muppJj for more information.

ChangeLog/release notes: https://goo.gl/YnmXOs
Connecting to ec2-...@54.174.210.194.

..
Loading NaCl plugin... done.
Permission denied (publickey).
NaCl plugin exited with status code 255.
(R)econnect, (C)hoose another connection, or E(x)it?
 failed! :(

[Mike Frysinger]

> Permission denied (publickey).

you need to provide valid keys to auth with the remote server

-mike

--

You received this message because you are subscribed to the Google Groups "chromium-hterm" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/f0009f7f-33b9-42b1-a850-8b76667b9fdd%40chromium.org.

[robloxro...@gmail.com]

[kgstar...@gmail.com]

how to you verify creds?