<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dzu's Blog (Einträge über security)</title><link>https://blog.lazy-evaluation.net/</link><description></description><atom:link href="https://blog.lazy-evaluation.net/de/categories/security.xml" rel="self" type="application/rss+xml"></atom:link><language>de</language><copyright>Contents © 2025 &lt;a href="mailto:dzu@member.fsf.org"&gt;Detlev Zundel&lt;/a&gt; </copyright><lastBuildDate>Wed, 10 Dec 2025 16:11:11 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Using SoloKey2 under GNU/Linux</title><link>https://blog.lazy-evaluation.net/de/posts/linux/solokey2-gnu-linux.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;div id="org3f9fb72" class="figure"&gt;
&lt;p&gt;&lt;img src="https://blog.lazy-evaluation.net/de/images/giant-gd1d82756c_640.jpg" alt="giant-gd1d82756c_640.jpg" title="Big and Little" align="middle" width="150"&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;
As I used the &lt;a href="https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/i-mx-applications-processors/i-mx-8-processors/i-mx-8m-mini-arm-cortex-a53-cortex-m4-audio-voice-video:i.MX8MMINI"&gt;i.MX8M Mini&lt;/a&gt; SoC in previous blog posts, I decided to
explain the "magic" going on with the default boot settings in
U-Boot.  Understanding this gives us a solid foundation to efficiently
work with the eval board during early development.
&lt;/p&gt;

&lt;p&gt;
Of course it is also possible to reuse the framework for your own
embedded Linux project, so it is even more important to understand the
functional implications of it.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/solokey2-gnu-linux.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (2 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/solokey2-gnu-linux.html</guid><pubDate>Tue, 01 Apr 2025 09:01:30 GMT</pubDate></item><item><title>checksec</title><link>https://blog.lazy-evaluation.net/de/posts/linux/checksec.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;p&gt;It is not a coincidence that the first post in this still young year
is about security.  Since I realized last year how far the current
internet with its "data capitalism" has strayed from its beginnings, I
did a lot of reading to understand the situation in more detail.
&lt;a class="reference external" href="https://www.schneier.com/books/data_and_goliath/"&gt;Data and Goliath&lt;/a&gt;
by the renowned security expert Bruce Schneier was a depressing eye
opener and I am currently still reading his new book &lt;a class="reference external" href="https://www.schneier.com/books/click_here/"&gt;Click Here to
Kill Everybody&lt;/a&gt; which
reiterates the problems in light of more recent events.  If you are
looking for more in depth information from somebody with a long track
record, I can strongly recommend those books as a starting point.&lt;/p&gt;
&lt;img alt="Linux Security" class="align-center" src="https://blog.lazy-evaluation.net/images/Linux-Security.jpg" style="width: 250px;"&gt;
&lt;p&gt;One of the lessons I recently learned is that real security is
extremely hard to achieve - even by the best in the field.  It is also
pretty much impossible for a non-specialist to evaluate the security
of any given solution without much more transparency into the security
design process (threat models) and the implementation methods used to
avoid them (protocols, etc.).&lt;/p&gt;
&lt;p&gt;The Linux kernel and the GNU tool chains on the other hand offer a
variety of hardening features to protect a GNU/Linux system from
certain vulnerabilities.  Having a tool to quickly evaluation which of
those methods are in effect on a given system would be a welcome tool
in the toolbox, especially when custom build systems are involved
rather than the well known distributions.&lt;/p&gt;
&lt;p&gt;The application security expert Tobias Klein provides a nice &lt;a class="reference external" href="http://www.trapkit.de/tools/checksec.html"&gt;shell
script&lt;/a&gt; to do exactly
that. As &lt;code class="docutils literal"&gt;checksec.sh&lt;/code&gt; only requires the Bourne Again Shell (bash), it is
immediately usable on pretty much every GNU/Linux system out there.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/checksec.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (2 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/checksec.html</guid><pubDate>Tue, 01 Jan 2019 23:48:31 GMT</pubDate></item><item><title>Switching to https with Let's Encrypt</title><link>https://blog.lazy-evaluation.net/de/posts/switching-to-https.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;p&gt;As you may have noticed, the blog is now being served as a secure,
encrypted page with the help of a fresh TLS certificate from &lt;a class="reference external" href="https://letsencrypt.org/"&gt;Let's Encrypt&lt;/a&gt;.&lt;/p&gt;
&lt;img alt="Let's Encrypt" class="align-center" src="https://blog.lazy-evaluation.net/images/letsencrypt-logo-horizontal.png"&gt;
&lt;p&gt;Ever since I first learned about this initiative supporting a more
secure and privacy-respecting web, I wanted to use such a certificate
for my blog.  The immediate enthusiasm was slowed by the realization
of the very short lifetime of the certificates and so the idea was
left dormant for a while.  With a validity of only three months, some
sort of scripting infrastructre is needed to ensure that the
certificates are renewed in a timely fashion and back then I didn't
see an easy solution ready in a few minutes.  Luckily enough, my web
space provider &lt;a class="reference external" href="https://www.hostsharing.net/"&gt;Hostsharing eG&lt;/a&gt;
integrated Let's Encrypt in a completely seamless fashion in the last
weeks.  All I needed to do was to tick the "Let's Encrypt Zertifikat"
option in the HSAdmin web interface, specify the valid sub-domains and
a few minutes later the website started serving the certificate.&lt;/p&gt;
&lt;p&gt;Admittedly it took a little longer to find out why Firefox kept
complaining about &lt;a class="reference external" href="https://support.mozilla.org/en-US/kb/mixed-content-blocking-firefox"&gt;blocking mixed content&lt;/a&gt;
on the TLS connection replacing the icons in the left hand panel by
empty rectangles.  Debugging the problem showed that the icons are in
fact individual "characters" in an off-site font referenced by my
chosen &lt;a class="reference external" href="https://getnikola.com/"&gt;Nikola&lt;/a&gt; theme.  Switching the
template HTML to load the fonts also over https finished the
transition.&lt;/p&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/switching-to-https.html</guid><pubDate>Sun, 22 Oct 2017 17:46:00 GMT</pubDate></item></channel></rss>