Odd-I've tested this again and again on my own system. Reopen cryptdisks.functions from your machine in a text editor and make sure it is truly overwritten-a suprise there would be the first thing I would suspect.
If you are NOT able to unlock the encrypted partition, but DO see you text echoed on the console, you have a different problem. In my early experiments, I sometimes had trouble in Hardy with usplash corrupting the console and got the result you describe-but with characters shown not being the ones typed. Never saw this again with later versions of my own code for unknown reasons-and never saw it once in Jaunty.
BTW, it's the hardy version of Usplash I'm using for compatability with a customized splash screen, and I'm not getting either problem.
First, check your cryptdisks.functions. If the local changes aren't there, it didn't copy.
I've sometimes seen issues in Jaunty with renamed backup files being called as though they had not been renamed-seen it with xorg.conf backup files corrupting VESA displays. Try putting the text "BAK" before and after the backup file to see if this is happening.
Askpass should NOT be called so its bugs should not be an issue. You could rename askpass or move it, but then would be locked out if you have the 1.0.6 version of cryptdisks.functions.
In cryptsetup 2:1.0.5 , askpass and the fifo are not used and not present in /lib/cryptsetup at all.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.6 (GNU/Linux)
> Date: Fri, 10 Apr 2009 05:00:49 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 55159] Re: usplash prevents passwords from being not echoed on the console
>
> Luke : Thanks for your great work. Unfortunately I get a different
> result here. I overwrited my /lib/cryptsetup/cryptdisks.functions file
> by the one provided in your comment #30 and I'm still able to see my
> passphrase echoed in plain text on console if I switch to console before
> finishing typing my passphrase using the initial steps in the bug
> description.
>
> I tested this with a luks partition which is mounted in "/media" (not a
> root partition) and therefore which is unlocked by cryptsetup during
> init.d and not initramfs.
>
> Can you see something that could be missing in your current fix so it
> can apply to the configuration I described?
>
> --
> usplash prevents passwords from being not echoed on the console
> https://bugs.launchpad.net/bugs/55159
> You received this bug notification because you are a direct subscriber
> of the bug.
Odd-I've tested this again and again on my own system. Reopen cryptdisks. functions from your machine in a text editor and make sure it is truly overwritten-a suprise there would be the first thing I would suspect.
If you are NOT able to unlock the encrypted partition, but DO see you text echoed on the console, you have a different problem. In my early experiments, I sometimes had trouble in Hardy with usplash corrupting the console and got the result you describe-but with characters shown not being the ones typed. Never saw this again with later versions of my own code for unknown reasons-and never saw it once in Jaunty.
BTW, it's the hardy version of Usplash I'm using for compatability with a customized splash screen, and I'm not getting either problem.
First, check your cryptdisks. functions. If the local changes aren't there, it didn't copy.
I've sometimes seen issues in Jaunty with renamed backup files being called as though they had not been renamed-seen it with xorg.conf backup files corrupting VESA displays. Try putting the text "BAK" before and after the backup file to see if this is happening.
Askpass should NOT be called so its bugs should not be an issue. You could rename askpass or move it, but then would be locked out if you have the 1.0.6 version of cryptdisks. functions.
In cryptsetup 2:1.0.5 , askpass and the fifo are not used and not present in /lib/cryptsetup at all.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.6 (GNU/Linux)
mQGiBElz9bERBAD HbO/o4DHTv5tNDs 0N/QCL2nXKbLDMw LJatti6QtEDOB98 yNeW y4fZZLPBriYybxU udU5RCqKY64KK3P nc9oAMuYk5PxVO+ 7hrx K59Re3VTK6r6uBN gBfteST3jy/ XvuvXQSWi9408lC swCgnnGK URzWn6vcD/ 2lW4sEUFnCfVSFu TdP0/CSJQq4XUJs ys1thsm6W HfzmcqnYj9Tpi51 XMCvqpi1vb2awxE E4PZ2AtKgWXkqfJ Hzl1 Gdkf571f61cJhty WCmlTMu9TLd5Nil wwPtxMTrQSzA+ f1xlaH ypGmPr6buv1LYfa K3PMpwjAhxYvCKB sqjSk/KYiiliHyN IFnq NUHbKHmICToDaxb uTQdIKbBjMCAzf3 xLZCiRP3F3jPF66 QDO/ I5xbUGhDQu3ym84 2NbmsrGBoE4b75S +5DzLQbTHVrZSA8 bHVr pbC5jb20+ iGAEExECACAFAkl z9bECGyMGCwkIBw MCBBUCCAME KCRCrYZ03I1TDoo 14AKCapTyOXADsX tR9oAjvSwAbF/ zNIgCe 1alG38b4UHzu5AQ 0ESXP1tBAEALhyO 0p3hLYVywLkgUEI mo1M LSHtyCQWz6trl8W /hqz8dLdlYAM7Mx v681PJHCC4PEo9b YIdk mX7uvGgeZBH53md Uct0D7LUyDW/ mOxUp/yVy49LUhq O4YcNiA ouZTTAAMFA/ 45PsuZ12ZZdZSCj 0PH02ByN95qVzXY P7714eY2 kbKPAhmypHDdzFI BuAyP2VkMW3T/ 2JPNtY7VelD6B1m UEJGvd 34aD+UcqzDwwSPa +fDfy9JQIGQeUPh MGrzBc+ ZGAvtq7xNMn9 JBQJJc/ W0AhsMAAoJEKthn TcjVMOiQBYAnjqE F54U0HUdJ3JE 8TzjlIc1pGxlnWB E91IIUq4FzZA= =
1oKaJ4B9kWJQanM
8GIShwJtEFVBpS4
KYYoOiI4G6k5WJa
320u7wt8VEvXUV8
IyqtGHyf5JOQUQJ
+hneBAC1invLXDe
xZdhTBLS6BjVJ7l
iDTLzKkvjjNwIli
ZWt1aG5AaG90bWF
FgIDAQIeAQIXgAA
OQvVHgmQ266jsNq
qthrNk6gIMdRKMU
K7QJT62A8mQCHOt
NdCk1/fzZq9Yc3X
IFcFImuFsGqf3vr
rQCavsYox98QMAg
6gqxnIhJBBgRAgA
oYo/l5t7j7RRAJ9
=mwCZ
-----END PGP PUBLIC KEY BLOCK-----
> Date: Fri, 10 Apr 2009 05:00:49 +0000 /cryptdisks. functions file /bugs.launchpad .net/bugs/ 55159
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 55159] Re: usplash prevents passwords from being not echoed on the console
>
> Luke : Thanks for your great work. Unfortunately I get a different
> result here. I overwrited my /lib/cryptsetup
> by the one provided in your comment #30 and I'm still able to see my
> passphrase echoed in plain text on console if I switch to console before
> finishing typing my passphrase using the initial steps in the bug
> description.
>
> I tested this with a luks partition which is mounted in "/media" (not a
> root partition) and therefore which is unlocked by cryptsetup during
> init.d and not initramfs.
>
> Can you see something that could be missing in your current fix so it
> can apply to the configuration I described?
>
> --
> usplash prevents passwords from being not echoed on the console
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
_______ _______ _______ _______ _______ _______ _______ _______ _______ __ windowslive. com/RediscoverH otmail? ocid=TXT_ TAGLM_WL_ HM_Rediscover_ Updates1_ 042009
Rediscover HotmailĀ®: Get quick friend updates right in your inbox.
http://