-
Run the command:
python pixiv_auth.py login
This will open the browser with Pixiv login page.
We will tackle this process in 10 steps listed below.
I didn't want to repeat some sections well explained in the UEFI Process. You can refer there and follow due process.
Namely;
- Connecting to WiFi.
[package] | |
name = "xmlformat" | |
version = "0.1.0" | |
authors = ["aaron"] | |
edition = "2018" | |
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html | |
[dependencies] | |
xmltree = "0.10" |
-
After installing mitmproxy run it (just type
mitmproxy
) in a terminal session and quit. This will create the necessaries certificates files at~/.mitmproxy
. -
Extract the certificate to
.crt
format:
openssl x509 -in ~/.mitmproxy/mitmproxy-ca.pem -inform PEM -out ca.crt
-
Trust the certificate into CA:
sudo trust anchor ca.crt
-
Run the
mitmproxy
again
1) Go to https://git-scm.com/ and check out the latest version of Git
Currently, the latest version is 2.18.0. Download and extract it and go to the folder of the source code:
wget https://mirrors.edge.kernel.org/pub/software/scm/git/git-2.18.0.tar.gz
tar xf git-2.18.0.tar.gz
cd git-2.18.0/
#!/bin/sed -nf | |
x ; s/^$/\n/ ; x ; t scan_unop | |
:scan_unop | |
/^[ ]*[-+][ ]*)/{i\ | |
unary op expected an operand, got ')' | |
x ; b hold_bailout | |
} | |
/^[ ]*[-+][ ]*$/{i\ | |
unary op expected an operand, got EOF | |
x ; b hold_bailout |
These commands generate and use private keys in unencrypted binary (not Base64 “PEM”) PKCS#8 format. The PKCS#8 format is used here because it is the most interoperable format when dealing with software that isn't based on OpenSSL.
OpenSSL has a variety of commands that can be used to operate on private
key files, some of which are specific to RSA (e.g. openssl rsa
and
openssl genrsa
) or which have other limitations. Here we always use
100+ different js counter apps... |