DNS-level adblock on the go with blocky
2024-05-31
Introduction#
An adblocker is something you commonly find installed in browsers, usually through an extension. However, what if you wanted an adblocking system that was a bit deeper? Something that doesn't require a browser extension, and gives you a consistent adblocking system? This is where DNS-level adblockers like AdGuard Home or Pi-hole come in.
DNS?#
DNS stands for Domain Name System. It's what points URLs like https://duck.com to an IP address (like 52.142.124.215), making it much easier to find things on the internet.
DNS-level adblockers work by filtering out queries for URLs pointing to IP addresses serving ads. In this blog post, I'll use blocky as an example of one such adblocker for demonstration purposes.
Setting up blocky#
NixOS configuration#
There's a configuration option for blocky provided by NixOS, so you can enable and configure it in your NixOS config:
1 services.blocky = {
+DNS-level adblock on the go with blocky DNS-level adblock on the go with blocky
2024-05-31Introduction#
An adblocker is something you commonly find installed in browsers, usually through an extension. However, what if you wanted an adblocking system that was a bit deeper? Something that doesn't require a browser extension, and gives you a consistent adblocking system? This is where DNS-level adblockers like AdGuard Home or Pi-hole come in.
DNS?#
DNS stands for Domain Name System. It's what points URLs like https://duck.com to an IP address (like 52.142.124.215), making it much easier to find things on the internet.
DNS-level adblockers work by filtering out queries for URLs pointing to IP addresses serving ads. In this blog post, I'll use blocky as an example of one such adblocker for demonstration purposes.
Setting up blocky#
NixOS configuration#
There's a configuration option for blocky provided by NixOS, so you can enable and configure it in your NixOS config:
1 services.blocky = {
2 enable = true;
3 settings = {
4 prometheus.enable = true;
diff --git a/public/blog/btrfs-raid-setup/index.html b/public/blog/btrfs-raid-setup/index.html
new file mode 100644
index 0000000..b8fcb40
--- /dev/null
+++ b/public/blog/btrfs-raid-setup/index.html
@@ -0,0 +1,17 @@
+RAID with btrfs RAID with btrfs
2024-12-30Introduction#
What is RAID?#
Shamelessly copying from the relevant Wikipedia page:
RAID (/reɪd/; redundant array of inexpensive disks or redundant array of independent disks) is a data storage virtualization technology that combines multiple physical data storage components into one or more logical units for the purposes of data redundancy, performance improvement, or both.
That definition works well enough in case you don't already know what RAID is, which I doubt is the case for anyone reading this post.
Why use it?#
Ever had a hard drive containing important data - without any backups - fail? Or, a little less likely, had a mission-critical file server break for a few hours because a drive failed? These are the two biggest problems that RAID solves.
That's great, but how do I use it?#
And finally, we have the main body of this blog post! While frustatingly looking up how to do slightly weird things with RAID using btrfs, I found the lack of documentation annoying - so, I thought I'd make this blog post to aggregate a bunch of commands.
And so, the list:
RAID1#
- Setting up RAID1 with two disks:
mkdir /mnt/raid1 # make the RAID1 pool
+btrfs device add /dev/sdA1 /mnt/raid1 # add the first device
+btrfs device add /dev/sdB1 /mnt/raid1 # add the second device
+
- Setting up RAID1 when you already have a disk with some data on it and want to add another:
btrfs device add /dev/sdB1 /mnt/raid1 # add the second device
+btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/raid1 # distribute data to get the array set up
+
RAID0#
- Setting up RAID0 with two disks - exactly the same as with RAID1:
mkdir /mnt/raid1 # make the RAID1 pool
+btrfs device add /dev/sdA1 /mnt/raid0 # add the first device
+btrfs device add /dev/sdB1 /mnt/raid0 # add the second device
+
You can also continue to add more devices. The total storage available at the end of the process is the sum of the storage available on each drive:btrfs device add /dev/sdC1 /mnt/raid0 # add the third device
+btrfs device add /dev/sdD1 /mnt/raid0 # add the fourth device
+# and so on...
+
- Setting up RAID0 when you already have a disk with some data on it and want to add another:
btrfs device add /dev/sdA1 /mnt/raid0 # add the second device
+btrfs balance start -dconvert=raid0 /mnt/raid0 # distribute data to get the array set up
+
Nested RAID levels#
Btrfs also supports RAID10 (or RAID1+0) which is a combination of RAID1 and RAID0 as demonstrated by the following image: 
However, as you can see, RAID10 requires n disks where n is an even number greater than or equal to 4. Furthermore, if you tried using devices of varying sizes, space would likely be wasted. So what would you do if you had 3 devices, with, for example, sizes of 1TB, 500GB, and 500GB?
A possible solution here would be to split the 1TB drive into two equal partitions of 500GB, and pass them to btrfs as independant drives.
Theoretically, you could also combine the two 500GB drives into a RAID0 partition and combine them through RAID1 with the 1TB drive (creating a nested RAID01/RAID0+1 array), but this seems to be unsupported by btrfs.
In general, setting up a RAID10 array with btrfs looks like this:
mkdir /mnt/raid10 # make the RAID10 pool
+btrfs device add /dev/sdA1 /dev/sdB1 /dev/sdC1 /dev/sdD1 /mnt/raid10 # add the drives
+btrfs balance start -dconvert=raid10 -mconvert=raid10 /mnt/raid10 # distribute data to get the array set up
+
Useful resources#
- btrfs disk usage calculator - I found this somewhat useful, but it won't tell you how to get whatever configuration you set up to work
- The Wikipedia page on nested RAID levels
All of the posts for my blog
- 2024-05-31T00:00:00+00:00
+ 2024-12-30T00:00:00+00:00
https://devraza.giize.com/blog/feed.xml
+
+ RAID with btrfs
+ 2024-12-30T00:00:00+00:00
+ 2024-12-30T00:00:00+00:00
+
+ https://devraza.giize.com/blog/btrfs-raid-setup/
+ <h1 id="introduction">Introduction<a class="zola-anchor" href="#introduction" aria-label="Anchor link for: introduction">#</a></h1>
+<h2 id="what-is-raid">What is RAID?<a class="zola-anchor" href="#what-is-raid" aria-label="Anchor link for: what-is-raid">#</a></h2>
+<p>Shamelessly copying from the <a rel="nofollow noreferrer" href="https://en.wikipedia.org/wiki/RAID">relevant Wikipedia page</a>:</p>
+<blockquote>
+<p>RAID (/reɪd/; redundant array of inexpensive disks or redundant array of independent disks) is a data storage virtualization technology that combines multiple physical data storage components into one or more logical units for the purposes of data redundancy, performance improvement, or both.</p>
+</blockquote>
+<p>That definition works well enough in case you don't already know what RAID is, which I doubt is the case for anyone reading this post.</p>
+<h2 id="why-use-it">Why use it?<a class="zola-anchor" href="#why-use-it" aria-label="Anchor link for: why-use-it">#</a></h2>
+<p>Ever had a hard drive containing important data - without any backups - fail? Or, a little less likely, had a mission-critical file server break for a few hours because a drive failed? These are the two biggest problems that RAID solves.</p>
+<h1 id="that-s-great-but-how-do-i-use-it">That's great, but how do I use it?<a class="zola-anchor" href="#that-s-great-but-how-do-i-use-it" aria-label="Anchor link for: that-s-great-but-how-do-i-use-it">#</a></h1>
+<p>And finally, we have the main body of this blog post! While frustatingly looking up how to do <em>slightly</em> weird things with RAID using <code>btrfs</code>, I found the lack of documentation annoying - so, I thought I'd make this blog post to aggregate a bunch of commands.</p>
+<p>And so, the list:</p>
+<h2 id="raid1">RAID1<a class="zola-anchor" href="#raid1" aria-label="Anchor link for: raid1">#</a></h2>
+<ul>
+<li>Setting up RAID1 with two disks:<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">mkdir</span><span> /mnt/raid1 </span><span style="color:#888888;"># make the RAID1 pool
+</span><span style="color:#ffb964;">btrfs</span><span> device add /dev/sdA1 /mnt/raid1 </span><span style="color:#888888;"># add the first device
+</span><span style="color:#ffb964;">btrfs</span><span> device add /dev/sdB1 /mnt/raid1 </span><span style="color:#888888;"># add the second device
+</span></code></pre>
+</li>
+<li>Setting up RAID1 when you already have a disk with some data on it and want to add another:<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">btrfs</span><span> device add /dev/sdB1 /mnt/raid1 </span><span style="color:#888888;"># add the second device
+</span><span style="color:#ffb964;">btrfs</span><span> balance start</span><span style="color:#ffb964;"> -dconvert</span><span>=raid1</span><span style="color:#ffb964;"> -mconvert</span><span>=raid1 /mnt/raid1 </span><span style="color:#888888;"># distribute data to get the array set up
+</span></code></pre>
+</li>
+</ul>
+<h2 id="raid0">RAID0<a class="zola-anchor" href="#raid0" aria-label="Anchor link for: raid0">#</a></h2>
+<ul>
+<li>Setting up RAID0 with two disks - exactly the same as with RAID1:<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">mkdir</span><span> /mnt/raid1 </span><span style="color:#888888;"># make the RAID1 pool
+</span><span style="color:#ffb964;">btrfs</span><span> device add /dev/sdA1 /mnt/raid0 </span><span style="color:#888888;"># add the first device
+</span><span style="color:#ffb964;">btrfs</span><span> device add /dev/sdB1 /mnt/raid0 </span><span style="color:#888888;"># add the second device
+</span></code></pre>
+You can also continue to add more devices. The total storage available at the end of the process is the sum of the storage available on each drive:<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">btrfs</span><span> device add /dev/sdC1 /mnt/raid0 </span><span style="color:#888888;"># add the third device
+</span><span style="color:#ffb964;">btrfs</span><span> device add /dev/sdD1 /mnt/raid0 </span><span style="color:#888888;"># add the fourth device
+</span><span style="color:#888888;"># and so on...
+</span></code></pre>
+</li>
+<li>Setting up RAID0 when you already have a disk with some data on it and want to add another:<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">btrfs</span><span> device add /dev/sdA1 /mnt/raid0 </span><span style="color:#888888;"># add the second device
+</span><span style="color:#ffb964;">btrfs</span><span> balance start</span><span style="color:#ffb964;"> -dconvert</span><span>=raid0 /mnt/raid0 </span><span style="color:#888888;"># distribute data to get the array set up
+</span></code></pre>
+</li>
+</ul>
+<h2 id="nested-raid-levels">Nested RAID levels<a class="zola-anchor" href="#nested-raid-levels" aria-label="Anchor link for: nested-raid-levels">#</a></h2>
+<p>Btrfs also supports RAID10 (or RAID1+0) which is a combination of RAID1 and RAID0 as demonstrated by the following image:
+<img src="https://devraza.giize.com/img/raid10.png" alt="Image demonstrating how RAID10 looks" /></p>
+<p>However, as you can see, RAID10 requires <em>n</em> disks where <em>n</em> is an even number greater than or equal to 4. Furthermore, if you tried using devices of varying sizes, space would likely be wasted. So what would you do if you had 3 devices, with, for example, sizes of 1TB, 500GB, and 500GB?</p>
+<p>A possible solution here would be to split the 1TB drive into two equal partitions of 500GB, and pass them to btrfs as independant drives.</p>
+<p>Theoretically, you could also combine the two 500GB drives into a RAID0 partition and combine them through RAID1 with the 1TB drive (creating a nested RAID01/RAID0+1 array), but this seems to be unsupported by btrfs.</p>
+<p>In general, setting up a RAID10 array with btrfs looks like this:</p>
+<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">mkdir</span><span> /mnt/raid10 </span><span style="color:#888888;"># make the RAID10 pool
+</span><span style="color:#ffb964;">btrfs</span><span> device add /dev/sdA1 /dev/sdB1 /dev/sdC1 /dev/sdD1 /mnt/raid10 </span><span style="color:#888888;"># add the drives
+</span><span style="color:#ffb964;">btrfs</span><span> balance start</span><span style="color:#ffb964;"> -dconvert</span><span>=raid10</span><span style="color:#ffb964;"> -mconvert</span><span>=raid10 /mnt/raid10 </span><span style="color:#888888;"># distribute data to get the array set up
+</span></code></pre>
+<h1 id="useful-resources">Useful resources<a class="zola-anchor" href="#useful-resources" aria-label="Anchor link for: useful-resources">#</a></h1>
+<ul>
+<li><a rel="nofollow noreferrer" href="https://carfax.org.uk/btrfs-usage/">btrfs disk usage calculator</a> - I found this somewhat useful, but it won't tell you how to get whatever configuration you set up to work</li>
+<li><a rel="nofollow noreferrer" href="https://en.wikipedia.org/wiki/Nested_RAID_levels">The Wikipedia page on nested RAID levels</a></li>
+</ul>
+
+
DNS-level adblock on the go with blocky
2024-05-31T00:00:00+00:00
@@ -269,7 +333,7 @@ Lots of devices to read!</li>
https://devraza.giize.com/blog/selfhost-tailscale/
<h1 id="tailscale">Tailscale<a class="zola-anchor" href="#tailscale" aria-label="Anchor link for: tailscale">#</a></h1>
-<p><a rel="nofollow noreferrer" href="https://tailscale.com/">Tailscale</a> is a modern tunnel VPN service based on <a rel="nofollow noreferrer" href="https://www.wireguard.com/">WireGuard®</a> which provides a 'free' and secure means of communication between
+<p><a rel="nofollow noreferrer" href="https://tailscale.com/">Tailscale</a> is a modern tunnel VPN service based on <a rel="nofollow noreferrer" href="https://www.wireguard.com/">WireGuard®</a> which provides a 'free' and secure means of communication between
devices within a <a rel="nofollow noreferrer" href="https://tailscale.com/kb/1136/tailnet">tailnet</a> - a private network which Tailscale provides its users.</p>
<p>Essentially, it provides a private and secure way of accessing any of your devices, no matter where you are in the world - a personal WAN encompassing the entire world.</p>
<p>And on top of this, Tailscale is completely free and open-source! At least, on the surface...</p>
@@ -329,7 +393,7 @@ Headscale's a self-hostable, open-source alternative to the Tailscale contr
</span></code></pre>
<p>And that's it. A self-hosted, <em>truly</em> open-source Wireguard®-based VPN is now at your fingertips. Enjoy! Oh, but please read the conclusion before doing that:</p>
<h1 id="conclusion">Conclusion<a class="zola-anchor" href="#conclusion" aria-label="Anchor link for: conclusion">#</a></h1>
-<p>For those of you who wish to have access to something like Tailscale but value your privacy above all, you would genuinely be greatful for Headscale.
+<p>For those of you who wish to have access to something like Tailscale but value your privacy above all, you would genuinely be greatful for Headscale.
However, I've found that some are fine with what Tailscale <em>does</em> provide in regards to FOSS, and are satisfied by the raw convenience and simplicity of a non-selfhosted Tailscale control server - exactly what it hopes to provide, as shown by their self-description on their website: 'a zero-config, no-fuss VPN [provider]'.</p>
<p>Or you could just settle with bare Wireguard®.</p>
diff --git a/public/blog/hoaxes-overview/index.html b/public/blog/hoaxes-overview/index.html
index 4ad26eb..8043588 100644
--- a/public/blog/hoaxes-overview/index.html
+++ b/public/blog/hoaxes-overview/index.html
@@ -1 +1 @@
-An overview on hoaxes An overview on hoaxes
2024-01-04Introduction#
In recent times, hoaxes have become increasingly prevalent as the internet continues to expand and as more people use social media. Misinformation is on a rise - though this is information which isn't really new, the current state of things is horrible, and things really shouldn't be the way they are.
I aim for this to be a brief blog post detailing the effect of hoaxes on society, focusing on why they're so harmful.
What exactly is a hoax?#
Put simply, a hoax is made-up information, be it a story or something else. Hoaxes are created with the intent of spreading false information - for a immense variety of reasons, from jokes and causing embarrassment to provoking politic or social change1. I won't discuss the causes of hoaxes further in this blog post.
The effect of hoaxes#
Hoaxes can cause significant damage to their targets if formulated cleverly. For example:
The stock price of Apple Inc. fell significantly in October 2008 after a hoax story was submitted to CNN's user-generated news site iReport.com claiming that company CEO Steve Jobs had suffered a major heart attack. The source of the story was traced back to 4chan.
- Excerpt from the Wikipedia 4chan page
With the incredible presence of social media in our lives, spreading harmful misinformation like that above can be as simple as making a few posts - they don't even need to be very convincing! What makes matters worse is how gullible the general population is, even those educated in this sort of thing - this shows just how much influence the internet and it's contents have on us.
I would like to clarify that I'm not suggesting that people should avoid using the internet to gather information - while its reliability is incredibly questionable, the accessibility and openness it provides far beats traditional methods of gathering information (books and such). My suggestion is that people should be much more careful with how they interpret information on the internet, and perform their due diligence in their research into whatever they're aiming to learn; people should make sure that what they're reading is accurate before absorbing any information (here's your tl;dr).
That's about it for this blog post, as it was meant to be a brief way of expressing my thoughts on the matter. Thanks for reading!
An overview on hoaxes An overview on hoaxes
2024-01-04Introduction#
In recent times, hoaxes have become increasingly prevalent as the internet continues to expand and as more people use social media. Misinformation is on a rise - though this is information which isn't really new, the current state of things is horrible, and things really shouldn't be the way they are.
I aim for this to be a brief blog post detailing the effect of hoaxes on society, focusing on why they're so harmful.
What exactly is a hoax?#
Put simply, a hoax is made-up information, be it a story or something else. Hoaxes are created with the intent of spreading false information - for a immense variety of reasons, from jokes and causing embarrassment to provoking politic or social change1. I won't discuss the causes of hoaxes further in this blog post.
The effect of hoaxes#
Hoaxes can cause significant damage to their targets if formulated cleverly. For example:
The stock price of Apple Inc. fell significantly in October 2008 after a hoax story was submitted to CNN's user-generated news site iReport.com claiming that company CEO Steve Jobs had suffered a major heart attack. The source of the story was traced back to 4chan.
- Excerpt from the Wikipedia 4chan page
With the incredible presence of social media in our lives, spreading harmful misinformation like that above can be as simple as making a few posts - they don't even need to be very convincing! What makes matters worse is how gullible the general population is, even those educated in this sort of thing - this shows just how much influence the internet and it's contents have on us.
I would like to clarify that I'm not suggesting that people should avoid using the internet to gather information - while its reliability is incredibly questionable, the accessibility and openness it provides far beats traditional methods of gathering information (books and such). My suggestion is that people should be much more careful with how they interpret information on the internet, and perform their due diligence in their research into whatever they're aiming to learn; people should make sure that what they're reading is accurate before absorbing any information (here's your tl;dr).
That's about it for this blog post, as it was meant to be a brief way of expressing my thoughts on the matter. Thanks for reading!
Home server security Home server security
2024-03-28Introduction#
Home server security is pretty often overlooked from what I can tell. Any device accessible from the internet has some degree of vulnerability in the current era of the internet. I aim for this document to detail methods to amend the contemporary cybersecurity challenges faced by most homelabbers.
Justification in Depth#
Of course, my statements about home servers needing some security measures put in place aren't baseless. My own experience, as well as that of a sizable number of people on the wonderful lemmy community at selfhosted@lemmy.world shows that home servers are endlessly 'knocked' on, and that login attempts to services like SSH are made. Here's a snippet from my fail2ban filter to verify this point:
Mar 29 14:38:13 icefall fail2ban.filter[1097]: INFO [...] Found 176.126.240.158 - 2024-03-29 14:38:13
+Home server security Home server security
2024-03-28Introduction#
Home server security is pretty often overlooked from what I can tell. Any device accessible from the internet has some degree of vulnerability in the current era of the internet. I aim for this document to detail methods to amend the contemporary cybersecurity challenges faced by most homelabbers.
Justification in Depth#
Of course, my statements about home servers needing some security measures put in place aren't baseless. My own experience, as well as that of a sizable number of people on the wonderful lemmy community at selfhosted@lemmy.world shows that home servers are endlessly 'knocked' on, and that login attempts to services like SSH are made. Here's a snippet from my fail2ban filter to verify this point:
Mar 29 14:38:13 icefall fail2ban.filter[1097]: INFO [...] Found 176.126.240.158 - 2024-03-29 14:38:13
Mar 29 14:40:11 icefall fail2ban.filter[1097]: INFO [...] Found 176.126.240.158 - 2024-03-29 14:40:11
Mar 29 14:40:29 icefall fail2ban.filter[1097]: INFO [...] Found 185.8.165.204 - 2024-03-29 14:40:29
Mar 29 14:40:40 icefall fail2ban.filter[1097]: INFO [...] Found 162.212.154.58 - 2024-03-29 14:40:40
-
Within the past few minutes, I've already got a few IP addresses from all over the world taking a peak at my services. If I had my SSH port set to the standard 22, I could have expected a few rogue login attempts to have been made, too.
And, speaking of not having my SSH port set to the standard 22, I'll now move on to what you should be done to secure a home server. One thing that I think should be noted, however, is that security doesn't need to be very strong, and you generally don't need to go too far out of your way with security measures (though this definitely depends on invdividual circumstance). Honestly speaking, you probably don't have competent black hats looking to get in to your server - what you probably do have, however, are a bunch of script kiddies and perversive bots.
The list#
The fairly basic stuff you'd need to do in this case doesn't make much room for detail. So, here it all is in the form of a simple list (I've included the relevant NixOS configuration where I think it'd be useful1):
Move your SSH daemon to a non-default port, like 3291.
services.openssh = {
+
Within the past few minutes, I've already got a few IP addresses from all over the world taking a peak at my services. If I had my SSH port set to the standard 22, I could have expected a few rogue login attempts to have been made, too.
And, speaking of not having my SSH port set to the standard 22, I'll now move on to what you should be done to secure a home server. One thing that I think should be noted, however, is that security doesn't need to be very strong, and you generally don't need to go too far out of your way with security measures (though this definitely depends on invdividual circumstance). Honestly speaking, you probably don't have competent black hats looking to get in to your server - what you probably do have, however, are a bunch of script kiddies and perversive bots.
The list#
The fairly basic stuff you'd need to do in this case doesn't make much room for detail. So, here it all is in the form of a simple list (I've included the relevant NixOS configuration where I think it'd be useful1):
Move your SSH daemon to a non-default port, like 3291.
services.openssh = {
ports = [ 3291 ]; # whatever you like
};
-
Force public key authentication with SSH and disable root logins.
services.openssh.settings = {
+
Force public key authentication with SSH and disable root logins.
services.openssh.settings = {
PermitRootLogin = "no";
PasswordAuthentication = false;
};
-
Set up a pretty basic firewall - something like ufw would do the trick.
networking = {
+
Set up a pretty basic firewall - something like ufw would do the trick.
networking = {
nftables.enable = true; # use the newer nftables
firewall = {
enable = true;
diff --git a/public/blog/index.html b/public/blog/index.html
index 12230ed..996e4db 100644
--- a/public/blog/index.html
+++ b/public/blog/index.html
@@ -1 +1 @@
-Blog Posts Self-hosting DNS-level adblock on the go with blocky 2024-05-31 Home server security 2024-03-28 Selecting hardware for a (home) server 2024-01-31 Take control of tailscale with headscale 2024-01-10 Host your own private search engine with SearXNG 2023-12-31 CybersecurityMisc.
\ No newline at end of file
+Blog Posts Misc.Self-hosting DNS-level adblock on the go with blocky 2024-05-31 Home server security 2024-03-28 Selecting hardware for a (home) server 2024-01-31 Take control of tailscale with headscale 2024-01-10 Host your own private search engine with SearXNG 2023-12-31 Cybersecurity
\ No newline at end of file
diff --git a/public/blog/nfc-misconceptions/index.html b/public/blog/nfc-misconceptions/index.html
index e75f397..6483052 100644
--- a/public/blog/nfc-misconceptions/index.html
+++ b/public/blog/nfc-misconceptions/index.html
@@ -1 +1 @@
-Misconceptions about NFC Misconceptions about NFC
2024-01-19Alert
I made a mistake while writing this blog post - somehow forgetting that security isn't unambiguous. You can actually skim NFC chips from a certain distance (having a limited distance is still an important factor though!), and though I think some of what I said below still applies you're better off ignoring it all.
There are, of course, a whole range of problems with skimming NFC chips from a distance so my point - don't be so worried - would still stand.
Either way, I recommend you take this with a grain of salt.
Introduction#
NFC (short for Near-Field Communication) is the set of communication protocols which allow for near-field communication between two electronic devices. One of the most prominent uses of this technology are contactless transactions - this includes services like Google and Apple Pay as well as all of your contactless-enabled cards.
It's been a while since my last blog past, but this one will be brief too - I'm writing here for the sake of clearing up some misconceptions people have about NFC.
The Misconceptions#
Inspiration#
While talking with a friend on a WhatsApp group chat a few days ago about a program I found on my jailbroken iOS device - Aemulo - I was informed of 'subway skimmers'; devices that could supposedly read data from contactless-enabled devices (via NFC) and would be able to emulate them.
The idea behind the above example was that someone with malicious intent could place such a device in a public location and take their contactless devices for their malicious purposes. When I heard of this, my first thought was: hoax, and I think that it was rightfully so.
What exactly is wrong with this?#
Several things. I'm no expert in cybersecurity - everyone's a student in some way, but I was sure that NFC was, as it's name implies, for near-field communication. I'm repeating myself here, but that's kind of the point. Various reliable resources, including Wikipedia, show that NFC has a maximum range of only a few centimetres - which makes sense, no?
And yet, whatever source my friend had for 'subway skimmers' gave the impression, or otherwise stated, that it would work within a radius of a few feet, which is just impossible. Upon voicing my doubts, I was then told that 'with a powerful enough antenna, it's possible'. Hoaxes sure are convincing, aren't they? Unfortunately, I am not able to find the source of my friend's misinformation.
See, NFC only works within a few centimetres anyways. Even if it could magically work within a radius of a few feet, you've got to take in the electromagnetic interference that the clothes and wallets people have would bring to any malicious device. The point of electromagnetic interference is especially true over a huge area of a few feet (relatively), where you've got several NFC-enabled devices.
Where it's actually an issue#
Of course, that isn't to say there aren't any issues with NFC and malicious readers - I'm just saying that the word getting around is horribly unrealistic. For example, a realistic example of a malicious NFC reader would be one placed on the card slots in cash machines - you get:
- The short range (< ~20 cm)
- Only one device
- Lots of devices to read!
And so, you've got someone so much more realistic that poses an actual threat!
Conclusion#
The information above, which I deem accurate, is there. What I suggest be taken away from this is pretty much the same as what is was for my blog post on hoaxes - do some fact-checking!
Misconceptions about NFC Misconceptions about NFC
2024-01-19Alert
I made a mistake while writing this blog post - somehow forgetting that security isn't unambiguous. You can actually skim NFC chips from a certain distance (having a limited distance is still an important factor though!), and though I think some of what I said below still applies you're better off ignoring it all.
There are, of course, a whole range of problems with skimming NFC chips from a distance so my point - don't be so worried - would still stand.
Either way, I recommend you take this with a grain of salt.
Introduction#
NFC (short for Near-Field Communication) is the set of communication protocols which allow for near-field communication between two electronic devices. One of the most prominent uses of this technology are contactless transactions - this includes services like Google and Apple Pay as well as all of your contactless-enabled cards.
It's been a while since my last blog past, but this one will be brief too - I'm writing here for the sake of clearing up some misconceptions people have about NFC.
The Misconceptions#
Inspiration#
While talking with a friend on a WhatsApp group chat a few days ago about a program I found on my jailbroken iOS device - Aemulo - I was informed of 'subway skimmers'; devices that could supposedly read data from contactless-enabled devices (via NFC) and would be able to emulate them.
The idea behind the above example was that someone with malicious intent could place such a device in a public location and take their contactless devices for their malicious purposes. When I heard of this, my first thought was: hoax, and I think that it was rightfully so.
What exactly is wrong with this?#
Several things. I'm no expert in cybersecurity - everyone's a student in some way, but I was sure that NFC was, as it's name implies, for near-field communication. I'm repeating myself here, but that's kind of the point. Various reliable resources, including Wikipedia, show that NFC has a maximum range of only a few centimetres - which makes sense, no?
And yet, whatever source my friend had for 'subway skimmers' gave the impression, or otherwise stated, that it would work within a radius of a few feet, which is just impossible. Upon voicing my doubts, I was then told that 'with a powerful enough antenna, it's possible'. Hoaxes sure are convincing, aren't they? Unfortunately, I am not able to find the source of my friend's misinformation.
See, NFC only works within a few centimetres anyways. Even if it could magically work within a radius of a few feet, you've got to take in the electromagnetic interference that the clothes and wallets people have would bring to any malicious device. The point of electromagnetic interference is especially true over a huge area of a few feet (relatively), where you've got several NFC-enabled devices.
Where it's actually an issue#
Of course, that isn't to say there aren't any issues with NFC and malicious readers - I'm just saying that the word getting around is horribly unrealistic. For example, a realistic example of a malicious NFC reader would be one placed on the card slots in cash machines - you get:
- The short range (< ~20 cm)
- Only one device
- Lots of devices to read!
And so, you've got someone so much more realistic that poses an actual threat!
Conclusion#
The information above, which I deem accurate, is there. What I suggest be taken away from this is pretty much the same as what is was for my blog post on hoaxes - do some fact-checking!
Host your own private search engine with SearXNG Host your own private search engine with SearXNG
2023-12-31Introduction#
SearXNG, put in its own words, is a 'free internet metasearch engine'. Note that it describes itself as a metasearch engine specifically - unlike your traditional search engine like Google or Bing, SearXNG does things a little bit differently: It aggregrates the results produced by search services like those aforementioned, and feeds them back to you.
Because of this key detail and a great deal of effort by those who've helped shape it, SearXNG protects your privacy, and does so very well:
- Private data from requests going to the search services it aggregrates results from is removed
- It does not forward anything to any third parties through search services
- Private data is also removed from requests going to the results pages
Furthermore, SearXNG can be configured to use Tor.
However, the aspect of privacy isn't the only great selling feature of the engine; from my use of the engine so far, it's also great at...searching (is that a surprise?). The fact that it's a metasearch engine plays a key role in this, as it provides SearXNG the ability to pull content more efficiently and gives you the ability to further tailor your experience.
Setting up SearXNG#
Installing the service#
As you may have expected if you've used NixOS for a while, searxng is packaged and has a service on NixOS. This makes setting it up just that much easier.
To get started, place somewhere in your system config the following:
{
+Host your own private search engine with SearXNG Host your own private search engine with SearXNG
2023-12-31Introduction#
SearXNG, put in its own words, is a 'free internet metasearch engine'. Note that it describes itself as a metasearch engine specifically - unlike your traditional search engine like Google or Bing, SearXNG does things a little bit differently: It aggregrates the results produced by search services like those aforementioned, and feeds them back to you.
Because of this key detail and a great deal of effort by those who've helped shape it, SearXNG protects your privacy, and does so very well:
- Private data from requests going to the search services it aggregrates results from is removed
- It does not forward anything to any third parties through search services
- Private data is also removed from requests going to the results pages
Furthermore, SearXNG can be configured to use Tor.
However, the aspect of privacy isn't the only great selling feature of the engine; from my use of the engine so far, it's also great at...searching (is that a surprise?). The fact that it's a metasearch engine plays a key role in this, as it provides SearXNG the ability to pull content more efficiently and gives you the ability to further tailor your experience.
Setting up SearXNG#
Installing the service#
As you may have expected if you've used NixOS for a while, searxng is packaged and has a service on NixOS. This makes setting it up just that much easier.
To get started, place somewhere in your system config the following:
{
# ...
services.searx = {
enable = true;
@@ -13,7 +13,7 @@
};
# ...
}
-
The snippet above starts the searx systemd service for listening on port 8888, and assumes a base_url of https://search.devraza.duckdns.org.
Now that we've got the actual searx instance running, we can now set up a reverse proxy allowing the service to be accessed remotely (whether this is within your local network or across the internet is up to you).
Setting up a reverse proxy#
What is a reverse proxy?#
Before I get started with the technical details of setting this up, I'd like to briefly clarify what a reverse proxy exactly is (to my understanding).
Let's get the wikipedia definition of reverse proxy out of the way first:
[...] a reverse proxy is an application that sits in front of back-end applications and forwards client requests to those applications. [...]
However, you might be confused as to what this actually means; I'll give an example of the usage of reverse proxies to better explain this:
- Suppose you've got a few services running on a server (for demonstration purposes, let's name these
x, y and z), each running on their own unique port. - Assuming you had a domain, and wanted to access all of these services from their own unique sub-domains (e.g.
x.yourdomain.com, y.yourdomain.com and z.yourdomain.com), you would have to use a reverse proxy. - This reverse proxy would take in requests from clients going to sub-domains, and forward these requests to the appropriate port on your machine for the service being requested.
The concept should be clear now, if it wasn't already.
Using NGINX to set up the reverse proxy#
NGINX is a popular web server that supports the creation of virtual hosts and the usage of reverse proxies. To accomodate our searx instance, we append the following to our NixOS server configuration:
1 {
+The snippet above starts the searx systemd service for listening on port 8888, and assumes a base_url of https://search.devraza.duckdns.org.
Now that we've got the actual searx instance running, we can now set up a reverse proxy allowing the service to be accessed remotely (whether this is within your local network or across the internet is up to you).
Setting up a reverse proxy#
What is a reverse proxy?#
Before I get started with the technical details of setting this up, I'd like to briefly clarify what a reverse proxy exactly is (to my understanding).
Let's get the wikipedia definition of reverse proxy out of the way first:
[...] a reverse proxy is an application that sits in front of back-end applications and forwards client requests to those applications. [...]
However, you might be confused as to what this actually means; I'll give an example of the usage of reverse proxies to better explain this:
- Suppose you've got a few services running on a server (for demonstration purposes, let's name these
x, y and z), each running on their own unique port. - Assuming you had a domain, and wanted to access all of these services from their own unique sub-domains (e.g.
x.yourdomain.com, y.yourdomain.com and z.yourdomain.com), you would have to use a reverse proxy. - This reverse proxy would take in requests from clients going to sub-domains, and forward these requests to the appropriate port on your machine for the service being requested.
The concept should be clear now, if it wasn't already.
Using NGINX to set up the reverse proxy#
NGINX is a popular web server that supports the creation of virtual hosts and the usage of reverse proxies. To accomodate our searx instance, we append the following to our NixOS server configuration:
1 {
2 # ...
3 services.nginx = {
4 enable = true;
@@ -24,7 +24,7 @@
9 serverName = "search.yourdomain.com"; # replace this with whatever you're serving from
10 # SearX proxy
11 locations."/" = {
- 12 proxyPass = "http://${toString config.services.searx.settings.server.bind_address}:${toString config.services.searx.settings.server.port}";
+12 proxyPass = "http://${toString config.services.searx.settings.server.bind_address}:${toString config.services.searx.settings.server.port}";
13 proxyWebsockets = true;
14 recommendedProxySettings = true;
15 };
diff --git a/public/blog/selfhost-tailscale/index.html b/public/blog/selfhost-tailscale/index.html
index 1d40862..5c34b83 100644
--- a/public/blog/selfhost-tailscale/index.html
+++ b/public/blog/selfhost-tailscale/index.html
@@ -1,4 +1,4 @@
-Take control of tailscale with headscale Take control of tailscale with headscale
2024-01-10Tailscale#
Tailscale is a modern tunnel VPN service based on WireGuard® which provides a 'free' and secure means of communication between devices within a tailnet - a private network which Tailscale provides its users.
Essentially, it provides a private and secure way of accessing any of your devices, no matter where you are in the world - a personal WAN encompassing the entire world.
And on top of this, Tailscale is completely free and open-source! At least, on the surface...
Not FOSS? What do you mean?#
There's a quite popular saying within the free and open-source software community, which goes along the lines of:
If you aren't paying for the product, then you are the product.
Which makes perfect sense. It's the modern era so anything significant is powered by some form of modern technology, data is the new oil, and so on. In exchange for offering you 'free' services, companies collect and use your data; while there supposedly are laws in place preventing the inconcensual collection of data in most countries around the world, your personal data may still be traded unethically and inconsensually.
I personally am of the opinion that these laws are worth absolutely nothing if people aren't educated in how their data is being used, and what specifically is being collected. But I digress, and that's a blog post for another time.
I also think it's quite unfortunate that users of paid services still have their personal data collected in the unethical manner outlined above, despite the fact that they are paying for the service...
In the context of Tailscale: while their clients are all open-source, their control server - the thing that's managing and rerouting everything going through what they advertise as your 'secure' VPN, isn't. You've got no idea what this thing is doing with the traffic it recieves.
Headscale#
For every problem, there's probably a solution somewhere. And luckily for this one (which may or may not actually be a problem for you), we've got Headscale as our solution. Headscale's a self-hostable, open-source alternative to the Tailscale control server, and aims to 'provide self-hosters and hobbyists with an open-source server they can use for their projects and labs'.
Installing on NixOS#
Moving on to installing and setting up Headscale on NixOS.
# ...
+Take control of tailscale with headscale Take control of tailscale with headscale
2024-01-10Tailscale#
Tailscale is a modern tunnel VPN service based on WireGuard® which provides a 'free' and secure means of communication between devices within a tailnet - a private network which Tailscale provides its users.
Essentially, it provides a private and secure way of accessing any of your devices, no matter where you are in the world - a personal WAN encompassing the entire world.
And on top of this, Tailscale is completely free and open-source! At least, on the surface...
Not FOSS? What do you mean?#
There's a quite popular saying within the free and open-source software community, which goes along the lines of:
If you aren't paying for the product, then you are the product.
Which makes perfect sense. It's the modern era so anything significant is powered by some form of modern technology, data is the new oil, and so on. In exchange for offering you 'free' services, companies collect and use your data; while there supposedly are laws in place preventing the inconcensual collection of data in most countries around the world, your personal data may still be traded unethically and inconsensually.
I personally am of the opinion that these laws are worth absolutely nothing if people aren't educated in how their data is being used, and what specifically is being collected. But I digress, and that's a blog post for another time.
I also think it's quite unfortunate that users of paid services still have their personal data collected in the unethical manner outlined above, despite the fact that they are paying for the service...
In the context of Tailscale: while their clients are all open-source, their control server - the thing that's managing and rerouting everything going through what they advertise as your 'secure' VPN, isn't. You've got no idea what this thing is doing with the traffic it recieves.
Headscale#
For every problem, there's probably a solution somewhere. And luckily for this one (which may or may not actually be a problem for you), we've got Headscale as our solution. Headscale's a self-hostable, open-source alternative to the Tailscale control server, and aims to 'provide self-hosters and hobbyists with an open-source server they can use for their projects and labs'.
Installing on NixOS#
Moving on to installing and setting up Headscale on NixOS.
# ...
{
# ...
services.headscale = {
@@ -13,7 +13,7 @@
};
# ...
}
-
This starts up the headscale systemd service on our host machine at port 7070. After that, we make Headscale available over the clearnet with an NGINX reverse proxy, per the usual:
{
+
This starts up the headscale systemd service on our host machine at port 7070. After that, we make Headscale available over the clearnet with an NGINX reverse proxy, per the usual:
{
services.nginx = {
enable = true;
virtualHosts = {
diff --git a/public/blog/server-hardware-selection/index.html b/public/blog/server-hardware-selection/index.html
index 43781c4..3b47c7e 100644
--- a/public/blog/server-hardware-selection/index.html
+++ b/public/blog/server-hardware-selection/index.html
@@ -1 +1 @@
-Selecting hardware for a (home) server Selecting hardware for a (home) server
2024-01-31Introduction#
I see a lot of people worryingly mistaken about what a server needs (specifically, a home server). Some think that a bland and incredibly ignorant '20% budget for CPU, 30% for GPU, and the rest for the rest' plan for selecting hardware is good enough (at least, before choosing specific items) - you can't exactly be wrong when choosing hardware, but this is very, very far from right.
Requirements#
Server hardware needs to be low-power and resource-efficient - so as not to waste any money unnessarily, obviously. Your budget will strongly impact the specifications you can get your hands on, but I would think that even $200 is enough for a decent home server - depending on what you want to do with it. Keep in mind that you could always repurpose an old laptop or desktop lying around; it's cheap, and you get what may be a surprisingly decent machine.
Power consumption#
The difference between low peak and low idle power should be noted in particular. Running costs can get very high if you don't work to moderate power consumption, and probably wouldn't be something you would ignore when it comes to home servers.
Usage of the server#
Naturally, how a server will be used will affect pretty much everything about the hardware chosen for it. For example, if you're looking to stream games remotely, you'd go for a (perhaps powerful) dedicated GPU and would likely invest in some high-speed internet solution. As indicated by the above example of the GPU, you need to be very specific with what you choose - do you need a powerful GPU or do you not? After all, one of the last things you would want, ever, is money going to waste on something you don't need, or failing to buy something that meets your expectations.
Conclusion#
I only gave two points of interest when selecting a server - looking at the numbers alone, this might seem like hardly anything to consider at all. My reasons for this are:
- Power comumption is one factor that people often forego thinking about, and an extremely important one at that.
- Building on top of the previous point, you (probably) aren't stupid. Knowing (albeit at a very basic level) what to look out for should be enough.
- It would be extremely difficult for me, or anyone else for that matter, to provide a truly complete solution to everyone's needs for a home server.
Well, that's it. I wish you luck in selecting your hardware.
Selecting hardware for a (home) server Selecting hardware for a (home) server
2024-01-31Introduction#
I see a lot of people worryingly mistaken about what a server needs (specifically, a home server). Some think that a bland and incredibly ignorant '20% budget for CPU, 30% for GPU, and the rest for the rest' plan for selecting hardware is good enough (at least, before choosing specific items) - you can't exactly be wrong when choosing hardware, but this is very, very far from right.
Requirements#
Server hardware needs to be low-power and resource-efficient - so as not to waste any money unnessarily, obviously. Your budget will strongly impact the specifications you can get your hands on, but I would think that even $200 is enough for a decent home server - depending on what you want to do with it. Keep in mind that you could always repurpose an old laptop or desktop lying around; it's cheap, and you get what may be a surprisingly decent machine.
Power consumption#
The difference between low peak and low idle power should be noted in particular. Running costs can get very high if you don't work to moderate power consumption, and probably wouldn't be something you would ignore when it comes to home servers.
Usage of the server#
Naturally, how a server will be used will affect pretty much everything about the hardware chosen for it. For example, if you're looking to stream games remotely, you'd go for a (perhaps powerful) dedicated GPU and would likely invest in some high-speed internet solution. As indicated by the above example of the GPU, you need to be very specific with what you choose - do you need a powerful GPU or do you not? After all, one of the last things you would want, ever, is money going to waste on something you don't need, or failing to buy something that meets your expectations.
Conclusion#
I only gave two points of interest when selecting a server - looking at the numbers alone, this might seem like hardly anything to consider at all. My reasons for this are:
- Power comumption is one factor that people often forego thinking about, and an extremely important one at that.
- Building on top of the previous point, you (probably) aren't stupid. Knowing (albeit at a very basic level) what to look out for should be enough.
- It would be extremely difficult for me, or anyone else for that matter, to provide a truly complete solution to everyone's needs for a home server.
Well, that's it. I wish you luck in selecting your hardware.
Setting up Zola on NixOS Setting up Zola on NixOS
2023-12-29Introduction#
Zola is a static site generator (similarly to the infamous Hugo, which you may have already heard of) and is written in Rust. It also happens to be the framework that this site is built on!
This blog post is a guide on setting up the site engine on NixOS specifically.
Installation#
Installing the package#
zola is packaged in the nix package repository, so you just declaratively add the package to your configuration as usual: For the purposes of this guide, zola can be installed either as a system or user package.
- As a system package:
{ pkgs, ... }: {
+Setting up Zola on NixOS Setting up Zola on NixOS
2023-12-29Introduction#
Zola is a static site generator (similarly to the infamous Hugo, which you may have already heard of) and is written in Rust. It also happens to be the framework that this site is built on!
This blog post is a guide on setting up the site engine on NixOS specifically.
Installation#
Installing the package#
zola is packaged in the nix package repository, so you just declaratively add the package to your configuration as usual: For the purposes of this guide, zola can be installed either as a system or user package.
- As a system package:
{ pkgs, ... }: {
# ...
environment.systemPackages = with pkgs; [
zola # Append the package name to the list
];
# ...
}
-
- As a user package (with home-manager):
{ pkgs, ... }: {
+
- As a user package (with home-manager):
{ pkgs, ... }: {
# ...
home.packages = with pkgs; [
zola # Append the package name to the list
];
# ...
}
-
Now that zola itself is installed, we can move on setting up the pages it serves - continue reading...
Setting up a theme#
Zola actually has a section of its website showcasing several community-made themes which you can choose from to be the theme for your static site here.
Simply choose a theme that you like (demos are usually available for each theme listed) and follow its appropriate documentation to set it up - this site uses a version of the serene theme with my custom colours.
Custom themes
You can also make your own theme if that better suits you (I recommend giving the documentation a read if so).
Setting up NGINX#
After selecting a theme (or making your own) you should now have a directory somewhere on your server containing your static site. For the following snippet, we'll assume this is at /var/lib/blog.
NGINX is a popular webserver which we're going to use for the purposes of hosting and serving our site. To do so, append the following somewhere in your configuration:
# ...
+
Now that zola itself is installed, we can move on setting up the pages it serves - continue reading...
Setting up a theme#
Zola actually has a section of its website showcasing several community-made themes which you can choose from to be the theme for your static site here.
Simply choose a theme that you like (demos are usually available for each theme listed) and follow its appropriate documentation to set it up - this site uses a version of the serene theme with my custom colours.
Custom themes
You can also make your own theme if that better suits you (I recommend giving the documentation a read if so).
Setting up NGINX#
After selecting a theme (or making your own) you should now have a directory somewhere on your server containing your static site. For the following snippet, we'll assume this is at /var/lib/blog.
NGINX is a popular webserver which we're going to use for the purposes of hosting and serving our site. To do so, append the following somewhere in your configuration:
# ...
{
# ...
services.nginx = {
diff --git a/public/elasticlunr.min.js b/public/elasticlunr.min.js
new file mode 100644
index 0000000..79dad65
--- /dev/null
+++ b/public/elasticlunr.min.js
@@ -0,0 +1,10 @@
+/**
+ * elasticlunr - http://weixsong.github.io
+ * Lightweight full-text search engine in Javascript for browser search and offline search. - 0.9.6
+ *
+ * Copyright (C) 2017 Oliver Nightingale
+ * Copyright (C) 2017 Wei Song
+ * MIT Licensed
+ * @license
+ */
+!function(){function e(e){if(null===e||"object"!=typeof e)return e;var t=e.constructor();for(var n in e)e.hasOwnProperty(n)&&(t[n]=e[n]);return t}var t=function(e){var n=new t.Index;return n.pipeline.add(t.trimmer,t.stopWordFilter,t.stemmer),e&&e.call(n,n),n};t.version="0.9.5",lunr=t,t.utils={},t.utils.warn=function(e){return function(t){e.console&&console.warn&&console.warn(t)}}(this),t.utils.toString=function(e){return void 0===e||null===e?"":e.toString()},t.EventEmitter=function(){this.events={}},t.EventEmitter.prototype.addListener=function(){var e=Array.prototype.slice.call(arguments),t=e.pop(),n=e;if("function"!=typeof t)throw new TypeError("last argument must be a function");n.forEach(function(e){this.hasHandler(e)||(this.events[e]=[]),this.events[e].push(t)},this)},t.EventEmitter.prototype.removeListener=function(e,t){if(this.hasHandler(e)){var n=this.events[e].indexOf(t);-1!==n&&(this.events[e].splice(n,1),0==this.events[e].length&&delete this.events[e])}},t.EventEmitter.prototype.emit=function(e){if(this.hasHandler(e)){var t=Array.prototype.slice.call(arguments,1);this.events[e].forEach(function(e){e.apply(void 0,t)},this)}},t.EventEmitter.prototype.hasHandler=function(e){return e in this.events},t.tokenizer=function(e){if(!arguments.length||null===e||void 0===e)return[];if(Array.isArray(e)){var n=e.filter(function(e){return null===e||void 0===e?!1:!0});n=n.map(function(e){return t.utils.toString(e).toLowerCase()});var i=[];return n.forEach(function(e){var n=e.split(t.tokenizer.seperator);i=i.concat(n)},this),i}return e.toString().trim().toLowerCase().split(t.tokenizer.seperator)},t.tokenizer.defaultSeperator=/[\s\-]+/,t.tokenizer.seperator=t.tokenizer.defaultSeperator,t.tokenizer.setSeperator=function(e){null!==e&&void 0!==e&&"object"==typeof e&&(t.tokenizer.seperator=e)},t.tokenizer.resetSeperator=function(){t.tokenizer.seperator=t.tokenizer.defaultSeperator},t.tokenizer.getSeperator=function(){return t.tokenizer.seperator},t.Pipeline=function(){this._queue=[]},t.Pipeline.registeredFunctions={},t.Pipeline.registerFunction=function(e,n){n in t.Pipeline.registeredFunctions&&t.utils.warn("Overwriting existing registered function: "+n),e.label=n,t.Pipeline.registeredFunctions[n]=e},t.Pipeline.getRegisteredFunction=function(e){return e in t.Pipeline.registeredFunctions!=!0?null:t.Pipeline.registeredFunctions[e]},t.Pipeline.warnIfFunctionNotRegistered=function(e){var n=e.label&&e.label in this.registeredFunctions;n||t.utils.warn("Function is not registered with pipeline. This may cause problems when serialising the index.\n",e)},t.Pipeline.load=function(e){var n=new t.Pipeline;return e.forEach(function(e){var i=t.Pipeline.getRegisteredFunction(e);if(!i)throw new Error("Cannot load un-registered function: "+e);n.add(i)}),n},t.Pipeline.prototype.add=function(){var e=Array.prototype.slice.call(arguments);e.forEach(function(e){t.Pipeline.warnIfFunctionNotRegistered(e),this._queue.push(e)},this)},t.Pipeline.prototype.after=function(e,n){t.Pipeline.warnIfFunctionNotRegistered(n);var i=this._queue.indexOf(e);if(-1===i)throw new Error("Cannot find existingFn");this._queue.splice(i+1,0,n)},t.Pipeline.prototype.before=function(e,n){t.Pipeline.warnIfFunctionNotRegistered(n);var i=this._queue.indexOf(e);if(-1===i)throw new Error("Cannot find existingFn");this._queue.splice(i,0,n)},t.Pipeline.prototype.remove=function(e){var t=this._queue.indexOf(e);-1!==t&&this._queue.splice(t,1)},t.Pipeline.prototype.run=function(e){for(var t=[],n=e.length,i=this._queue.length,o=0;n>o;o++){for(var r=e[o],s=0;i>s&&(r=this._queue[s](r,o,e),void 0!==r&&null!==r);s++);void 0!==r&&null!==r&&t.push(r)}return t},t.Pipeline.prototype.reset=function(){this._queue=[]},t.Pipeline.prototype.get=function(){return this._queue},t.Pipeline.prototype.toJSON=function(){return this._queue.map(function(e){return t.Pipeline.warnIfFunctionNotRegistered(e),e.label})},t.Index=function(){this._fields=[],this._ref="id",this.pipeline=new t.Pipeline,this.documentStore=new t.DocumentStore,this.index={},this.eventEmitter=new t.EventEmitter,this._idfCache={},this.on("add","remove","update",function(){this._idfCache={}}.bind(this))},t.Index.prototype.on=function(){var e=Array.prototype.slice.call(arguments);return this.eventEmitter.addListener.apply(this.eventEmitter,e)},t.Index.prototype.off=function(e,t){return this.eventEmitter.removeListener(e,t)},t.Index.load=function(e){e.version!==t.version&&t.utils.warn("version mismatch: current "+t.version+" importing "+e.version);var n=new this;n._fields=e.fields,n._ref=e.ref,n.documentStore=t.DocumentStore.load(e.documentStore),n.pipeline=t.Pipeline.load(e.pipeline),n.index={};for(var i in e.index)n.index[i]=t.InvertedIndex.load(e.index[i]);return n},t.Index.prototype.addField=function(e){return this._fields.push(e),this.index[e]=new t.InvertedIndex,this},t.Index.prototype.setRef=function(e){return this._ref=e,this},t.Index.prototype.saveDocument=function(e){return this.documentStore=new t.DocumentStore(e),this},t.Index.prototype.addDoc=function(e,n){if(e){var n=void 0===n?!0:n,i=e[this._ref];this.documentStore.addDoc(i,e),this._fields.forEach(function(n){var o=this.pipeline.run(t.tokenizer(e[n]));this.documentStore.addFieldLength(i,n,o.length);var r={};o.forEach(function(e){e in r?r[e]+=1:r[e]=1},this);for(var s in r){var u=r[s];u=Math.sqrt(u),this.index[n].addToken(s,{ref:i,tf:u})}},this),n&&this.eventEmitter.emit("add",e,this)}},t.Index.prototype.removeDocByRef=function(e){if(e&&this.documentStore.isDocStored()!==!1&&this.documentStore.hasDoc(e)){var t=this.documentStore.getDoc(e);this.removeDoc(t,!1)}},t.Index.prototype.removeDoc=function(e,n){if(e){var n=void 0===n?!0:n,i=e[this._ref];this.documentStore.hasDoc(i)&&(this.documentStore.removeDoc(i),this._fields.forEach(function(n){var o=this.pipeline.run(t.tokenizer(e[n]));o.forEach(function(e){this.index[n].removeToken(e,i)},this)},this),n&&this.eventEmitter.emit("remove",e,this))}},t.Index.prototype.updateDoc=function(e,t){var t=void 0===t?!0:t;this.removeDocByRef(e[this._ref],!1),this.addDoc(e,!1),t&&this.eventEmitter.emit("update",e,this)},t.Index.prototype.idf=function(e,t){var n="@"+t+"/"+e;if(Object.prototype.hasOwnProperty.call(this._idfCache,n))return this._idfCache[n];var i=this.index[t].getDocFreq(e),o=1+Math.log(this.documentStore.length/(i+1));return this._idfCache[n]=o,o},t.Index.prototype.getFields=function(){return this._fields.slice()},t.Index.prototype.search=function(e,n){if(!e)return[];e="string"==typeof e?{any:e}:JSON.parse(JSON.stringify(e));var i=null;null!=n&&(i=JSON.stringify(n));for(var o=new t.Configuration(i,this.getFields()).get(),r={},s=Object.keys(e),u=0;u0&&t.push(e);for(var i in n)"docs"!==i&&"df"!==i&&this.expandToken(e+i,t,n[i]);return t},t.InvertedIndex.prototype.toJSON=function(){return{root:this.root}},t.Configuration=function(e,n){var e=e||"";if(void 0==n||null==n)throw new Error("fields should not be null");this.config={};var i;try{i=JSON.parse(e),this.buildUserConfig(i,n)}catch(o){t.utils.warn("user configuration parse failed, will use default configuration"),this.buildDefaultConfig(n)}},t.Configuration.prototype.buildDefaultConfig=function(e){this.reset(),e.forEach(function(e){this.config[e]={boost:1,bool:"OR",expand:!1}},this)},t.Configuration.prototype.buildUserConfig=function(e,n){var i="OR",o=!1;if(this.reset(),"bool"in e&&(i=e.bool||i),"expand"in e&&(o=e.expand||o),"fields"in e)for(var r in e.fields)if(n.indexOf(r)>-1){var s=e.fields[r],u=o;void 0!=s.expand&&(u=s.expand),this.config[r]={boost:s.boost||0===s.boost?s.boost:1,bool:s.bool||i,expand:u}}else t.utils.warn("field name in user configuration not found in index instance fields");else this.addAllFields2UserConfig(i,o,n)},t.Configuration.prototype.addAllFields2UserConfig=function(e,t,n){n.forEach(function(n){this.config[n]={boost:1,bool:e,expand:t}},this)},t.Configuration.prototype.get=function(){return this.config},t.Configuration.prototype.reset=function(){this.config={}},lunr.SortedSet=function(){this.length=0,this.elements=[]},lunr.SortedSet.load=function(e){var t=new this;return t.elements=e,t.length=e.length,t},lunr.SortedSet.prototype.add=function(){var e,t;for(e=0;e1;){if(r===e)return o;e>r&&(t=o),r>e&&(n=o),i=n-t,o=t+Math.floor(i/2),r=this.elements[o]}return r===e?o:-1},lunr.SortedSet.prototype.locationFor=function(e){for(var t=0,n=this.elements.length,i=n-t,o=t+Math.floor(i/2),r=this.elements[o];i>1;)e>r&&(t=o),r>e&&(n=o),i=n-t,o=t+Math.floor(i/2),r=this.elements[o];return r>e?o:e>r?o+1:void 0},lunr.SortedSet.prototype.intersect=function(e){for(var t=new lunr.SortedSet,n=0,i=0,o=this.length,r=e.length,s=this.elements,u=e.elements;;){if(n>o-1||i>r-1)break;s[n]!==u[i]?s[n]u[i]&&i++:(t.add(s[n]),n++,i++)}return t},lunr.SortedSet.prototype.clone=function(){var e=new lunr.SortedSet;return e.elements=this.toArray(),e.length=e.elements.length,e},lunr.SortedSet.prototype.union=function(e){var t,n,i;this.length>=e.length?(t=this,n=e):(t=e,n=this),i=t.clone();for(var o=0,r=n.toArray();oDevraza 
Muhammad Nauman Raza@devrazaProgramming and cybersecurityI'm a programmer, entry-level cybersecurity specialist, system administrator, and aspiring graphic designer. NixOS is my operating system of choice, and radiant.nvim (my bespoke distribution of neovim) is my text editor of choice.
I also happen to be a devoted rustacean and a devout follower of the self-hosted way of life.
My skills in programming and scripting languages I've used so far are as follows:
- Advanced:
Python, Nix - Intermediate:
Rust, Go, E-Lisp - Beginner:
Julia, Lua
However, I consider myself able to work to a reasonable degree with any modern programming language.
Other tools that I can work with include git, linux, inkscape, and GIMP.
Devraza Muhammad Nauman Raza@devrazaProgramming and cybersecurity I'm a programmer, entry-level cybersecurity specialist, system administrator, and aspiring graphic designer. NixOS is my operating system of choice, and radiant.nvim (my bespoke distribution of neovim) is my text editor of choice.
I also happen to be a devoted rustacean and a devout follower of the self-hosted way of life.
My skills in programming and scripting languages I've used so far are as follows:
- Advanced:
Python, Nix - Intermediate:
Rust, Go, E-Lisp - Beginner:
Julia, Lua
However, I consider myself able to work to a reasonable degree with any modern programming language.
Other tools that I can work with include git, linux, inkscape, and GIMP.
Projects Catchtwo
A second generation, free Pokétwo autocatcher, made to stop people from wasting their money on 'premium' alternatives. [Deprecated]
Projects Catchtwo
A second generation, free Pokétwo autocatcher, made to stop people from wasting their money on 'premium' alternatives. [Deprecated]
https://devraza.giize.com/blog/adblock-blocky/
2024-05-31
+
+ https://devraza.giize.com/blog/btrfs-raid-setup/
+ 2024-12-30
+
https://devraza.giize.com/blog/hoaxes-overview/
2024-01-04
@@ -62,6 +66,9 @@
https://devraza.giize.com/tags/blocky/
+
+ https://devraza.giize.com/tags/btrfs/
+
https://devraza.giize.com/tags/hacking/
@@ -83,6 +90,9 @@
https://devraza.giize.com/tags/homelab/
+
+ https://devraza.giize.com/tags/nas/
+
https://devraza.giize.com/tags/nfc/
@@ -92,6 +102,18 @@
https://devraza.giize.com/tags/privacy/
+
+ https://devraza.giize.com/tags/raid/
+
+
+ https://devraza.giize.com/tags/raid0/
+
+
+ https://devraza.giize.com/tags/raid1/
+
+
+ https://devraza.giize.com/tags/raid10/
+
https://devraza.giize.com/tags/searxng/
diff --git a/public/tags/adblock/index.html b/public/tags/adblock/index.html
index 39c4a6f..eca2ece 100644
--- a/public/tags/adblock/index.html
+++ b/public/tags/adblock/index.html
@@ -1,3 +1,3 @@
Blog Posts Blog Posts Blog Posts Blog Posts Blog Posts Blog Posts Blog Posts Blog Posts # hardeningAll Tags
\ No newline at end of file
+en">Blog Posts # hardeningAll Tags
\ No newline at end of file
diff --git a/public/tags/hardware/index.html b/public/tags/hardware/index.html
index a181ce0..4329f3b 100644
--- a/public/tags/hardware/index.html
+++ b/public/tags/hardware/index.html
@@ -1,3 +1,3 @@
Blog Posts Blog Posts Blog Posts # headscaleAll Tags
\ No newline at end of file
+en">Blog Posts # headscaleAll Tags
\ No newline at end of file
diff --git a/public/tags/hoax/index.html b/public/tags/hoax/index.html
index becc14d..3bc2814 100644
--- a/public/tags/hoax/index.html
+++ b/public/tags/hoax/index.html
@@ -1,3 +1,3 @@
Blog Posts Blog Posts Blog Posts Blog Posts Blog Posts # homelabAll Tags
\ No newline at end of file
+en">Blog Posts # homelabAll Tags
\ No newline at end of file
diff --git a/public/tags/index.html b/public/tags/index.html
index c23f23d..6532e6e 100644
--- a/public/tags/index.html
+++ b/public/tags/index.html
@@ -1,3 +1,3 @@
Tags Tags
\ No newline at end of file
+en">Tags Tags
\ No newline at end of file
diff --git a/public/tags/nas/index.html b/public/tags/nas/index.html
new file mode 100644
index 0000000..4b0d99c
--- /dev/null
+++ b/public/tags/nas/index.html
@@ -0,0 +1,3 @@
+Blog Posts Blog Posts Blog Posts Blog Posts # nixosAll Tags
\ No newline at end of file
+en">Blog Posts # nixosAll Tags
\ No newline at end of file
diff --git a/public/tags/privacy/index.html b/public/tags/privacy/index.html
index a3c57de..69dce8b 100644
--- a/public/tags/privacy/index.html
+++ b/public/tags/privacy/index.html
@@ -1,3 +1,3 @@
Blog Posts # privacyAll Tags
\ No newline at end of file
+en">Blog Posts # privacyAll Tags
\ No newline at end of file
diff --git a/public/tags/raid/index.html b/public/tags/raid/index.html
new file mode 100644
index 0000000..f9d8b02
--- /dev/null
+++ b/public/tags/raid/index.html
@@ -0,0 +1,3 @@
+Blog Posts Blog Posts Blog Posts Blog Posts # RAID10All Tags
\ No newline at end of file
diff --git a/public/tags/searxng/index.html b/public/tags/searxng/index.html
index f4ed1aa..4e48455 100644
--- a/public/tags/searxng/index.html
+++ b/public/tags/searxng/index.html
@@ -1,3 +1,3 @@
Blog Posts Blog Posts Blog Posts # selfhostedAll Tags
\ No newline at end of file
+en">Blog Posts # selfhostedAll Tags
\ No newline at end of file
diff --git a/public/tags/social-engineering/index.html b/public/tags/social-engineering/index.html
index 7d2b504..a6c76bd 100644
--- a/public/tags/social-engineering/index.html
+++ b/public/tags/social-engineering/index.html
@@ -1,3 +1,3 @@
Blog Posts # social engineeringAll Tags
\ No newline at end of file
+en">Blog Posts # social engineeringAll Tags
\ No newline at end of file
diff --git a/public/tags/sysadmin/index.html b/public/tags/sysadmin/index.html
index 6892c08..51d65e3 100644
--- a/public/tags/sysadmin/index.html
+++ b/public/tags/sysadmin/index.html
@@ -1,3 +1,3 @@
Blog Posts Blog Posts Blog Posts # tailscaleAll Tags
\ No newline at end of file
+en">Blog Posts # tailscaleAll Tags
\ No newline at end of file
diff --git a/public/tags/zola/index.html b/public/tags/zola/index.html
index d37ab2e..077701d 100644
--- a/public/tags/zola/index.html
+++ b/public/tags/zola/index.html
@@ -1,3 +1,3 @@
Blog Posts Blog Posts