Few months ago, I've made a similar work but I wanted something a little more easier to manage. Please have a look at here for my previous work.
This time, I'm gonna do pretty much the same thing but using Pi-hole as base then modify it to include unbound and stubby.
This way, I can use the power of Pi-hole with some additional security layers:
unbound)stubby)
| #!/bin/bash | |
| # | |
| # Prints the compute capability of the first CUDA device installed | |
| # on the system, or alternatively the device whose index is the | |
| # first command-line argument | |
| device_index=${1:-0} | |
| timestamp=$(date +%s.%N) | |
| gcc_binary=${CMAKE_CXX_COMPILER:-$(which c++)} | |
| cuda_root=${CUDA_DIR:-/usr/local/cuda} |
This gist will explain how to create a DNS-over-TLS bridge for the local network.
The server part will be based on: https://dfarq.homeip.net/dns-over-tls-protect-your-network-with-ubuntu/.
Install required packaages:
In this document, I will explain how to upgrade the default systemd version from 237 to 242.
The main reason why I needed this was related to the DNS-over-TLS that was not supported in the version 237 but available from version 242.
Later, when playing with Lynis, the security auditing tool, I then discovered that the version 242 was also providing the command systemd-analyze that is used by lynis to detect if existing systemd services are configured correctly in the security context, meaning that the existing services can run as expected but needs few or several changes in their configuration to make them safe without any exploitable attack surfaces.
You can try it once you've installed the version 242 of systemd that way:
Once rebooted after patching, you will kindly greated by error: symbol 'grub_calloc' not found, entering rescue mode and way to boot the OS anymore...
The thing become even more horrible if you are using an encrypted partition plus LVM...
You can skip the steps 2 and 4 if you just have a normal partition scheme with no encryption or
LVM.
The goal of this gist is to explain how I have build a Beowulf cluster based on Raspberry Pi models 3B / 3B+ and 4B.
The cluster will be expendable with other device types. Any working computer can be added to the cluster.
Adding the following packages: Ansible, SSHFS, Slurm, MPICH and MPI4PY will give me to possiblity to run parallel computing tasks using all cluster nodes.
The final goal will be to create a low cost computing platform that can be managed with a web interface that I will create soon. Adding remote clients and compute nodes is also a part of this project.
I will explain here how to start and stop boinc depending on the host temperature.
I'm actually using a NUC to run BOINC and the Rosetta@Home project but this host is getting hot very quick and sometimes it will shutdown because of overheating.
To avoid this, I've requested the help of @AenBleidd, one of the BOINC developers. He gave me idea to use lm-sensors and CRON to run a script that will start / stop BOINC.
The goal of this gist is to explain how I have build a Beowulf cluster based on Raspberry Pi models 3B / 3B+ and 4B.
The cluster will be expendable with other device types. Any working computer can be added to the cluster.
The cluster will be initially used to compute workunits from the Rosetta@Home project.
In this gist I will stay with Raspberry Pi nodes.