<div dir="ltr"><div>Hi Guilhem, how are you?</div><div><br></div><div>Well, your suggestion is good but I don't think it is an ideal way to solve this...</div><div><br></div><div>For tests purposes, I had installed the latest release of Ubuntu Desktop (16.04) and it don't have this "problem"... I think they managed to solve that by loading the keyboard module before the prompt of the cryptographic passphrase. I really want to help more but I'm not any good with these things in Linux, sorry... </div><div><br></div><div>Maybe you will need to talk to someone from Debian to define a better sequence for loading the modules at the boot time.</div><div><br></div><div>Could you test the Ubuntu 16.04 to see how it works?</div><div><br></div><div>Thank you for your response and sorry about the lack of more information about how to solve the issue...</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">2016-09-13 20:15 GMT-03:00 Guilhem Moulin <span dir="ltr"><<a href="mailto:guilhem@guilhem.org" target="_blank">guilhem@guilhem.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Andre,<br>
<br>
On Sat, 16 Jul 2016 at 15:02:40 -0300, Andre wrote:<br>
> During the installation process of setting up my operating system, I<br>
> chose as the default keyboard layout the Portuguese (Brazilian), then<br>
> set up the encryption of disk volumes and then set an encryption<br>
> password using accented characters.<br>
<br>
FWIW, this what the cryptsetup(8) manpage says about this:<br>
<br>
Character encoding: If you enter a passphrase with special symbols,<br>
the passphrase can change depending character encoding. Keyboard<br>
settings can also change, which can make blind input hard or<br>
impossible. For example, switching from some ASCII 8-bit variant to<br>
UTF-8 can lead to a different binary encoding and hence different<br>
passphrase seen by cryptsetup, even if what you see on the terminal<br>
is exactly the same. It is therefore highly recommended to select<br>
passphrase characters only from 7-bit ASCII, as the encoding for<br>
7-bit ASCII stays the same for all ASCII variants and UTF-8.<br>
<br>
Perhaps we should make the installer print a warning if the user enters<br>
non 7-bit ASCII characters?<br>
<br>
Cheers,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Guilhem.<br>
</font></span></blockquote></div><br></div></div>