chore: reformat
parent
fab273aa7e
commit
b5c5b31812
|
@ -265,21 +265,23 @@ restic -r rclone:remote:PrivateData restore latest --target <span class="pl-k">~
|
||||||
There are many strategies that I process to react as if something strange
|
There are many strategies that I process to react as if something strange
|
||||||
is happening to my devices.
|
is happening to my devices.
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<ul>
|
||||||
If I lost my laptops, single laptop or all, do not panic as long as I have
|
<li>
|
||||||
my phones. The OTPs are in there, the passwords are in Bitwarden cloud,
|
If I lost my laptops, single laptop or all, do not panic as long as I
|
||||||
other data is in Google Drive so nothing is lost here.
|
have my phones. The OTPs are in there, the passwords are in Bitwarden
|
||||||
</p>
|
cloud, other data is in Google Drive so nothing is lost here.
|
||||||
<p>
|
</li>
|
||||||
If I lost my phone, but not my laptops, I use the OTPs which are stored
|
<li>
|
||||||
locally in my laptops.
|
If I lost my phone, but not my laptops, I use the OTPs which are stored
|
||||||
</p>
|
locally in my laptops.
|
||||||
<p>
|
</li>
|
||||||
In the worst situation, I lost everything, my laptops, my phone. The first
|
<li>
|
||||||
step is to recover my SIM, then log in to Google account using the
|
In the worst situation, I lost everything, my laptops, my phone. The
|
||||||
password and SMS OTP. After that, log in to Bitwarden account using the
|
first step is to recover my SIM, then log in to Google account using the
|
||||||
master password and OTP from Gmail, which I open previously.
|
password and SMS OTP. After that, log in to Bitwarden account using the
|
||||||
</p>
|
master password and OTP from Gmail, which I open previously.
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
<h2>
|
<h2>
|
||||||
<a
|
<a
|
||||||
id="user-content-the-end"
|
id="user-content-the-end"
|
||||||
|
|
|
@ -92,14 +92,12 @@ Because if I want to access my OTPs in the cloud, I should log in, and then inpu
|
||||||
|
|
||||||
There are many strategies that I process to react as if something strange is happening to my devices.
|
There are many strategies that I process to react as if something strange is happening to my devices.
|
||||||
|
|
||||||
If I lost my laptops, single laptop or all, do not panic as long as I have my phones.
|
- If I lost my laptops, single laptop or all, do not panic as long as I have my phones.
|
||||||
The OTPs are in there, the passwords are in Bitwarden cloud, other data is in Google Drive so nothing is lost here.
|
The OTPs are in there, the passwords are in Bitwarden cloud, other data is in Google Drive so nothing is lost here.
|
||||||
|
- If I lost my phone, but not my laptops, I use the OTPs which are stored locally in my laptops.
|
||||||
If I lost my phone, but not my laptops, I use the OTPs which are stored locally in my laptops.
|
- In the worst situation, I lost everything, my laptops, my phone.
|
||||||
|
The first step is to recover my SIM, then log in to Google account using the password and SMS OTP.
|
||||||
In the worst situation, I lost everything, my laptops, my phone.
|
After that, log in to Bitwarden account using the master password and OTP from Gmail, which I open previously.
|
||||||
The first step is to recover my SIM, then log in to Google account using the password and SMS OTP.
|
|
||||||
After that, log in to Bitwarden account using the master password and OTP from Gmail, which I open previously.
|
|
||||||
|
|
||||||
## The end
|
## The end
|
||||||
|
|
||||||
|
|
|
@ -77,7 +77,8 @@ This is where I build Go program.
|
||||||
- `CGO_ENABLED=0` because I don't want to mess with C libraries.
|
- `CGO_ENABLED=0` because I don't want to mess with C libraries.
|
||||||
- `GOOS=linux GOARCH=amd64` is easy to explain, Linux with x86-64.
|
- `GOOS=linux GOARCH=amd64` is easy to explain, Linux with x86-64.
|
||||||
- `GOAMD64=v3` is new since [Go 1.18](https://go.dev/doc/go1.18#amd64),
|
- `GOAMD64=v3` is new since [Go 1.18](https://go.dev/doc/go1.18#amd64),
|
||||||
I use v3 because I read about AMD64 version in [Arch Linux rfcs](https://gitlab.archlinux.org/archlinux/rfcs/-/blob/master/rfcs/0002-march.rst). TLDR's newer computers are already x86-64-v3.
|
I use v3 because I read about AMD64 version in [Arch Linux rfcs](https://gitlab.archlinux.org/archlinux/rfcs/-/blob/master/rfcs/0002-march.rst).
|
||||||
|
TLDR's newer computers are already x86-64-v3.
|
||||||
- `-tags timetzdata` to embed timezone database in case base image does not have.
|
- `-tags timetzdata` to embed timezone database in case base image does not have.
|
||||||
- `-trimpath` to support reproduce build.
|
- `-trimpath` to support reproduce build.
|
||||||
- `-ldflags="-s -w"` to strip debugging information.
|
- `-ldflags="-s -w"` to strip debugging information.
|
||||||
|
|
Loading…
Reference in New Issue