From: grumpy@mailfence.com
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup gui
Date: Sun, 3 May 2020 00:57:58 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.2005021756180.13797@tehzcl5.tehzcl-arg> (raw)
In-Reply-To: <20200501205944.GA9020@tansi.org>
On Fri, 1 May 2020, Arno Wagner wrote:
> On Fri, May 01, 2020 at 18:08:28 CEST, Michael Kj?rling wrote:
>> On 1 May 2020 15:44 +0200, from grumpy@mailfence.com:
>>> i don't know what i have screwed up
>>> i have an encrypted root fs
>>> while the system is still running the initial ramdisk it launches a cryptsetup gui
>>> it ask for the password and then presents 3 square dots
>>> this obscures the rest of the boot process
>>> can someone tell me how to disable this
>>> i don't know if this is part of dm-crypt or not
>>
>> That doesn't sound to me like anything that's part of cryptsetup, LUKS
>> or dm-crypt.
>>
>> It's more likely to be a distribution front-end to the tools that
>> unlock the LUKS container.
>>
>> I'd recommend that you look to see if this is a known issue with your
>> distribution and distribution version; if not, consider filing a bug
>> report with the distribution vendor.
>>
>
> I second that. Cryptsetup has no gui and it does not do encrypted
> root. You can do encrypted root with cryptsetup in an initrd
> and your distro seems to do that.
>
> If you want to change this process, you likely have to modify
> the initrd created or delivered by your distro. The cryptsetup
> FAQ has some help there in Section 9, but do not expect a detailed
> guide:
>
> https://gitlab.com/cryptsetup/cryptsetup/-/wikis/FrequentlyAskedQuestions#9-the-initrd-question
>
> Regards,
> Arno
i asked on the debian mailing list but got no response
thanks
prev parent reply other threads:[~2020-05-02 22:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 13:44 [dm-crypt] cryptsetup gui grumpy
2020-05-01 16:08 ` Michael Kjörling
2020-05-01 20:59 ` Arno Wagner
2020-05-02 22:57 ` grumpy [this message]
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=nycvar.QRO.7.76.2005021756180.13797@tehzcl5.tehzcl-arg \
--to=grumpy@mailfence.com \
--cc=dm-crypt@saout.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.