The article was originally published at the Third Frontier Institute in SZHSHP
Reprint Please specify
Gracefully messing with linux-6-chrome-side SSH plugins
Recently registered an AWS, free one year, a year can be a variety of fun ~
Connecting to a cloud host from your own computer typically requires something like ssh. Since there is such a chance, simply systematically study under SSH:
Secure Shell (SSH) is a cryptographic network protocol for operating network services securely over an unsecured network. The best known example application are for remote login to computer systems by users.
SSH provides a secure channel over the unsecured network in a client-server architecture, connecting an SSH client Applicat Ion with an SSH server. Common applications include remote command-line login and remote command execution, but no network service can be secured With SSH. The protocol specification distinguishes between, major versions, referred to as SSH-1 and SSH-2.
The most visible application of the protocol are for access to shell accounts on unix-like operating systems, but it sees s OME Limited use on Windows as well. In, Microsoft announced this they would include native support for SSH into a future release.
SSH is an encrypted network protocol that is used to establish a secure link to a network device under a non-secure network. SSH is widely used for remote computer command execution, such as VPS, cloud host and other devices require SSH operation.
SSH connection
There are several ways to establish an SSH connection:
Linux/Unix
Directly created under the system Terminal
Linux/Unix/Windows
Using three-party software to create the system
浏览器
JRE is required, and many browsers do not already support
Chrome
Using the plug-in to create
The main talk about the plugin in chrome solution
Secure Shell: Using SSH in Chrome
First Download plugins: Https://chrome.google.com/webstore/detail/secure-shell/pnhechapfaindjhompbnflcldabbghjo?hl=en-US
Basically, I know how to use it.
EC2 authentication problem in Secure Shell: NaCl plugin exited with status code 255
EC2 generally uses .pem
the private key for authentication, but often encounters a problem in using Secure Shell:
with status code 255.(R)econnect, (C)hoose another connection, or E(x)it?
Look at a lot of discussion that the reason is: SSH needs a public key, but we only have a private key
Many solution say that there is a need to generate a Publick key, but in fact there is no requirement for public key, we just need to .pem
copy and then change the extension .pub
to
For example, your private key is 123.pem
copied and then named, and 123.pen.pub
then the import is selected.
This looks like a recipe, but it does.
Series Articles
Gracefully messing with Linux
Reference documents
- Https://en.wikipedia.org/wiki/Secure_Shell
Gracefully messing with linux-6-chrome-side SSH plugins