public inbox for cryptsetup@lists.linux.dev
 help / color / mirror / Atom feed
From: "Kiss István" <keraform@gmail.com>
To: cryptsetup@lists.linux.dev
Subject: Issues with LUKS Password Management Options
Date: Fri, 11 Oct 2024 09:08:18 +0200	[thread overview]
Message-ID: <32be1215-bcab-425b-99cd-3adc26590b14@gmail.com> (raw)

Dear Developers,

I would like to bring to your attention an issue regarding the password 
management of LUKS-encrypted volumes. Currently, the LUKS password 
prompt offers three options for remembering the password, with the 
default setting being to remember the password until logout. However, I 
rarely turn off my computer, and I often keep it in standby mode for 
weeks. As a result, the LUKS-encrypted volume remains unlocked for 
extended periods, which is not ideal from a security perspective.

Every time, I have to manually ensure that the password is only stored 
temporarily (forgotten immediately), which can be inconvenient and is 
easy to overlook. I believe it would be helpful if users had the option 
to set "forget the password immediately" as the default behavior, 
perhaps through a simple checkbox, avoiding unnecessary compromises 
between convenience and security.

I would like to ask if such a change is planned for the future or if you 
have any suggestions on how this can be more efficiently handled with 
the current system configuration.

Thank you for your attention, and I look forward to your response.

Best regards,
     István Kiss


             reply	other threads:[~2024-10-11  7:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  7:08 Kiss István [this message]
2024-10-11  7:51 ` Issues with LUKS Password Management Options Michael Kjörling
2024-10-11  7:54 ` Ondrej Kozina
2024-10-11 14:01 ` iam.frightful278
2024-10-12  7:51   ` Arno Wagner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32be1215-bcab-425b-99cd-3adc26590b14@gmail.com \
    --to=keraform@gmail.com \
    --cc=cryptsetup@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox