Linux

A quick guide about how to migrate a signed zone from dnssec-tools to OpenDNSSEC.

I’ve configured my own web frontend for git using gitweb and git-http-backend.

I wanted to use Nginx as the webserver, but unfortunately there was a piece of software missing: fcgiwrap.  It’s packaging is a work in progress, so I have packaged it myself and now it is available in this copr, so you can download it from there.

You can configure your country’s regulatory domain, creating the file /etc/modprobe.d/cfg80211.conf with this content:

options cfg80211 ieee80211_regdom=ES

Don’t forget to change ES with your country code.

The Raspberry Pi images are whole disk images, and they contain generally two partitions inside. To mount one of those partitions you can use this method.

I’ve learned how to boot a host and load the Fedora installer directly from HTTP. This has enabled me to install Fedora in a VPS which didn’t have the Fedora ISOs available and I cannot upload any other. All of this thanks to the virtual ethernet card and its gPXE firmware.

I’ve recently discovered modoboa, a mail hosting and management platform which looks very promising. It uses Django and can be a frontend of postfix, amavisd-new, radicale, etc.

I’ve submitted some RPM packages based on the previous work of Didier, and will begin to do some tests in a couple of days to see how everything plays together.

Any help/suggestion is welcomed.

To extract an attachment from a raw email message, clean the file to leave only the base64 attachment and do: base64 -di encoded_file > decoded_file

This post has a very good explanation of the problems I’ve been suffering with my IPsec tunnels recently:

MTU woes in IPsec tunnels and how you can fix it

Two things have fixed my stalled transmissions over IPsec tunnels:

1. Clamping the MSS of the IPsec connections to 1280
2. Setting the sysctl net.ipv4.tcp_mtu_probing=1

As seen in this post, the values of net.ipv4.tcp_mtu_probing are:

Using this recipe you’ll get a single ssh-agent and a single gpg-agent running for your user and the correct environmental variables will be set everywhere. Just add this code to your ~/.bashrc: [code lang=“bash”]# GPG Agent if [ -x $(which gpg-agent) ] && [ -d “${HOME}/.gnupg” ]; then oldumask=$(umask) umask 0077 pgrep -U $LOGNAME gpg-agent >/dev/null 2>&1 || gpg-agent –daemon –write-env-file “${HOME}/.gnupg/gpg-agent-info” >/dev/null 2>&1 umask $oldumask GPG_TTY=$(tty) export GPG_TTY if [ -r “${HOME}/.gnupg/gpg-agent-info” ]; then . “${HOME}/.gnupg/gpg-agent-info” export GPG_AGENT_INFO fi fi

Please, be careful with this new kernel, I have suffered from multiple fs corruptions. Give a look to:

http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg38092.html http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg38039.html

It seems that the bug is already identified, so a fix will land soon. Great news!