s83/privacy-guides
1
0
Fork 0
mirror of https://github.com/sunknudsen/privacy-guides.git synced 2025-02-23 09:13:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Raspberry Pi private IP

Browse Source
This commit is contained in:
Sun Knudsen 2020-12-10 08:16:05 -05:00
parent a35535fbc6
commit d79fb8c0ff
No known key found for this signature in database
GPG Key ID: 1FA767862BBD1305
2 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
how-to-configure-hardened-raspberry-pi-os-server/README.md
View File

@ -149,12 +149,12 @@ ip a
### Step 9: log in to Raspberry Pi over SSH
Replace `10.0.1.69` with IP of Raspberry Pi.
Replace `10.0.1.248` with IP of Raspberry Pi.
When asked for password, enter password from [step 5](#step-5-log-in-as-pi-using-keyboard-and-change-password-using-passwd).
```shell
ssh pi@10.0.1.69
ssh pi@10.0.1.248
```
### Step 10: configure pi SSH authorized keys
@ -181,12 +181,12 @@ exit
### Step 12: log in to Raspberry Pi over SSH (using `pi` private key)
Replace `10.0.1.69` with IP of Raspberry Pi.
Replace `10.0.1.248` with IP of Raspberry Pi.
When asked for password, enter password from [step 1](#step-1-create-ssh-key-pair-on-computer).
```shell
ssh pi@10.0.1.69 -i ~/.ssh/pi
ssh pi@10.0.1.248 -i ~/.ssh/pi
```
### Step 13: disable pi Bash history
@ -395,12 +395,12 @@ exit
#### Log in
Replace `10.0.1.69` with IP of Raspberry Pi.
Replace `10.0.1.248` with IP of Raspberry Pi.
When asked for password, enter password from [step 1](#step-1-create-ssh-key-pair-on-computer).
```shell
ssh pi@10.0.1.69 -i ~/.ssh/pi
ssh pi@10.0.1.248 -i ~/.ssh/pi
```
#### Switch to root

12
how-to-configure-strongswan-client-on-headless-debian-based-linux-computer/README.md
View File

@ -91,10 +91,10 @@ Getting CA Private Key
### Step 2: log in to client computer
Replace `pi@10.0.1.69` with SSH destination of client computer and `~/.ssh/pi` with path to associated private key.
Replace `pi@10.0.1.248` with SSH destination of client computer and `~/.ssh/pi` with path to associated private key.
```shell
ssh pi@10.0.1.69 -i ~/.ssh/pi
ssh pi@10.0.1.248 -i ~/.ssh/pi
```
### Step 3: switch to root
@ -390,7 +390,7 @@ systemctl restart strongswan
```shell
$ ipsec status
Security Associations (1 up, 0 connecting):
ikev2[1]: ESTABLISHED 3 minutes ago, 10.0.1.69[bob@vpn-server.com]...185.193.126.203[vpn-server.com]
ikev2[1]: ESTABLISHED 3 minutes ago, 10.0.1.248[bob@vpn-server.com]...185.193.126.203[vpn-server.com]
ikev2{1}: INSTALLED, TUNNEL, reqid 1, ESP in UDP SPIs: c3fcabed_i c2b0c4cd_o
ikev2{1}: 10.0.2.171/32 === 0.0.0.0/0
```
@ -449,10 +449,10 @@ systemctl restart dnsmasq
### Step 17: log in to client computer
Replace `pi@10.0.1.69` with SSH destination of client computer and `~/.ssh/pi` with path to associated private key.
Replace `pi@10.0.1.248` with SSH destination of client computer and `~/.ssh/pi` with path to associated private key.
```shell
ssh pi@10.0.1.69 -i ~/.ssh/pi
ssh pi@10.0.1.248 -i ~/.ssh/pi
```
### Step 18: switch to root
@ -472,7 +472,7 @@ systemctl restart strongswan
```shell
$ ipsec status
Security Associations (1 up, 0 connecting):
ikev2[1]: ESTABLISHED 3 minutes ago, 10.0.1.69[bob@vpn-server.com]...185.193.126.203[vpn-server.com]
ikev2[1]: ESTABLISHED 3 minutes ago, 10.0.1.248[bob@vpn-server.com]...185.193.126.203[vpn-server.com]
ikev2{1}: INSTALLED, TUNNEL, reqid 1, ESP in UDP SPIs: c3fcabed_i c2b0c4cd_o
ikev2{1}: 10.0.2.2/32 === 0.0.0.0/0
```