LinuxPizza

Why I decided to block gab.[com|ai], and some other thoughts.

It has not gone unoticed, but gab – the plattform that champions “free speechs” has joined the fediverse. Why? Because probably (hopefully) they are running out of money.

4th of July, 2019 – gab did enter the fediverse with glory and might. Users loved it and the software was great!

gab-5 No it was'nt. People hated it and complained everywhere over the extremely bad performance and the unreliable service. I enjoyed the show, it was great because it means that gab is loosing money when the deploy did not work well. gab-500 gab also uses cloudflare gab-cf

gab-error

The funny thing aside for a moment, and lets focus on the dangerous and evil side of gab. Gab claims to be a champion of free speech, sadly this has turned into a harbor of extremist – actual Nazis.

I decided to create an account on the platform to observe it myself. I did not have to scroll much to be greeted with this: gab-1

More: gab-2

And more: gab-3 This was presented to me withing the first minute.

gab-trending So much for the All are welcome slogan.

You maybe wonder – why does a platform allow content that celebrates genocide, fascism , violence, hate, and authoritarian governments and hides it in the free speech bucket? I do not know, I honestly do not know. The founder of gab – Andrew Torba – is even a proclaimed christian. Is'nt christianity supposed to be the opposite of the content that is spreading on gab?

This is why I have suspended gab on my instance. And if you as an admin does it – great! But it would also be great if people could federate with them to be able to ridicule them (or as some people calls it – virtual milk-shaking).

We can't let history repeat itself.

Note: I do publish social.linux.pizza's blocklist here

Since I was a little kid I've always had a love for computes. Later on, that love transformed to a love for servers – hence that's why I got myself a tiny homelab.

Currently, the homelab is rocking the following setup: One Proliant Microserver G8 8TB disk, 8GB RAM, simple celeron CPU, 10Gbit Network running Debian 9. Currently using this as a shared storage (iSCSI) between my to hypervisors. I had two of those before, but I gave one away.


One homebuild server with an SuperMicro X9SCI/X9SCA motherboard, Xeon E3-1240 V2, 32GB RAM and 4TB storage (mostly ZFS with alot of SSD cache) Currently running Proxmox in a HA-environment


One homebuild PC that was repurposed into a server. ASRock H61 Pro BTC motherboard, Intel i5-2400, 16GB RAM and 1,1 TB of ZFS with SSD-cache storage. Also running Proxmox in a HA-environment


