home.social

#luks1 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #luks1, aggregated by home.social.

  1. This week has been full of major improvements to my setup across my . I now have:
    1. Significantly faster boot times due to quicker decryption by separating out and into separate volumes.
    2. Upgrade from to (while most of the rest of my setup)
    3. Better visuals for LUKS passphrase prompts using (finally)

    I couldn't have asked for more improvements in barely two days.

  2. This week has been full of major improvements to my #Linux setup across my #ThinkPads. I now have:
    1. Significantly faster boot times due to quicker #LUKS decryption by separating out #boot and #EFI into separate volumes.
    2. Upgrade from #LUKS1 to #LUKS2 (while most of the rest of my setup)
    3. Better visuals for LUKS passphrase prompts using (finally) #plymouth

    I couldn't have asked for more improvements in barely two days.

  3. This week has been full of major improvements to my #Linux setup across my #ThinkPads. I now have:
    1. Significantly faster boot times due to quicker #LUKS decryption by separating out #boot and #EFI into separate volumes.
    2. Upgrade from #LUKS1 to #LUKS2 (while most of the rest of my setup)
    3. Better visuals for LUKS passphrase prompts using (finally) #plymouth

    I couldn't have asked for more improvements in barely two days.

  4. This week has been full of major improvements to my #Linux setup across my #ThinkPads. I now have:
    1. Significantly faster boot times due to quicker #LUKS decryption by separating out #boot and #EFI into separate volumes.
    2. Upgrade from #LUKS1 to #LUKS2 (while most of the rest of my setup)
    3. Better visuals for LUKS passphrase prompts using (finally) #plymouth

    I couldn't have asked for more improvements in barely two days.

  5. This week has been full of major improvements to my #Linux setup across my #ThinkPads. I now have:
    1. Significantly faster boot times due to quicker #LUKS decryption by separating out #boot and #EFI into separate volumes.
    2. Upgrade from #LUKS1 to #LUKS2 (while most of the rest of my setup)
    3. Better visuals for LUKS passphrase prompts using (finally) #plymouth

    I couldn't have asked for more improvements in barely two days.

  6. @mjg59

    Thank you for sounding the alert!

    I identified a minor issue with your otherwise nice explanation: According to my sources (man cryptsetup, #rfc9106), all #argon2 varieties are memory-hard. RFC 9106 is even titled “Argon2 Memory-Hard Function for Password Hashing and Proof-of-Work Applications”.

    However, given that there are known attacks against #argon2i, it seems wise to use #argon2id instead. It is also what is recommended in the RFC.

    As a #QubesOS user, I just checked the state of affairs there:

    The cryptsetup that comes with QubesOS 3.x used #luks1, and those who did an in-place upgrade to 4.x still have that unless they converted to #luks2 manually (as detailed in the migration guide).

    The cryptsetup in QubesOS 4.x uses #luks2, but it still defaults to #argon2i unfortunately.