Here is irregular verbs dictionary made by Igor Mostitsky which contains:
More than 500 irregular verbs; more than 300 verbs have translations (English to Russian actually). Most important for learning verbs have specific mark (importance rate): one bold point corresponds to one rank level. 5 is the highest rank. Most popular verbs has transcription.
Here are two links to download either DSL or LSD files
There are serveral tutorials in the internet (this and this). Which describes installation process OpenVPN on linux.
They both not so applicable for Fedora 26 because from moment they was written it has been several years and there are many discrepancies.
And when I ended them up and faced several issues:
Why I can ping but cannot access internet/local network behind the vpn server?
Where keys should be placed?
how to use Easy-RSA v3 instead v2?
how to omit password on service start up?
1) First of all install necessary dependencies
1
sudo dnf install openvpn easy-rsa
2) Copy rsa scripts to the home folder
1
2
cp -ai /usr/share/easy-rsa/3/* ~/openvpn-ca
cd ~/rsa
3) According to this start a new PKI and build a CA keypair/cert
1
2
./easyrsa init-pki
./easyrsa build-ca nopass
4) Build Server certificate, key
1
./easyrsa build-server-full server nopass
5) Build Client certificate, key
1
./easyrsa build-client-full client1 nopass
you can omitt nopass on steps 3,4,5 if you need to
6) Generate a strong Diffie-Hellman keys
1
./easyrsa gen-dh
7) Generate HMAC signature to strengthen the server’s TLS integrity verification capabilities
1
openvpn --genkey --secret pki/ta.key
8) Before openvpn server setting up we need to put appropriate keys ca.crt ca.key server.crt server.key ta.key dh.pem into /etc/openvpn/server/keys folder
NB! server corresponts with the configuration file name in /etc/openvpn/server such as server.conf. So if you have myserver.conf you have to replace server with myserver
Done! We successfully deployed our OpenVPN server, and we are ready to move on and set up the client
Client setup
As you remember we have already generated client1.crt and client1.key at the step 5. And now we need combine them with our general Certificates of Authority in order to build client config file.
1) First of all we need generate Client Configurations. Lets create client-configs directory and prepare with the keys
remote server_IP_address 1194 #place your server address here
proto udp # update with specified protocol
next uncomment (by removing ;)
1
2
user nobody
group nogroup
NB: If you are using CentOS, change the group from nogroup to nobody to match the distribution’s available groups
and comment out the lines because we place them directly in client’s config
1
2
3
#ca ca.crt
#cert client.crt
#key client.ke
add this lines at the end of the file
1
2
auth SHA256
key-direction 1
5) Next, we will create a simple script to compile our base configuration with the relevant certificate, key, and encryption files. This will place the generated configuration in the ~/client-configs/ files directory.
1
nano ~/client-configs/make_config.sh
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
BASE_CONFIG=~/client-configs/base.conf
KEY_DIR=~/client-configs/keys
OUTPUT_DIR=~/client-configs
cat ${BASE_CONFIG} \
<(echo -e '<ca>') \
${KEY_DIR}/ca.crt \
<(echo -e '</ca>\n<cert>') \
${KEY_DIR}/${1}.crt \
<(echo -e '</cert>\n<key>') \
${KEY_DIR}/${1}.key \
<(echo -e '</key>\n<tls-auth>') \
${KEY_DIR}/ta.key \
<(echo -e '</tls-auth>') \
> ${OUTPUT_DIR}/${1}.ovpn
make that file executable
1
chmod 700 ~/client-configs/make_config.sh
6) Execute that file with client1 input parameter
1
./make_config.sh client1
If everything went well, we should have a client1.ovpn file in our ~/client-configs/ directory
7) Now that file can be used on the client machine