An EdgeRouter X-SFP (serving the secondary connection”


Three MikroTik Switches – RouterBOARD 260GS, 260GSP & CSS326-24G-2S+RM.


A Meraki accesspoint


Thinkpad W530


This is the hardware my environment utilizes. I am running Pfsense in a virtual environment instead of using the Edgerouter as the main router. The reason is that I wanted a more advanced firewall than the EdgeRouter on my “main” connection. And the reason that I run pfsense in a virtual machine is because I want the ability to easily restore backups in case if something goes wrong – which pfsense often do when I upgrade for some reason.

I hope that I can get a newer server in the coming month so I can replace my ASRock “server” and convert that one to a router instead – hopefully.

You probably came here because some friend of you mentioned “fediverse” to you, while you responded – fediverse? what is that?.

And your friend did not really wanted to explain it, so you was sent here instead.

Great! I will try my best into explaining what the “Fediverse” is, and how it might save your digital life.

The Fediverse is a name of a network of tens of thousands connected servers, consisting of many different kind of software that “speaks” to each other. The most popular software is Mastodon, that basically is a Twitter clone. The big difference is that the code that is being used on the server is publicly available to everyone, so that ensures that the code is secure and does not hide any hidden “feature” such as data collection on a massive scale, such as Twitter.

Mastodon is developed by many, but the leader and founder of the project is Eugen “Gargron” Rochko that wanted to create a social network because he was tired of having his friends and family being on different networks. And if he wanted to keep in touch with he had to create account on different places (MySpace, Twitter, Viber, Telegram and so on). And so Mastodon was born.

Today, there is thousands of Mastodon servers up and running, each one with it's own characteristic, culture, rules and people. Servers for those who love beer, cats, politics, Linux or just being social. Most of the servers is connected to each other. Yes, you can join that super-niche server that focuses exclusively on cats with moustaches, while still connecting to your friends who is on that instance about helicopters – is'nt that awesome?

Or, if you just want to listen to someone explain how it works, here is a Peertube (which is also a fediverse compatible piece of software) video explaining how it works

As a MTA lover, I always try to encourage people (especially “IT-people”) to host their own mailserver. Mostly so they actually can learn something and also that I do not like how the big providers like Google, Microsoft, Amazon etc keep eating up the market. Diversity is a key to a healthy market – but that is another topic.

This guide will mostly apply to Debian-based distros like Debian (9 or newer), Ubuntu (16.04 or newer) or any other “serverdistro”. I do assume that you already have a working mailserver that do both deliver and receive emails that are DKIM signed (or atleast perform validation with OpenDKIM), otherwhise you can read my short guide here (coming soon).

First, install OpenDMARC from the repository.

apt update
apt install opendmarc -y

Verify that the user and group opendmarc has been created by checking /etc/passwd and /etc/group. Otherwhise, create them. When you have installed it, verify the installation by running this:

opendmarc -V

You will get something like this (the version number is not that important yet):

opendmarc: OpenDMARC Filter v1.3.2       
    SMFI_VERSION 0x1000001       
    libmilter version 1.0.1       
    Active code options:               
    WITH_SPF               
    WITH_SPF2

Great! Let's proceed to configuring opendmarc First, take a backup of the current opendmarc.conf, it will save some headache in the future if you want to redo it:

cp /etc/opendmarc.conf /etc/opendmarc.conf.BAK

Edit /etc/opendmarc.conf with the following:

AuthservID [SERVERHOSTNAME]
FailureReports true
PidFile /var/run/opendmarc.pid
RejectFailures false
SPFSelfValidate yes
Socket inet:8893@localhost
SoftwareHeader true
Syslog true
SyslogFacility mail
TrustedAuthservIDs [SERVERHOSTNAME]
HistoryFile /var/run/opendmarc/opendmarc.dat
UMask 0002
UserID opendmarc

Dont forget to restart opendmarc

service opendmarc restart 

Proceed with adding opendmarc as a milter in postfix. I am assuming that you already have opendkim enabled as a milter like this:

smtpd_milters = inet:localhost:8891
non_smtpd_milters = inet:localhost:8891

We now need to add the opendmarc milter into the postfix configuration, it is important that you add it AFTER the opendkim milter, otherwhise opendmarc will not be able to check if the DKIM key is valid.

smtpd_milters = inet:localhost:8891,inet:localhost:8893
non_smtpd_milters = inet:localhost:8891,inet:localhost:8893milter_default_action   = accept

The last one is pretty important, so if one of your milters does not work for some reason – Postfix will still let it throu. Restart postfix

service postfix restart

We should now be able to test the configuration by sending an email from example a gmail.com account to an email address on your email-server and check your logs if opendmarc actually works.

tail -f /var/log/mail.log | grep "opendmarc"

You should be able to see this:

Apr 26 12:16:38 mx opendmarc[31490]: 5155751C32: SPF(mailfrom): dmarctest@linux.pizza pass
Apr 26 12:16:39 mx opendmarc[31490]: 5155751C32: linux.pizza pass

Great! Your server does now validate DMARC policies! If you just wanted this basic functionality, you are done now. But there is always room for improvement!

Adding a Public-suffix list

This can be achieved in the following simple steps: Create a catalogue (and change ownership) for the list to be downloaded to:

mkdir -p /etc/opendmarc/
chown opendmarc: /etc/opendmarc

Set up a cronjob to download the suffix list once a week

crontab -u opendmarc -e

And this line:

@weekly/usr/bin/wget -k -q -N -P /etc/opendmarc https://publicsuffix.org/list/effective_tld_names.dat

Also, just download the list so you have it before you configure opendmarc to use it:

wget -k -q -N -P /etc/opendmarc https://publicsuffix.org/list/effective_tld_names.dat 

Finally, configure opendmarc to actually use that list, put this on the bottom in /etc/opendmarc.conf and restart opendmarc

PublicSuffixList /etc/opendmarc/effective_tld_names.dat
service opendmarc restart 

Awesome! You are now done with the OpenDMARC. Next up – adding DMARC reporting, this will be in an upcoming post.

During my short IT-career, I have dealt with alot people who struggle with generating a .csr file (certificate signing request) on Linux. Windows (especially IIS) have a more clearer approach so that can most of the people figure out by themselves without having to ask to many questions :)

The following example generates a .csr and a .key file for the Company “Company Name”, located in some country in the city “City”. Just replace the variables to your liking.

DOMAIN=www.example.com
COUNTRY=2 letter country code
ORG="Company Name"
CITY="City"

openssl req -utf8 -nameopt multiline,utf8 -new -newkey rsa:2048 -nodes -sha256 -out $DOMAIN.csr -keyout $DOMAIN.key -subj "/C=${COUNTRY}/ST=${STATE}/L=${CITY}/O=${ORG}/OU=IT/CN=$DOMAIN"

Sometimes, you do want to generare a .csr file that includes two or more domains – a SAN certificate. Using the same variable as above, we can now add more CN's to the .csr:

openssl req -utf8 -nameopt multiline,utf8 -new -newkey rsa:2048 -nodes -sha256 -out $DOMAIN.csr -keyout $DOMAIN.key -subj "/C=${COUNTRY}/ST=${STATE}/L=${CITY}/O=${ORG}/OU=IT/CN=$DOMAIN" -config <(
cat <<-EOF
[req]
default_bits = 2048
default_md = sha256
req_extensions = req_ext
distinguished_name = dn
[ dn ]
[ req_ext ]
subjectAltName = @alt_names
[alt_names]
DNS.1 = www.example.se
DNS.2 = example.se
DNS.3 = www.example.it
DNS.3 = example.it
DNS.3 = www.example.fi
DNS.3 = example.fi
DNS.3 = www.example.org
DNS.3 = example.org
EOF
)

I hope this can prevent some headache for one or two :)

#linux #openssl #csr #ssl #tls #certificate