Difference between revisions of "System Log In"
Kyoungmeyer (talk | contribs) (→Serial) |
|||
| (12 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{todo| | + | {{todo|SEOKWREV (11.25.13-13:30->KY+);(11.25.13-18:50->MD+);(11.26.13-21:35->MD+);(12.20.13-11:16->MW+);(03.04.14-15:30->BS-);(03.17.14-15:00->BS+)|Klint Youngmeyer|project=oe 4,oe 5,ky,SEOKWREV,md,mw,bs}} |
| − | '''This page needs to be reworked. The SSH section should show the users how to make good use of SSH. There may be other content for this already, and if so, it can probably be merged into here. Basically, it should also show:''' | + | <!--'''This page needs to be reworked. The SSH section should show the users how to make good use of SSH. There may be other content for this already, and if so, it can probably be merged into here. Basically, it should also show:''' |
* '''How to copy files over ssh (scp)''' | * '''How to copy files over ssh (scp)''' | ||
* '''How to remotely execute commands on a system via ssh: ssh user@host "my_command -args file"''' | * '''How to remotely execute commands on a system via ssh: ssh user@host "my_command -args file"''' | ||
* '''How to use sshpass to automate tasks over ssh(?) We'll have to think about this one.''' | * '''How to use sshpass to automate tasks over ssh(?) We'll have to think about this one.''' | ||
'''The login process, otherwise, is pretty straightforward. We probably don't really need a page describing how to enter a username and password, but if we have to have one, we should probably note that it's normal to not see any output while typing in a password at a Linux login prompt. That seems to be the thing that throws the most people.''' | '''The login process, otherwise, is pretty straightforward. We probably don't really need a page describing how to enter a username and password, but if we have to have one, we should probably note that it's normal to not see any output while typing in a password at a Linux login prompt. That seems to be the thing that throws the most people.''' | ||
| + | --> | ||
| + | {{#seo: | ||
| + | |title=System Log In | ||
| + | |titlemode=append | ||
| + | |keywords=Serial,SSH,Logging In,Transferring Files,Remote Execution | ||
| + | |description=System log in to EMAC OE Linux. | ||
| + | }} | ||
The next step after establishing a physical connection to the board is logging in. EMAC OE Linux allows login from getty, SSH (Secure Shell) and Telnet. A getty uses the serial connection or console while SSH and Telnet utilize a network connection. | The next step after establishing a physical connection to the board is logging in. EMAC OE Linux allows login from getty, SSH (Secure Shell) and Telnet. A getty uses the serial connection or console while SSH and Telnet utilize a network connection. | ||
{{mbox | type = warning | text = '''Warning:''' Using Telnet will expose all data "in the clear" to everyone in the network you are using. This includes your password and any data you transmit between the system and your computer. EMAC recommends using SSH for all network connections. Telnet should never be used if the system is connected directly to the Internet outside of any firewall or NAT router.}} | {{mbox | type = warning | text = '''Warning:''' Using Telnet will expose all data "in the clear" to everyone in the network you are using. This includes your password and any data you transmit between the system and your computer. EMAC recommends using SSH for all network connections. Telnet should never be used if the system is connected directly to the Internet outside of any firewall or NAT router.}} | ||
| + | |||
__TOC__ | __TOC__ | ||
| Line 21: | Line 29: | ||
| user || emac_inc | | user || emac_inc | ||
|} | |} | ||
| + | |||
| + | |||
| + | {{mbox | type= | text='''Note:''' It is normal to not see any output while typing in a password at a Linux login prompt. }} | ||
== Serial == | == Serial == | ||
| Line 35: | Line 46: | ||
For an SSH connection, you will need an SSH client application. An SSH client is included by default on most desktop Linux distributions and other operating systems, but is not included on Windows. EMAC recommends using [[PuTTY]] for an SSH client on Windows workstations. | For an SSH connection, you will need an SSH client application. An SSH client is included by default on most desktop Linux distributions and other operating systems, but is not included on Windows. EMAC recommends using [[PuTTY]] for an SSH client on Windows workstations. | ||
| + | SSH uses key pairs to authenticate identity and perform encryption. If the remote host's key is not recognized in the SSH known hosts list or if it changes, the SSH client will print a warning and require confirmation to continue. If this is the first connection attempt to this system, you will most likely see a message about the host key not being recognized similar to the following: | ||
| + | |||
| + | The authenticity of host '[10.0.2.41] ([10.0.2.41])' can't be established. | ||
| + | RSA key fingerprint is 5f:cc:f3:25:9d:37:89:bd:94:fc:74:a0:eb:55:a9:6a. | ||
| + | Are you sure you want to continue connecting (yes/no)? yes | ||
| + | Warning: Permanently added '[10.0.2.41]' (RSA) to the list of known hosts. | ||
| + | |||
| + | Any SSH protocol based command can generate this message. | ||
| + | |||
| + | ===Logging In=== | ||
The command line SSH client syntax to log in to a system is <code>ssh user@host</code>. For example, to log in as root to a system with the IP address 10.0.2.41, you would use the following command: | The command line SSH client syntax to log in to a system is <code>ssh user@host</code>. For example, to log in as root to a system with the IP address 10.0.2.41, you would use the following command: | ||
| Line 41: | Line 62: | ||
root@emac-oe:~# | root@emac-oe:~# | ||
| − | + | To connect to the system using [[PuTTY]] under Windows, follow the steps outlined in the [[PuTTY]] documentation. [[PuTTY]] will also warn if the host key is not recognized in a way similar to the SSH command line client under Linux as described above. | |
| + | ===Transferring Files=== | ||
| + | The command line syntax for transferring a file using the SSH protocol is <code>scp file user@host:/directory</code>. SCP or Secure Copy is a way of securely transferring files between a local and remote host. For example, to send the file ''example.text'' to the <code>/home</code> directory of a system with the IP address 10.0.2.41, enter the following command: | ||
| + | developer@ldc:~# scp example.text root@10.0.2.41:/home | ||
| + | |||
| + | Be aware that this copy operation will fail if the filesystem on the remote machine is mounted read-only, which is the default on most EMAC systems. | ||
| − | + | To send files to the system using [[PuTTY]] under Windows, follow the steps outlined in the [[PuTTY]] documentation. | |
| − | |||
| − | |||
| − | |||
| − | + | ===Remote Execution=== | |
| + | SSH can also be used to execute programs on remote systems without logging in. The syntax for SSH remote execution is <code>ssh user@host "my_command -args file"</code>. For example, to run the program ''hello_world'' with the ''-hi'' flags on a system with the IP address of 10.0.2.41, enter the following command: | ||
| + | developer@ldc:~# ssh root@10.0.2.41 "hello_world -hi" | ||
| + | <!--===Command Automation===--> | ||
== Next Steps == | == Next Steps == | ||
After you have logged into the system, user accounts may be [[User_Account_Configuration | configured.]] | After you have logged into the system, user accounts may be [[User_Account_Configuration | configured.]] | ||
| − | + | <!-- | |
[[Category:Linux]] | [[Category:Linux]] | ||
[[Category:OpenEmbedded]] | [[Category:OpenEmbedded]] | ||
| + | --> | ||
Latest revision as of 14:46, 19 March 2014
The next step after establishing a physical connection to the board is logging in. EMAC OE Linux allows login from getty, SSH (Secure Shell) and Telnet. A getty uses the serial connection or console while SSH and Telnet utilize a network connection.
 | Warning: Using Telnet will expose all data "in the clear" to everyone in the network you are using. This includes your password and any data you transmit between the system and your computer. EMAC recommends using SSH for all network connections. Telnet should never be used if the system is connected directly to the Internet outside of any firewall or NAT router. |
