<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TwofishSL92 on Michael’s Domain</title><link>https://jeltsch.org/en/tags/twofishsl92/</link><description>Recent content in TwofishSL92 on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/twofishsl92/index.xml" rel="self" type="application/rss+xml"/><item><title>Mouting of encrypted partitions under SuSE 9.3 (losetup, cryptotab, twofish256, twofishSL92)</title><link>https://jeltsch.org/en/mouting_of_encrypted_partitions_under_suse_9_3_losetup_cryptotab_twofish256_twofishsl92/</link><pubDate>Wed, 04 Apr 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/mouting_of_encrypted_partitions_under_suse_9_3_losetup_cryptotab_twofish256_twofishsl92/</guid><description>&lt;p&gt;I have one encrypted partition that was created under SuSE 9.2. After a fresh install of 9.3 (not an update) the mounting of that partition during bootup failed. I could, however, still mount it manually later using another loopdevice. To fix this, I had to change the encryption algorithm in /etc/cryptotab from twofish256 to twofishSL92. 
 &lt;a href="http://suse-linux-faq.koehntopp.de/q/q-suse93-cryptofs.html" target="_blank" rel="noopener noreferrer nofollow"&gt;More detailed information&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
.&lt;/p&gt;</description></item></channel></rss>