<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Decryption on nidomiro</title><link>https://nidomiro.de/tags/decryption/</link><description>Recent content in Decryption on nidomiro</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 14 Mar 2025 10:43:41 +0100</lastBuildDate><atom:link href="https://nidomiro.de/tags/decryption/index.xml" rel="self" type="application/rss+xml"/><item><title>Ubuntu: automatic password for second encrypted disk</title><link>https://nidomiro.de/2016/12/ubuntu-automatic-password-for-second-encrypted-disk/</link><pubDate>Thu, 15 Dec 2016 21:23:00 +0200</pubDate><guid>https://nidomiro.de/2016/12/ubuntu-automatic-password-for-second-encrypted-disk/</guid><description>&lt;p>I just encountered the problem that I have to type two passwords at
startup, for two encrypted disks. My first disk is encrypted through the
Ubuntu installer. After some searching I found the perfect solution for
that task. In german, it&amp;rsquo;s called
&lt;a href="https://wiki.ubuntuusers.de/LUKS/Schl%C3%BCsselableitung/#Bestehendes-LUKS-Geraet">&amp;ldquo;Schlüsselableitung&amp;rdquo;&lt;/a>,
in English derived keys. But perfect solutions often have a big issue
why they don’t work, like here. I’m using Ubuntu 16.04 which uses
´systemd´, and that has problems with derived keys. So I found the
second most perfect solution for me, using a key-file. Some people argue
that this is a security issue, but the derived key is also obtainable
with root rights, just like a key-file. And by the way, your private
keys of your certificates are also stored on that disks and nearly
nobody complains about that.&lt;/p></description></item></channel></rss>