[opensuse] Encryption password fail on install > internationalisation <
Hello Two problems related to security and internationalisation have arisen while attempting to install opensuse: one major, one merely obstructive. Both problems occur when setting the encryption password. 1. The major problem concerns the keyboard layout. The opensuse installer very helpfully asks which international keyboard layout it should use during install. It does this before asking for the user to set their passphrases. So the user gets to formulate their password in their chosen international keyboard layout - most likely the keyboard layout they are actually using: e.g. UK keyboard layout. But when install is complete, in my instance at least, the computer goes to a command screen and says, before prompting for the just given password to open the encrypted disk: "Note: only US keyboard layout is supported". The result is a failed install unless you happen to be in the US. Perhaps the problem has not occured in other countries where language differences have focused more attention on internationlisation? It is nigh on impossible to enter your encryption password using a US layout on a UK keyboard unless you use a password drawn from a limited and therefore less secure set of characters; and only then if you happen to know what characters are actually valid in both keyboard layouts, and where they are. I had a quick look. I'm not even sure it's actually possible to map characters chosen from a UK keyboard layout into a US keymap and then back onto a UK keyboard layout again without losing some. At least not for a regular person who is simply trying to put their password in at the prompt. Maybe not for anyone but Lou Gerstner himself. if this problem cannot be corrected, it would at least save the people time and frustration to tell them which characters are valid or not when they create their password, and to remove the offer of a non-US keyboard during install. I'm sure people would be happy not to choose invalid characters if they were told what they were. 2. The other problem is that the password itself recognises limited punctuation characters in whatever character set. Characters it does not recognise are recognised routinely by other password prompts. Some other password prompts fail to recognise characters that the opensuse password prompt does. Some password prompts have no limitations for a given standard keyboard layout. The result is that it becomes difficult to create a password system - i.e. a method for choosing complex passwords for different situations that can be remembered - because your system falls down as soon as you come across a password screen that disallows certain characters your system relies on. This actually happens pretty regularly. And the rules about what is a valid character or not seem always to be different. That doesn't make it right. If only the base system could assure no limitations. Hope this helps. mb. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 22/07/2014 22:14, Mark Ballard a écrit :
it right. If only the base system could assure no limitations.
it's current. One may also have to type his passwd on an other keyboard... so it's important to keep passwd on asci characters. I don't know how asian people do, for example, but if it's only between us and uk, the differences should not be that big, I'm french and know how to go from AZERTY to QUERTY jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-07-22 22:14, Mark Ballard wrote:
But when install is complete, in my instance at least, the computer goes to a command screen and says, before prompting for the just given password to open the encrypted disk: "Note: only US keyboard layout is supported".
Yes, you are absolutely right. It is a known bug, apparently unsolvable, or little interest in solving it. I think it is lack of different keyboard layout in grub2, but don't take my word on that. It could be plymouth.
The result is a failed install unless you happen to be in the US.
You can add more passwords to the encrypted filesystem. You could change temporarily the keyboard to the US one, and then type the same keys as on the UK one, which now will be different chars - no matter which. I'm unsure if you understand the idea? Then your password can be typed no matter what layout you have, and you just have to remember the one on the UK keyboard.
Perhaps the problem has not occured in other countries where language differences have focused more attention on internationlisation?
Actually, they are worse.
if this problem cannot be corrected, it would at least save the people time and frustration to tell them which characters are valid or not when they create their password, and to remove the offer of a non-US keyboard during install. I'm sure people would be happy not to choose invalid characters if they were told what they were.
True. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlPO0kEACgkQtTMYHG2NR9XDRgCePtACwMnU/aQhOXXtjBXssaHm f9AAmgNh4dzcg4ZOG0iPTvtvQxtAl0dN =3oCz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday, July 22, 2014 11:06:09 PM Carlos E. R. wrote:
On 2014-07-22 22:14, Mark Ballard wrote:
But when install is complete, in my instance at least, the computer goes to a command screen and says, before prompting for the just given password to open the encrypted disk: "Note: only US keyboard layout is supported".
Yes, you are absolutely right. It is a known bug, apparently unsolvable, or little interest in solving it.
It have been running from some time ago. Could be technical or branding related.
I think it is lack of different keyboard layout in grub2, but don't take my word on that. It could be plymouth.
I don't think is GRUB2 or Plymouth related (I prefer not going on speculation). So far I know, It happens on our distro.
The result is a failed install unless you happen to be in the US.
You can add more passwords to the encrypted filesystem. You could change temporarily the keyboard to the US one, and then type the same keys as on the UK one, which now will be different chars - no matter which. I'm unsure if you understand the idea?
Then your password can be typed no matter what layout you have, and you just have to remember the one on the UK keyboard.
Post install, You should add "your language layout" to make the switch to if desirable. If I can remember correctly, User Login will be able to access that Desktop session using the "preferred language layout". Root will need the "US language Layout" Warning: Root and Bash shell will need to use the "US layout" to accept the password. On this case, you need to remember switch the layout before shut the system down. If you forget to do that may be a funny time to access your HDD until remembering you are using the wrong layout.
Perhaps the problem has not occured in other countries where language differences have focused more attention on internationlisation?
Actually, they are worse.
+1
if this problem cannot be corrected, it would at least save the people time and frustration to tell them which characters are valid or not when they create their password, and to remove the offer of a non-US keyboard during install. I'm sure people would be happy not to choose invalid characters if they were told what they were.
True.
-- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Regards, R. Chung -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
If I can remember correctly, User Login will be able to access thatDesktop session using the "preferred language layout".
Ubuntu manages to accept its login passwords in the same format in which it created them.
On this case, you need to remember switch the layout before shut the system down.
If you can't login in the first place, you can't switch the layout before shutting down. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, July 23, 2014 08:23:23 AM Mark Ballard wrote:
If I can remember correctly, User Login will be able to access thatDesktop session using the "preferred language layout".
Ubuntu manages to accept its login passwords in the same format in which it created them.
On this case, you need to remember switch the layout before shut the system down.
If you can't login in the first place, you can't switch the layout before shutting down.
I did install several systems for users with different languages. They requested a very long 23 mixed characters and complex passwords to access its hard disk drive. Additional login on other languages than US English with 23 mixed characters passwords. Today, I went to one of my customers computer to check it and refresh my thoughts about this issue.The whole system displays another language different from US English except on HDD ( Hard Disk Drive ) to get access to (It shows English). The funny stuff here, It is able to use its NON-US English Keyboard and Non-US English Layout to get access to the HDD by using the very complex long password.The Login Interface is showing on Non-English and again it is able to work with Non-US English Keyboard Layout and the user get into Desktop Environment with preferred language.It includes the KWallet. The only case it needs to switch the keyboard to US English Keyboard Layout is to introduce Root password for administrative purposes. I know it is frustrating. I do ignore how difficult or why has been so difficult to fix it on this distro. Remember, every distro has its own challenges on different phases. There is no distro challenges free. And disregards the distro, I know, its developers have great challenges to deliver an usable experience without big hiccups (sometimes they need to negotiate with themselves to sacrifice features). I would not say it is comfortably to make a workaround. It just a workaround to make it work before full fix is to come. If time is available soon, I would like to help you more. In that case, I would try to buy another Hard Disk Drive and get the Hardware with similar conditions to annotate how I did this to work and make it available for you. Regards, R.Chung -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Content-ID: <alpine.LSU.2.11.1407231221351.32106@minas-tirith.valinor> El 2014-07-22 a las 18:39 -0500, Ricardo Chung escribió:
On Tuesday, July 22, 2014 11:06:09 PM Carlos E. R. wrote:
I think it is lack of different keyboard layout in grub2, but don't take my word on that. It could be plymouth.
I don't think is GRUB2 or Plymouth related (I prefer not going on speculation). So far I know, It happens on our distro.
The Bugzilla Andrey posted the link to, says that it is a problem with Plymouth. In fact, removing Plymouth kind of "solves" the issue. I first thought of grub because I know that grub in openSUSE also can not handle other keyboards. But I had my doubts, because the encryption password is handled after the kernel loads, not before. So the other obvious candidate was Plymouth - and I half remembered Andrey saying so ;-) - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlPPjhEACgkQja8UbcUWM1wcEwD9HlNtCiO4jXaXgdHCLP0lyw8d 2ArRqEcQIchPodl31bYBAIq9jGLITJ7tUeHR+PBwLGMjgX+97OcZInNpOad3Uz4x =Vzqx -----END PGP SIGNATURE-----
On Wed, Jul 23, 2014 at 2:27 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Content-ID: <alpine.LSU.2.11.1407231221351.32106@minas-tirith.valinor>
El 2014-07-22 a las 18:39 -0500, Ricardo Chung escribió:
On Tuesday, July 22, 2014 11:06:09 PM Carlos E. R. wrote:
I think it is lack of different keyboard layout in grub2, but don't take my word on that. It could be plymouth.
I don't think is GRUB2 or Plymouth related (I prefer not going on speculation). So far I know, It happens on our distro.
The Bugzilla Andrey posted the link to, says that it is a problem with Plymouth. In fact, removing Plymouth kind of "solves" the issue.
Not in this case. The bug I referred to was indeed triggered by using Plymouth, but it happened later. Removing plymouth would not fix problem of missing i18n support in mkinitrd. But solution suggested in this bug is to set up localization early in initrd. This means that local keyboard layout would be available early, when encrypted containers are configured. That's why I said "as side effect" :) Actually this bug includes mkinitrd script; anyone having this problem is welcome to test whether it helps (it may be run too late in which case we may need to adjust dependencies). As I mentioned, this problem should not exist with dracut. So it would be helpful if those who are concerned actually tested whether it is present in 13.2. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, July 23, 2014 12:27:29 PM Carlos E. R. wrote:
Content-ID: <alpine.LSU.2.11.1407231221351.32106@minas-tirith.valinor>
El 2014-07-22 a las 18:39 -0500, Ricardo Chung escribió:
On Tuesday, July 22, 2014 11:06:09 PM Carlos E. R. wrote:
I think it is lack of different keyboard layout in grub2, but don't take my word on that. It could be plymouth.
I don't think is GRUB2 or Plymouth related (I prefer not going on speculation). So far I know, It happens on our distro.
The Bugzilla Andrey posted the link to, says that it is a problem with Plymouth. In fact, removing Plymouth kind of "solves" the issue.
I do not think removing Plymouth really help on all cases or perhaps I missed something there. Sadly, I did not make annotations enough to go back on my steps to you. :-(
I first thought of grub because I know that grub in openSUSE also can not handle other keyboards. But I had my doubts, because the encryption password is handled after the kernel loads, not before. So the other obvious candidate was Plymouth - and I half remembered Andrey saying so ;-)
That's sound logic if it works so. Let me ask and apologies for my knowledge fault. Is it GRUB2 different for openSUSE from other distributions? Because I was able to make it work on 2 distro without KBd Layout switching.(Not ranting. Just want to kindly understand). Would it be transitional integration from old system packages to the new ones?
-- Cheers Carlos E. R.
(from 13.1 x86_64 "Bottle" (Minas Tirith)) Regards,
R.Chung -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Wed, 23 Jul 2014 11:46:03 -0500 Ricardo Chung <ricardo.a.chung@gmail.com> пишет:
On Wednesday, July 23, 2014 12:27:29 PM Carlos E. R. wrote:
Content-ID: <alpine.LSU.2.11.1407231221351.32106@minas-tirith.valinor>
El 2014-07-22 a las 18:39 -0500, Ricardo Chung escribió:
On Tuesday, July 22, 2014 11:06:09 PM Carlos E. R. wrote:
I think it is lack of different keyboard layout in grub2, but don't take my word on that. It could be plymouth.
I don't think is GRUB2 or Plymouth related (I prefer not going on speculation). So far I know, It happens on our distro.
The Bugzilla Andrey posted the link to, says that it is a problem with Plymouth. In fact, removing Plymouth kind of "solves" the issue.
I do not think removing Plymouth really help on all cases or perhaps I missed something there.
Sadly, I did not make annotations enough to go back on my steps to you. :-(
I first thought of grub because I know that grub in openSUSE also can not handle other keyboards. But I had my doubts, because the encryption password is handled after the kernel loads, not before. So the other obvious candidate was Plymouth - and I half remembered Andrey saying so ;-)
That's sound logic if it works so. Let me ask and apologies for my knowledge fault. Is it GRUB2 different for openSUSE from other distributions? Because I was able to make it work on 2 distro without KBd Layout switching.
Could you elaborate what "it" means in this sentence? I'm afraid I do not understand it.
(Not ranting. Just want to kindly understand). Would it be transitional integration from old system packages to the new ones?
-- Cheers Carlos E. R.
(from 13.1 x86_64 "Bottle" (Minas Tirith)) Regards,
R.Chung
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, July 23, 2014 09:02:36 PM Andrey Borzenkov wrote:
В Wed, 23 Jul 2014 11:46:03 -0500
Ricardo Chung <ricardo.a.chung@gmail.com> пишет:
On Wednesday, July 23, 2014 12:27:29 PM Carlos E. R. wrote:
Content-ID: <alpine.LSU.2.11.1407231221351.32106@minas-tirith.valinor>
El 2014-07-22 a las 18:39 -0500, Ricardo Chung escribió:
On Tuesday, July 22, 2014 11:06:09 PM Carlos E. R. wrote:
I think it is lack of different keyboard layout in grub2, but don't take my word on that. It could be plymouth.
I don't think is GRUB2 or Plymouth related (I prefer not going on speculation). So far I know, It happens on our distro.
The Bugzilla Andrey posted the link to, says that it is a problem with Plymouth. In fact, removing Plymouth kind of "solves" the issue.
I do not think removing Plymouth really help on all cases or perhaps I missed something there.
Sadly, I did not make annotations enough to go back on my steps to you. :-(
I first thought of grub because I know that grub in openSUSE also can not handle other keyboards. But I had my doubts, because the encryption password is handled after the kernel loads, not before. So the other obvious candidate was Plymouth - and I half remembered Andrey saying so ;-)
That's sound logic if it works so. Let me ask and apologies for my knowledge fault. Is it GRUB2 different for openSUSE from other distributions? Because I was able to make it work on 2 distro without KBd Layout switching. Could you elaborate what "it" means in this sentence? I'm afraid I do not understand it.
I will try to. Ubuntu and Fedora are able to handle the US English Keyboard Layout limitations to set a Full HDD Encryption with LVM. Both distros are able to use almost any Non-US English Keyboard Layout to gain access to the Encrypted Hard Disk Drive. Again, I am not complaining because I was able to make it work on openSUSE 13.1 with some twists on the process. My question would be. What is the limitation on our GRUB2 or whatever Application is handling this issue and preventing us to use any Non-US English Keyboard Layout? So far I able to confirm, openSUSE, Fedora and Ubuntu are using GRUB2. Is there a substantial differences to make work Non-US English Keyboard Layout on those distros? If I can recall, openSUSE supports plenty Languages for the user session. And fortunately, that's not the issue to solve. [...] Regards, R.Chung -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Wed, 23 Jul 2014 13:04:04 -0500 Ricardo Chung <ricardo.a.chung@gmail.com> пишет:
On Wednesday, July 23, 2014 09:02:36 PM Andrey Borzenkov wrote:
В Wed, 23 Jul 2014 11:46:03 -0500
Ricardo Chung <ricardo.a.chung@gmail.com> пишет:
On Wednesday, July 23, 2014 12:27:29 PM Carlos E. R. wrote:
Content-ID: <alpine.LSU.2.11.1407231221351.32106@minas-tirith.valinor>
El 2014-07-22 a las 18:39 -0500, Ricardo Chung escribió:
On Tuesday, July 22, 2014 11:06:09 PM Carlos E. R. wrote:
I think it is lack of different keyboard layout in grub2, but don't take my word on that. It could be plymouth.
I don't think is GRUB2 or Plymouth related (I prefer not going on speculation). So far I know, It happens on our distro.
The Bugzilla Andrey posted the link to, says that it is a problem with Plymouth. In fact, removing Plymouth kind of "solves" the issue.
I do not think removing Plymouth really help on all cases or perhaps I missed something there.
Sadly, I did not make annotations enough to go back on my steps to you. :-(
I first thought of grub because I know that grub in openSUSE also can not handle other keyboards. But I had my doubts, because the encryption password is handled after the kernel loads, not before. So the other obvious candidate was Plymouth - and I half remembered Andrey saying so ;-)
That's sound logic if it works so. Let me ask and apologies for my knowledge fault. Is it GRUB2 different for openSUSE from other distributions? Because I was able to make it work on 2 distro without KBd Layout switching. Could you elaborate what "it" means in this sentence? I'm afraid I do not understand it.
I will try to. Ubuntu and Fedora are able to handle the US English Keyboard Layout limitations to set a Full HDD Encryption with LVM. Both distros are able to use almost any Non-US English Keyboard Layout to gain access to the Encrypted Hard Disk Drive. Again, I am not complaining because I was able to make it work on openSUSE 13.1 with some twists on the process.
My question would be. What is the limitation on our GRUB2 or whatever Application is handling this issue and preventing us to use any Non-US English Keyboard Layout?
I already answered it. If you encrypt root, password for root is requested in initrd and mkinitrd does not support custom keyboard layouts. For non-root containers it should work, as password is requested after console is setup and keyboard layout is loaded.
So far I able to confirm, openSUSE, Fedora and Ubuntu are using GRUB2. Is there a substantial differences to make work Non-US English Keyboard Layout on those distros?
If I can recall, openSUSE supports plenty Languages for the user session. And fortunately, that's not the issue to solve.
[...]
Regards,
R.Chung
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2014-07-23 a las 11:46 -0500, Ricardo Chung escribió:
On Wednesday, July 23, 2014 12:27:29 PM Carlos E. R. wrote:
I first thought of grub because I know that grub in openSUSE also can not handle other keyboards. But I had my doubts, because the encryption password is handled after the kernel loads, not before. So the other obvious candidate was Plymouth - and I half remembered Andrey saying so ;-)
That's sound logic if it works so. Let me ask and apologies for my knowledge fault. Is it GRUB2 different for openSUSE from other distributions? Because I was able to make it work on 2 distro without KBd Layout switching.(Not ranting. Just want to kindly understand). Would it be transitional integration from old system packages to the new ones?
I don't know. I have problems when I have to edit something in grub prior to booting, like a path or kernel options, because keys like '/' or '-' change places. I don't have an encripted root partition, only data partitions; and I do have more problems when plymouth is active than not. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF0EAREIAAYFAlPQ5kMACgkQja8UbcUWM1xMGQD4t7fkFIcVv3QCnkVNjB0iQ1Dt 89TGLv6ZU0uubfv8OwD/XjoE9gV6fLwmziauD4SNUDnQfPMw1rL5ZsooM17seVo= =nn1Q -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Tue, 22 Jul 2014 23:06:09 +0200 "Carlos E. R." <carlos.e.r@opensuse.org> пишет:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-07-22 22:14, Mark Ballard wrote:
But when install is complete, in my instance at least, the computer goes to a command screen and says, before prompting for the just given password to open the encrypted disk: "Note: only US keyboard layout is supported".
Yes, you are absolutely right. It is a known bug, apparently unsolvable, or little interest in solving it.
I think it is lack of different keyboard layout in grub2, but don't take my word on that. It could be plymouth.
The original post is so vague that it is basically just rant, but it is likely prompt in initrd. /lib/mkinitrd/scripts/boot-luks.sh: echo "*** Note: only US keyboard layout is supported." In this case https://bugzilla.novell.com/show_bug.cgi?id=780516 may provide fix as side effect :) For 13.2 as I understand mkinitrd is being replaced by dracut which had i18n support from the very early stage so it should work there. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlPPH1gACgkQR6LMutpd94xSLACgni9NM9UvFPiXCdqiIjmglZbN K+IAoKOrCZQwQ2HZSXf+oanZW6G5OYrL =EwyW -----END PGP SIGNATURE-----
The original post is so vague that it is basically just rant,
The original post is actually quite specific but may appear otherwise to anyone with less than vague means of comprehension.
I think it is lack of different keyboard layout in grub2, but don't take my word on that. It could be plymouth.
I would guess the problem is Suse. Ubuntu did not have this problem. Clearly then, the problem can be solved quite simply. Even if Suse is unable to solve the problem itself, it can use the solution developed by Ubuntu.
In this case https://bugzilla.novell.com/show_bug.cgi?id=780516 may provide fix as side effect :)
Pleaes, spare us the pain. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Content-ID: <alpine.LSU.2.11.1407231212560.32106@minas-tirith.valinor> El 2014-07-23 a las 08:59 +0100, Mark Ballard escribió:
The original post is so vague that it is basically just rant,
The original post is actually quite specific but may appear otherwise to anyone with less than vague means of comprehension.
Please, try not to be confrontational, it doesn't help. Andrey happens to be the person I met more knowledgable about this particular problem, and also has been trying to find a solution for a long time. It is not that easy to solve.
itself, it can use the solution developed by Ubuntu.
I understand not. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlPPjGMACgkQja8UbcUWM1zeUwD9FAejPM80uOS2KSDM6TbiZD3U etNQJeiu9ESV4PFPnR0A/imN/LQoBpupA+Bbho9YEoCdWpc/lYRS5tsSYm4tSjm2 =fV0N -----END PGP SIGNATURE-----
The original post is so vague that it is basically just rant,
The original post is actually quite specific but may appear otherwise to anyone with less than vague means of comprehension.
Please, try not to be confrontational, it doesn't help.
I thought that was a fair riposte.
itself, it can use the solution developed by Ubuntu.
I understand not.
See Ricardo Chung's mail of 19:04. I was saying that I have found it is possible to use a complex password in Ubuntu without any problems. I suggested in all seriousness, though with come sarcasm, that since Ubuntu was open source, the solution might be easily replicated or at least advised. It is worth noting that Debian has the same problem. cheers mb.
- -- Cheers Carlos E. R.
(from 13.1 x86_64 "Bottle" (Minas Tirith))
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iF4EAREIAAYFAlPPjGMACgkQja8UbcUWM1zeUwD9FAejPM80uOS2KSDM6TbiZD3U etNQJeiu9ESV4PFPnR0A/imN/LQoBpupA+Bbho9YEoCdWpc/lYRS5tsSYm4tSjm2 =fV0N -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Jul 24, 2014 at 1:25 PM, Mark Ballard <markjballard@googlemail.com> wrote:
I suggested in all seriousness, though with come sarcasm, that since Ubuntu was open source, the solution might be easily replicated or at least advised.
Did you test mkinitrd script I suggested? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Excuse me, Andrey. I failed to see that you asked me to test a script. I could not get to the command line because my way was barred by a password prompt that didn't recognise my keyboard. I reinstalled opensuse using a simple password. As it happens, that install failed for another reason (Gnome environment failure on IBM X40 laptop). I shall try KDE. I have limited time. I must get this laptop up and running as soon as possible. But I can intentionally break the reinstall with a complex password if you need me to run a test. Is this test necessary, or is it more an admirable looking fix that I would nevertheless respectfully decline because it seems easier to me to add/delete complex/simple luks passwords after the install? On 24 July 2014 11:04, Andrey Borzenkov <arvidjaar@gmail.com> wrote:
On Thu, Jul 24, 2014 at 1:25 PM, Mark Ballard <markjballard@googlemail.com> wrote:
I suggested in all seriousness, though with come sarcasm, that since Ubuntu was open source, the solution might be easily replicated or at least advised.
Did you test mkinitrd script I suggested? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 2014-07-23 at 08:59 +0100, Mark Ballard wrote:
The original post is so vague that it is basically just rant,
The original post is actually quite specific but may appear otherwise to anyone with less than vague means of comprehension.
I think it is lack of different keyboard layout in grub2, but don't take my word on that. It could be plymouth.
I would guess the problem is Suse.
Ubuntu did not have this problem. Clearly then, the problem can be solved quite simply. Even if Suse is unable to solve the problem itself, it can use the solution developed by Ubuntu.
@work, we have systems with compressed,encrypted root (unfortunately ubuntu), and we were indeed confronted with users with complex luks-phrases that are used on various systems, most on US-international keyboards, some on azerty and even on keyboards with a obscure "dutch" layout. A college found a nice way to deal with that, at the grub-menu you can select different initrd-images that use different keyboard-layouts. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2014-07-24 a las 22:07 +0200, Hans Witvliet escribió:
@work, we have systems with compressed,encrypted root (unfortunately ubuntu),
Compressed? :-O How is that done? Is it read/write? - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlPRdccACgkQja8UbcUWM1x/aAD8DORPU+FsbZJZuwqnDr4IlhO2 KanijMG6X8PjRh4QpKUBAIMq+rw+tGTmrW+nkEDXdpbEHEJFNAsDhfci4muZhGBc =959W -----END PGP SIGNATURE-----
participants (7)
-
Andrey Borzenkov -
Carlos E. R. -
Carlos E. R. -
Hans Witvliet -
jdd -
Mark Ballard -
Ricardo Chung