1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL.TESTIN

  • defaults for cryptsetup

    From Bhasker C V@21:1/5 to All on Fri May 3 21:10:01 2024
    Hi all

    From cryptsetup 2:2.6.1-4~deb12u2 to 2:2.7.2-2 (on trixie) the defaults
    for cipher and hash have changed.
    I have used the previous version and it is difficult to type cypher and
    hash every time a dm-plain device is opened
    Is there a way to setup defaults in a config file - the only other option
    is to fall back to cryptsetup 2.6.1 to continue using my encrypted devices rather than typing out

    aes-cbc-essiv:sha256 or ripemd160

    every time.

    Thanks

    <div dir="ltr"><div>Hi all</div><div><br></div><div>From cryptsetup 2:2.6.1-4~deb12u2  to 2:2.7.2-2  (on trixie) the defaults for cipher and hash have changed. <br></div><div>I have used the previous version and it is difficult to type cypher and hash
    every time a dm-plain device is opened <br></div><div>Is there a way to setup defaults in a config file - the only other option is to fall back to cryptsetup 2.6.1 to continue using my encrypted devices rather than typing out <br><pre>aes-cbc-essiv:
    sha256 or ripemd160 <br><br></pre><pre><font face="arial,sans-serif">every time. <br><br></font></pre><pre><font face="arial,sans-serif">Thanks <br></font></pre></div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bhasker C V@21:1/5 to pabs@debian.org on Mon May 6 14:00:01 2024
    Thanks
    i resorted to writing a wrapper which is for now useful for me until i get
    a chance to re-create those new dm-plain crypt devices

    On Sun, May 5, 2024 at 7:34 AM Paul Wise <pabs@debian.org> wrote:

    On Fri, 2024-05-03 at 20:01 +0100, Bhasker C V wrote:

    From cryptsetup 2:2.6.1-4~deb12u2 to 2:2.7.2-2 (on trixie) the
    defaults for cipher and hash have changed.
    I have used the previous version and it is difficult to type cypher
    and hash every time a dm-plain device is opened
    Is there a way to setup defaults in a config file - the only other
    option is to fall back to cryptsetup 2.6.1 to continue using my
    encrypted devices rather than typing out
    aes-cbc-essiv:sha256 or ripemd160

    There are a few options for this:

    Create a new device using the new defaults, copy the data over and
    continue with the new defaults.

    Switch to a new device using LUKS, which stores the encryption type in
    a header that is stored on the disk, so you don't have to specify it.

    Store the settings in /etc/crypttab and rely on the default systemd
    crypttab conversion scripts starting and mounting the device.
    The crypttab manual page documents how to do this.

    Create a script containing the desired values and run it to setup
    devices instead of plain cryptsetup commands.

    Create the same using manually created systemd unit files.

    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise


    <div dir="ltr"><div>Thanks</div><div>i resorted to writing a wrapper which is for now useful for me until i get a chance to re-create those new dm-plain crypt devices<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun,
    May 5, 2024 at 7:34 AM Paul Wise &lt;<a href="mailto:pabs@debian.org">pabs@debian.org</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, 2024-05-03 at
    20:01 +0100, Bhasker C V wrote:<br>

    &gt; From cryptsetup 2:2.6.1-4~deb12u2  to 2:2.7.2-2  (on trixie) the<br> &gt; defaults for cipher and hash have changed. <br>
    &gt; I have used the previous version and it is difficult to type cypher<br> &gt; and hash every time a dm-plain device is opened <br>
    &gt; Is there a way to setup defaults in a config file - the only other<br> &gt; option is to fall back to cryptsetup 2.6.1 to continue using my<br>
    &gt; encrypted devices rather than typing out <br>
    &gt; aes-cbc-essiv:sha256 or ripemd160 <br>

    There are a few options for this:<br>

    Create a new device using the new defaults, copy the data over and<br>
    continue with the new defaults.<br>

    Switch to a new device using LUKS, which stores the encryption type in<br>
    a header that is stored on the disk, so you don&#39;t have to specify it.<br>

    Store the settings in /etc/crypttab and rely on the default systemd<br> crypttab conversion scripts starting and mounting the device.<br>
    The crypttab manual page documents how to do this.<br>

    Create a script containing the desired values and run it to setup<br>
    devices instead of plain cryptsetup commands.<br>

    Create the same using manually created systemd unit files.<br>

    -- <br>
    bye,<br>
    pabs<br>

    <a href="https://wiki.debian.org/PaulWise" rel="noreferrer" target="_blank">https://wiki.debian.org/PaulWise</a><br>
    </blockquote></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)