In addition to the root account, a user account with limited system permissions is also enabled by default. The default login and password are shown in Table 4 below.
| Table 4: Default Login Credentials | |
|---|---|
| Username | Password |
| root | emac_inc |
| user | emac_inc |
 | Note: It is normal to not see any output while typing in a password at a Linux login prompt. |
Serial
If you have established a serial connection with the board, the login prompt should be visible in the terminal application on the workstation similar to what is shown below.
EMAC OpenEmbedded Linux 4.0 (stable-2009) Some code contained within Copyright 2008-2011 EMAC, Inc. emac 2009-stable emac-oe ttyS0 emac-oe login:
SSH
For an SSH connection, you will need an SSH client application. An SSH client is included by default on most desktop Linux distributions and other operating systems, but is not included on Windows. EMAC recommends using PuTTY for an SSH client on Windows workstations.
SSH uses key pairs to authenticate identity and perform encryption. If the remote host's key is not recognized in the SSH known hosts list or if it changes, the SSH client will print a warning and require confirmation to continue. If this is the first connection attempt to this system, you will most likely see a message about the host key not being recognized similar to the following:
The authenticity of host '[10.0.2.41] ([10.0.2.41])' can't be established. RSA key fingerprint is 5f:cc:f3:25:9d:37:89:bd:94:fc:74:a0:eb:55:a9:6a. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '[10.0.2.41]' (RSA) to the list of known hosts.
Any SSH protocol based command can generate this message.
Logging In
The command line SSH client syntax to log in to a system is ssh user@host. For example, to log in as root to a system with the IP address 10.0.2.41, you would use the following command:
developer@ldc:~$ ssh root@10.0.2.41 root@10.0.2.41's password: root@emac-oe:~#
To connect to the system using PuTTY under Windows, follow the steps outlined in the PuTTY documentation. PuTTY will also warn if the host key is not recognized in a way similar to the SSH command line client under Linux as described above.
Transferring Files
The command line syntax for transferring a file using the SSH protocol is scp file user@host:/directory. SCP or Secure Copy is a way of securely transferring files between a local and remote host. For example, to send the file example.text to the /home directory of a system with the IP address 10.0.2.41, enter the following command:
developer@ldc:~# scp example.text root@10.0.2.41:/home
Be aware that this copy operation will fail if the filesystem on the remote machine is mounted read-only, which is the default on most EMAC systems.
To send files to the system using PuTTY under Windows, follow the steps outlined in the PuTTY documentation.
Remote Execution
SSH can also be used to execute programs on remote systems without logging in. The syntax for SSH remote execution is ssh user@host "my_command -args file". For example, to run the program hello_world with the -hi flags on a system with the IP address of 10.0.2.41, enter the following command:
developer@ldc:~# ssh root@10.0.2.41 "hello_world -hi"
Next Steps
After you have logged into the system, user accounts may be configured.
