For the first part - having to wait before XScreenSaver brings up the password prompt and starts registering your key presses, I think Iambchop ’s answer in this thread is relevant:
‘This is an inevitable consequence of the new security model introduced in XScreenSaver 6.00. The old behavior will not be returning, so get used to clicking the mouse or tapping “Shift” before you start typing your password.’
XScreenSaver FAQ
‘The old XScreenSaver daemon contained 14.5k lines of code in a single executable. The new one contains 12.5k lines across three different executables – a 14% reduction overall. But as I said earlier, the critical section – the process whose crash will result in an unlock – now contains only 1.8k lines – an 87% reduction. This is great not just because it reduces the attack surface, but also because it’s easier to understand and audit.’
jwz: XScreenSaver 6.00 out now
As for having to write your password slower - I don’t know.
3 Likes