Ok so it’s more of an annoyance than an issue but here it is.
I like openSUSE so much I have installed it on my main laptop, This laptop move’s around with me and contains personal information EG: Credit/Bank details etc, So I have opted for full disk encryption.
This however leads me to the following questions.
When I boot the laptop it asks for the passphrase as expected, However it only supports US keyboard layouts which means that " and @ are swapped, and as I use both of these in my passphrase it’s a bit annoying.
Is there anyway to fix this as once I get past that everything else is UK layout so I don’t understand why the encryption passphrase screen is US?
Is there anyway to change the screen that is presented when it asks for the encryption passphrase?, It’s ugly to say the least and a better background is desirable, Even a simple text input screen would be better.
I have used Full Disk Encryption (LUKS) as provided by the openSUSE installer to encrypt the entire hard drive
698GB encrypted disk comprising of the following partitions all encrypted as part of the encrypted block
2gb swap
30gb root
666gb home
When I boot the laptop I am required to enter the encryption password to unlock the hard drive, This is not a BIOS setting it is simply openSUSE asking for the key required to decrypt the hard drive.
On 2013-09-14 18:16, arvidjaar wrote:
>
> DaveMB;2584854 Wrote:
>> it only supports US keyboard layouts
>
> What is “it”? It is unclear whether you use BIOS provided facilities or
> something else.
The encryption password is by default asked by plymouth.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
> 2) Is there anyway to change the screen that is presented when it asks
> for the encryption passphrase?, It’s ugly to say the least and a better
> background is desirable, Even a simple text input screen would be
> better.
If you remove plymouth you get a text only boot screen, including the
password request. That is what I use, but… it goes like this (from
memory):
enter password
boot service name fine
boot service name2 fine
boot service name3 fine
boot service name4 fine
boot service name5 fine
And it stops; you have to guess that it is waiting for the password,
because there is no prompt. As you type, it displays asterisks, so it is
difficult to know what language the keyboard is in.
That prompt is presented by systemd, I believe.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Add “initrd” to the options column (perhaps replacing “none”) in “/etc/crypttab”. Then the prompting is handled by the “initrd” before systemd is started. The prompt is less confusing.
As for why plain ASCII is used – when done from the initrd, your language choices have not yet been configured and setup. When using an encrypted LVM, your language choice cannot be read until the root file system is decrypted.
Default is grub2. openSUSE installs whatever you told it. Why you make it so hard to get information?
Yes, 156mb
So not all partitions are encrypted at the end.
OK, so it is not grub prompt but indeed it comes from initrd for root partition and later from systemd-cryptsetup for anything else. For the first prompt indeed only US keyboard is possible - openSUSE mkinitrd does not support i18n. I have bug open for it for a long time. For the second prompt, it comes from plymouth indeed; of course you can change it, just create your own plymouth theme
On 2013-09-14 19:36, nrickert wrote:
>
> robin_listas;2584865 Wrote:
>> And it stops; you have to guess that it is waiting for the password,
>> because there is no prompt. As you type, it displays asterisks, so it
>> is
>> difficult to know what language the keyboard is in.
>>
>> That prompt is presented by systemd, I believe.
>
> Add “initrd” to the options column (perhaps replacing “none”) in
> “/etc/crypttab”. Then the prompting is handled by the “initrd” before
> systemd is started. The prompt is less confusing.
Interesting.
> As for why plain ASCII is used – when done from the initrd, your
> language choices have not yet been configured and setup. When using an
> encrypted LVM, your language choice cannot be read until the root file
> system is decrypted.
Ah… then maybe, if done from systemd, the proper keyboard is used. In that case, perhaps I’ll stay
with systemd. But I have to try your idea.
–
Cheers / Saludos,
Carlos E. R.
(from oS 12.3 “Dartmouth” GM (rescate 1))
On 2013-09-14 20:36, arvidjaar wrote:
>
> nrickert;2584869 Wrote:
>> When using an encrypted LVM, your language choice cannot be read until
>> the root file system is decrypted.
>
> Your default system choice can be added to initrd or passed on kernel
> command line. dracut supports both.
How? If you have a link, that’s fine
An example would be wonderful!
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Link for what? You can find suggested mkinitrd script to setup console in https://bugzilla.novell.com/show_bug.cgi?id=780516. And dracut is available for openSUSE, just install it, it comes with extensive manual page.
Oh ok, clearly I’ve offended your elite-ist mentality, I’m not making it hard to get information, I thought my post was pretty clear.
Obviously not, don’t worry I’ll refrain from asking anymore questions.
And the Linux community wonders why people run back to window’s, people Like you are the reason why.
We are not asking to irritate you we are asking so that we know the situation since we can not look over your shoulder. There are many ways these things can be done and it is needed that you give additional info so we can help.
> Oh ok, clearly I’ve offended your elite-ist mentality, I’m not making it
> hard to get information, I thought my post was pretty clear.
> Obviously not, don’t worry I’ll refrain from asking anymore questions.
Two things - first, please let’s stop making this personal, guys.
Second, please don’t give up because you had a bad experience in one
thread, Dave. We’re here to help, but sometimes we need more
information. If you don’t know how to obtain the information, please do
ask.
Arvidjaar - in future, please when someone says they don’t know, don’t go
on the offensive. Not everyone has the same experience that you or I do,
so provide information on how to find out rather than accusing them of
making it hard to get information.
USE default keys that are the same on both keyboards for password. Perhaps he uses a wrong approach to problem of password selection?
Is it possible, now questioner has set up his encryption disk for him to change password?I do not know answer to this.}
I think the user is starting from wrong place with his passwords selections. There is a commonality between USB keyboards and UK keyboards,
so choose passwords with symbols in same place on both keyboards, It is still a complex password with a lesser choice of common symbols,
but adequate for password selection.
On 2013-09-15 05:36, arvidjaar wrote:
>
> robin_listas;2584975 Wrote:
>> If you have a link, that’s fine
>
> Link for what? You can find suggested mkinitrd script to setup console
> in https://bugzilla.novell.com/show_bug.cgi?id=780516. And dracut is
> available for openSUSE, just install it, it comes with extensive manual
> page.
I understood you said that certain parameter given to mkinitrd or kernel
line so that the password prompt has my keyboard definition - not that I
have to install something different.
I simply asked for a link explaining the process in easy terms, or your
explanation.
The bugzilla is about fonts - fonts do not matter for the password, as
asterisks are displayed. And it is some kind of patch, not a parameter.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Oh, mkinitrd as distributed currently does not support it. dracut - which is alternative initrd implementation - does. You do not need anything special with dracut, it by default sets up default system locale in initrd (which includes fonts and keyboard) if called in local host mode. Or simply copies all available locale files and allow you to select your locale during boot.
The bugzilla is about fonts - fonts do not matter for the password, as
asterisks are displayed.
It does not matter. Suggested mkinitrd script sets up both font and keyboard layout.
And it is some kind of patch, not a parameter.
It is a mkinitrd script to setup default system keyboard layout and screen font in initrd.
I replied to the statement “initrd cannot know about system locale because root is not yet mounted”. That is not set in stone and can be implemented, just implementation is missing in openSUSE right now.
On 2013-09-15 16:06, arvidjaar wrote:
>
> robin_listas;2585091 Wrote:
>>
>> I understood you said that certain parameter given to mkinitrd or kernel
>> line so that the password prompt has my keyboard definition - not that I
>> have to install something different.
> Oh, mkinitrd as distributed currently does not support it. dracut -
> which is alternative initrd implementation - does. You do not need
> anything special with dracut, it by default sets up default system
> locale in initrd (which includes fonts and keyboard) if called in local
> host mode. Or simply copies all available locale files and allow you to
> select your locale during boot.
Oh, I see.
>> The bugzilla is about fonts - fonts do not matter for the password, as
>> asterisks are displayed.
> It does not matter. Suggested mkinitrd script sets up both font and
> keyboard layout.
>> And it is some kind of patch, not a parameter.
> It is a mkinitrd script to setup default system keyboard layout and
> screen font in initrd.
Ah.
> I replied to the statement “initrd cannot know about system locale
> because root is not yet mounted”. That is not set in stone and can be
> implemented, just implementation is missing in openSUSE right now.
Ah, but I did not say that
Thanks for the explanation. I’ll keep it mind for when I try full disk
encryption - I normally only encrypt data, not system.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
