Do yourself a favor, move your Ctrl to your CapsLock key.

setxkbmap -option ctrl:nocaps

changelog

v1.2.1

• makefile has now install and uninstall recipes

v1.2.0

• using $NOTIFY env variable
• news-update calls aftersh script after update routine

git clone https://git.sr.ht/~umgeher/sfeed-news

Homepage.

Piece of cake… As root:

bioctl -P $DISK

where $DISK is the target disk.

OpenVPN is a free and open-source virtual private network (VPN).

Install

Let’s install the openvpn client.

pkg_add openvpn

Settings

Config file

Assuming that you have an openvpn settings file, calling here as setup.ovpn.

cat setup.ovpn

client
proto tcp-client
remote 191.8.146.114 1194
dev tun
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
verify-x509-name server_lBklUYL2BA98l9B3 name
auth SHA256
auth-nocache
cipher AES-128-GCM
tls-client
tls-version-min 1.2
tls-cipher TLS-ECDHE-ECDSA-WITH-AES-128-GCM-SHA256
ignore-unknown-option block-outside-dns
setenv opt block-outside-dns # Prevent Windows 10 DNS leak
verb 3
<ca>
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
</ca>
<cert>
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN ENCRYPTED PRIVATE KEY-----
...
-----END ENCRYPTED PRIVATE KEY-----
</key>
<tls-crypt>
#
# 2048 bit OpenVPN static key
#
-----BEGIN OpenVPN Static key V1-----
...
-----END OpenVPN Static key V1-----
</tls-crypt>

ETC

Let’s create a directory to ours opvn files, as root:

mkdir -p /etc/openvpn

Store your opvn files in /etc/openvpn.

Manual

To connect use:

/usr/local/sbin/openvpn --config /etc/openvpn/setup.ovpn

If you need to provide a password, use --askpass flag.

/usr/local/sbin/openvpn --askpass --config /etc/openvpn/setup.ovpn

Daemon

Create a hostname file to your new network interface.

touch /etc/hostname.tun0

Edit the hostname.tun0 file.

up
!/usr/local/sbin/openvpn --daemon --config /etc/openvpn/setup.ovpn

Now you can setup your interface.

ifconfig tun0 up

draft…

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

“Talk is cheap. Show me the code.”

– Linus Torvalds

History

On 3 April 2005, Linus Torvalds began the development of git, after many Linux kernel developers gave up access to BitKeeper. Just 3 days after, on 6 April, Torvalds announced the project. And the next day, it became self-hosting.

On 26 July 2005, Linus Torvalds turned over git’s project maintenance to Junio Hamano. Hamano is the project’s core maintainer since.

Workflow

The basic/usual git workflow is the following:

• Create/clone a git repository, all your work is done in this Working Directory.
• Once your work reaches your goal, your changes are added to the Staging Area.
• Now your Staging Area contains everything you want to commit, you can save changes to the git repository.

Resume

Setup

Before you use git, you need to setup your name and email.

Setting up name and email

git config --global user.name "Liz Umgeher"
git config --global user.email "liz@umgeher.org"

Create a repository

git init

Clone a repository

git clone [url/path]

Add a file

git add file

Remove a file

git rm file

Checking status

git status

Commit changes

git commit 

Resume: basic commands