<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Luks on nagg.eu</title><link>https://nagg.eu/tags/luks/</link><description>Recent content in Luks on nagg.eu</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 14 Aug 2018 19:27:09 +0000</lastBuildDate><atom:link href="https://nagg.eu/tags/luks/index.xml" rel="self" type="application/rss+xml"/><item><title>LUKS2 the right way: Argon2</title><link>https://nagg.eu/luks2-the-right-way-argon2/</link><pubDate>Tue, 14 Aug 2018 19:27:09 +0000</pubDate><guid>https://nagg.eu/luks2-the-right-way-argon2/</guid><description>&lt;p&gt;Version 2 of cryptsetup got a few new fancy options, one of them is the ability to use &lt;!-- raw HTML omitted --&gt;Argon2&lt;!-- raw HTML omitted --&gt; as key derivation function.&lt;br&gt;
Creating a LUKS2 volume with Argon2 as hash function is very easy:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;sudo cryptsetup luksFormat -M luks2 --pbkdf argon2id -i 5000 /dev/sdb
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Please note that grub still does not support it, so it can&amp;rsquo;t be used for boot drives.&lt;br&gt;
Once the volume is created, to mount it run:&lt;/p&gt;</description></item><item><title>Fedora 18: TRIM and luks</title><link>https://nagg.eu/fedora-18-trim-and-luks/</link><pubDate>Fri, 01 Mar 2013 23:44:42 +0000</pubDate><guid>https://nagg.eu/fedora-18-trim-and-luks/</guid><description>&lt;p&gt;At a first glance enabling TRIM on a luks encrypted volume looks quite easy, and, as a matter of a fact it is.&lt;br&gt;
The shitstorm starts when trying to enable TRIM on the root volume, but, let&amp;rsquo;s go one step at a time.&lt;/p&gt;
&lt;p&gt;First of all, enabling trim on a regular not encrypted volume is pretty easy; just open the file &lt;code&gt;&amp;lt;em&amp;gt;/etc/fstab&amp;lt;/em&amp;gt;&lt;/code&gt; and add the flag &lt;code&gt;&amp;lt;em&amp;gt;discard&amp;lt;/em&amp;gt;&lt;/code&gt;.&lt;br&gt;
You may also want to add the flag &lt;code&gt;&amp;lt;em&amp;gt;noatime&amp;lt;/em&amp;gt;&lt;/code&gt; to prevent the OS from writing additional informations regarding last access date and such, it&amp;rsquo;s not strictly necessary but it will save the SSD&amp;rsquo;s cells some &lt;em&gt;useless&lt;/em&gt; write operations.&lt;br&gt;
The fstab file should look like this (here only one row is reported):&lt;/p&gt;</description></item></channel></rss>