Difference between revisions of "PinePhone Security"

From PINE64
Jump to navigation Jump to search
(stub entries)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{under construction}}
{{under construction}}
TODO intro


== Encryption ==
== Encryption ==
Line 9: Line 7:
=== Full-Disk Encryption ===
=== Full-Disk Encryption ===


Full-disk encryption encrypts the entire disk (except for the boot bits). Currently some OSes such as postmarketOS and Mobian offer an installation image, which have the option to encrypt the entire disk. Some OSes, such as postmarketOS (via pmbootstrap) and Arch Arm also offer an installation script for an fully encrypted installation.
Full-disk encryption encrypts the entire disk (except for the boot bits). Currently some operating systems such as postmarketOS and Mobian offer an installation image, which have the option to encrypt the entire disk. Some operating systems, such as postmarketOS (via pmbootstrap) and Arch Arm also offer an installation script for an fully encrypted installation.


Decryption is done at boot after entering the encryption password via an on-screen keyboard (Osk-sdl).
Decryption is done at boot after entering the encryption password via an on-screen keyboard (Osk-sdl).
Line 21: Line 19:
For safety reasons it is highly recommended to only use SSH in combination with keys, instead of simple numeric passwords.
For safety reasons it is highly recommended to only use SSH in combination with keys, instead of simple numeric passwords.


TODO: simply how-to of creating and copying SSH keys + certain SSH settings
To generate a key pair for ssh, open a terminal on your local computer, and type
 
ssh-keygen
 
It will ask you where to save the key pair. By default, this is in ~./ssh . Usually it's best to keep it in the default location. If you have previously generated a key pair, it will ask you if you wish to overwrite your existing one. You probably do not want to do this, as you will no longer be able to use your existing key pair for authentication.
 
Next, you will be prompted to enter a passphrase. It is recommended that you use this feature.
 
{{Info|Do not share your private key with anyone, nor change its file permissions}}
 
 
 
Now, you must start SSHD on your distribution of choice, as this process varies depending on init system, please consult the documentation of your distribution.
 
 
Now enabled, you can copy over your public key either manually, or via
 
ssh-copy-id $username@$ipaddress
 
replacing the variables "$username" and "$ipaddress" with the appropriate values, e.g user@192.168.1.15
 
 
You may see a message similar to this
 
Output
The authenticity of host '192.168.1.15 (192.168.1.15)' can't be established.
ECDSA key fingerprint is fd:fd:d4:f9:57:fe:23:44:e1:55:00:bd:d6:6d:42:fe.
Are you sure you want to continue connecting (yes/no)?
 
This will happen anytime you connect to a new host. Type "yes" and hit enter.


== Hardening ==
finally, to disable password authentication, type


== Hardware ==
sed -i -E 's/#?PasswordAuthentication yes/PasswordAuthentication no/' /etc/ssh/sshd_config


=== USB ===
as root on your PinePhone and either restart the sshd service, or reboot your device


== Validation ==
[[Category:PinePhone]]
=== dm-verity ===

Latest revision as of 16:39, 20 February 2023

This page or section is under construction

Please help to review and edit this page or section. Information are subject to change.

Encryption

While encryption alone is not sufficient to protect sensitive data, it is an important tool to safeguard data in certain attack vectors.

Full-Disk Encryption

Full-disk encryption encrypts the entire disk (except for the boot bits). Currently some operating systems such as postmarketOS and Mobian offer an installation image, which have the option to encrypt the entire disk. Some operating systems, such as postmarketOS (via pmbootstrap) and Arch Arm also offer an installation script for an fully encrypted installation.

Decryption is done at boot after entering the encryption password via an on-screen keyboard (Osk-sdl).

Encrypted home directory

SSH

An open SSH port is a typical gateway for attackers on any device exposed to the public Internet. Exposed devices might be attacked within minutes after being exposed. Typically such attacks try default passwords such as "12345", potentially putting the user at risk after connecting the phone to an open/unsecured access point, activating mobile data or mobile Internet.

For safety reasons it is highly recommended to only use SSH in combination with keys, instead of simple numeric passwords.

To generate a key pair for ssh, open a terminal on your local computer, and type

ssh-keygen 

It will ask you where to save the key pair. By default, this is in ~./ssh . Usually it's best to keep it in the default location. If you have previously generated a key pair, it will ask you if you wish to overwrite your existing one. You probably do not want to do this, as you will no longer be able to use your existing key pair for authentication.

Next, you will be prompted to enter a passphrase. It is recommended that you use this feature.

Note: Do not share your private key with anyone, nor change its file permissions


Now, you must start SSHD on your distribution of choice, as this process varies depending on init system, please consult the documentation of your distribution.


Now enabled, you can copy over your public key either manually, or via

ssh-copy-id $username@$ipaddress 

replacing the variables "$username" and "$ipaddress" with the appropriate values, e.g user@192.168.1.15


You may see a message similar to this

Output
The authenticity of host '192.168.1.15 (192.168.1.15)' can't be established.
ECDSA key fingerprint is fd:fd:d4:f9:57:fe:23:44:e1:55:00:bd:d6:6d:42:fe.
Are you sure you want to continue connecting (yes/no)? 

This will happen anytime you connect to a new host. Type "yes" and hit enter.

finally, to disable password authentication, type

sed -i -E 's/#?PasswordAuthentication yes/PasswordAuthentication no/' /etc/ssh/sshd_config

as root on your PinePhone and either restart the sshd service, or reboot your device