<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on Spezialks Blog</title><link>https://spezialk-dev.github.io/post/</link><description>Recent content in Posts on Spezialks Blog</description><generator>Hugo</generator><language>en</language><copyright>2026</copyright><lastBuildDate>Sun, 19 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://spezialk-dev.github.io/post/index.xml" rel="self" type="application/rss+xml"/><item><title>Developing bootsecure</title><link>https://spezialk-dev.github.io/post/developing_bootsecure/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://spezialk-dev.github.io/post/developing_bootsecure/</guid><description>&lt;h1 id="introduction-to-bootsecure"&gt;Introduction to bootsecure&lt;/h1&gt;
&lt;p&gt;&lt;a href="https://github.com/SpezialK-dev/bootsecure"&gt;Bootsecure&lt;/a&gt; is a small rust application that runs on every system login for the user and detects if the computer has been used without logging in. And notifies the User if that has been the case.
This uses a feature of the UEFI Spec so it is relatively portable. I found this feature while working on my next blog post about UEFI variables. And I thought that this could make an interesting security application for people worried that their hardware is interacted with while they are away from it. Hence, I build this application.
Currently, It&amp;rsquo;s still quite new, so bugs can happen since it was build in a single weekend, so I am happy if people report bugs with it or contribute to improve this.&lt;/p&gt;</description></item><item><title>Disabling FN+4 under Lenovo</title><link>https://spezialk-dev.github.io/post/disabling-fn+4-lenovo/</link><pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate><guid>https://spezialk-dev.github.io/post/disabling-fn+4-lenovo/</guid><description>&lt;h1 id="my-problem"&gt;My Problem&lt;/h1&gt;
&lt;p&gt;Lenovo has this feature that allows you to press &lt;code&gt;FN+4&lt;/code&gt; to put your laptop to sleep. Though this clashes with the switching of the FN and the Ctrl key. Because it seems that there is a bug in the Lenovo Bios of my E14 G6, that when I switched the keys now both keys are recognized as FN only for the sleep shortcut. All Other FN behaviour works as expected.&lt;/p&gt;</description></item><item><title>Understanding Uefi Vars</title><link>https://spezialk-dev.github.io/post/understanding_uefi_vars/</link><pubDate>Sat, 07 Mar 2026 00:00:00 +0000</pubDate><guid>https://spezialk-dev.github.io/post/understanding_uefi_vars/</guid><description>&lt;h1 id="what-are-uefi-vars"&gt;What are UEFI Vars&lt;/h1&gt;
&lt;p&gt;UEFI vars are variables that are stored on your motherboard. They store things like boot options, SHIM settings, and other information that have to be independent of your hard drive.&lt;/p&gt;
&lt;p&gt;Under the Linux system they are mapped under &lt;code&gt;/sys/firmware/efi/efivars/&lt;/code&gt; using the EFI vars file system &lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;
&lt;p&gt;Under Windows there are some special permissions needed for an app to read them out&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt;. Though system calls exist to ask for specific variables &lt;sup id="fnref:3"&gt;&lt;a href="#fn:3" class="footnote-ref" role="doc-noteref"&gt;3&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;</description></item></channel></rss>