Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
access_the_batocera_via_ssh [2023/04/18 05:18] – no pleases atariaccess_the_batocera_via_ssh [2025/07/26 14:30] (current) – Note for SSH on non-Linux partitions lbrpdx
Line 48: Line 48:
  
 ==== Password-less authentication ==== ==== Password-less authentication ====
 +
 +=== From a remote machine to Batocera ===
  
 Batocera can remember the SSH client's key such that it no longer requires a password to type in. Batocera can remember the SSH client's key such that it no longer requires a password to type in.
 +
 +<WRAP center round important>
 +This section assumes that your Batocera user data partition is 
 +formatted Linux-native (ext4 by default, or btrfs). The //chmod// commands below won’t be applied correctly on FAT32 or NTFS partitions, and as a result passwordless SSH will fail.</WRAP>
  
   - On Batocera, run the following in terminal: <code bash>   - On Batocera, run the following in terminal: <code bash>
 +chown root:root / /userdata/ /userdata/system/
 +chmod 755 / /userdata/ /userdata/system/
 mkdir -p ~/.ssh mkdir -p ~/.ssh
 touch ~/.ssh/authorized_keys touch ~/.ssh/authorized_keys
Line 57: Line 65:
 chmod 600 ~/.ssh/authorized_keys chmod 600 ~/.ssh/authorized_keys
 </code> </code>
-  - On the client computer (the one which logs into Batocera via SSH), generate its public keys (if not already done so) and add the public Batocera SSH keys to its SSH configuration.+  - On the client computer (the one which logs into Batocera via SSH), generate its SSH keypairs (if not already done so) and add the public Batocera SSH key to the Batocera SSH configuration as follows:
     * For most **Linux**-based distributions, run the following: <code bash>     * For most **Linux**-based distributions, run the following: <code bash>
 ssh-keygen ssh-keygen
Line 66: Line 74:
  
 That's it. You should be able now to SSH into your Batocera system from your SSH client without entering any password. That's it. You should be able now to SSH into your Batocera system from your SSH client without entering any password.
 +
 +<WRAP center round important>
 +Advanced users may be tempted to use ''ssh-copy-id'' to set up the ''authorized_keys'' file.  This will not work, due to limitations in the [[https://en.wikipedia.org/wiki/Dropbear_(software)|Dropbear]] setup as implemented in Batocera.
 +</WRAP>
 +
 +=== From Batocera to a remote machine ===
 +
 +It is also possible to set up passwordless authentication the other way around: From Batocera to am remote machine. Since Batocera does use the //Dropbear// SSH service, the ''ssh-keygen'' command will not work to create a local SSH keypair. Instead, the following command will generate the according SSH keypairs: \\ ''dropbearkey -t rsa -f ~/.ssh/id_dropbear'' \\ Once done, the public SSH key will be shown on the command line window. In case you want to show the public SSH key later, do so by executing: \\ ''dropbearkey -y -f /userdata/system/.ssh/id_dropbear | grep '^ssh-rsa' > /userdata/system/.ssh/id_dropbear.pub''
 +
 +You can now copy the according public SSH key to your remote machine as already shown above, but the other way around of course.
  
 ===== Basic SSH commands ===== ===== Basic SSH commands =====
Line 160: Line 178:
   * ''htop'' : basic task manager.   * ''htop'' : basic task manager.
   * ''pidof'' : gives a list of processes identifyiers (PID) for a running process name [**P**rocess **ID**entification **OF**], for example ''pidof retroarch'' returns a number when a retroarch-based emulator is running.   * ''pidof'' : gives a list of processes identifyiers (PID) for a running process name [**P**rocess **ID**entification **OF**], for example ''pidof retroarch'' returns a number when a retroarch-based emulator is running.
-  * ''kill [PID]'' : kills a process with a given PID, for example if ''pidof retroarch'' returned 640, then running ''kill 640'' would terminate the ''retroarch'' process.+  * ''kill [PID]'' : kills a process with a given PID, for example if ''pidof retroarch'' returned 640, then running ''kill 640'' would terminate the ''retroarch'' process. This command can also to be used to check if a process is alive with the ''-0'' flag. eg.''kill -0 640'' (FIXME what does this output?) 
 +  * ''pgrep'' : Works like the Unix ''grep'' command but instead of text and strings it works with processes. For example, ''pgrep emul*'' will obtain all PIDs of processes containing the string **emul**, such as ''emulationstation'' and its wrapper script. 
 +  * ''which'' : it is used to find the location of the executable file associated with the command. eg. ''which python'' shows the path of python binary.
  
 --> How to install btop on Batocera v33 and earlier# --> How to install btop on Batocera v33 and earlier#
Line 227: Line 247:
   --version  Shows current version of BATOCERA running   --version  Shows current version of BATOCERA running
   --update   Shows possible update for your install   --update   Shows possible update for your install
-      default: stable, you can type --update beta+      default: stable, you can type --update butterfly
  
   --overlay  will try to backup your overlay file   --overlay  will try to backup your overlay file
Line 293: Line 313:
 Overclocking your hardware could cause irreversible damage and/or erratic behavior, this is at your own risk. If any issues occur after setting this, this should be the first thing to be returned to default. Overclocking your hardware could cause irreversible damage and/or erratic behavior, this is at your own risk. If any issues occur after setting this, this should be the first thing to be returned to default.
 </WRAP> </WRAP>
-  * ''batocera sync list'' : list storage devices that are capable of being synced to +  * ''batocera-sync list'' : list storage devices that are capable of being synced to 
-  * ''batocera sync <storage UID>'' : uses rsync to sync the current userdata to the ''batocera/'' folder on the selected storage device (NTFS not supported, FAT systems don't support syncing Bluetooth settings)+  * ''batocera-sync <storage UID>'' : uses rsync to sync the current userdata to the ''batocera/'' folder on the selected storage device (NTFS not supported, FAT systems don't support syncing Bluetooth settings)
   * ''batocera-timezone get'' : show the current configured timezone   * ''batocera-timezone get'' : show the current configured timezone
   * ''batocera-timezone detect'' : attempt to automatically guess your timezone   * ''batocera-timezone detect'' : attempt to automatically guess your timezone
  • access_the_batocera_via_ssh.1681795106.txt.gz
  • Last modified: 3 years ago
  • by atari