https://bugs.kde.org/show_bug.cgi?id=346741
--- Comment #11 from Giorgio <gio...@yahoo.it> --- (In reply to Holger from comment #10) > so let's wait what the kscreenlocker maintainer thinks on the topic. Does it exist? Bug has been opened more than FOUR ! years ago and I don't see a single answer from KDE maintainers. (In reply to Holger from comment #5) > (In reply to Giorgio from comment #4) > > KDE in mobile device with autostart ?????? > > "mobile" in sense of "portable" as: netbook, notebook, laptop > > > Suspend to RAM just after having switched on ? > > No, not necessarily. I meant you to prepare for your presentation by opening > and arranging all needed programs at home, suspend your device and wake it > up the moment you need it. Waking up is quite fast and you can make it query > for the password. > > > Encrypted hard drive? > > > > May be my english knowledge is quite low but I don't see any relation with > > this bug. > > Hard-drive encryption also requires a password. People likely dislike > entering first the hard-drive password and second the login password, so > auto-login without password is perfectly sensible if you are using > hard-drive encryption. On the other hand, if you don't use hard-drive > encryption, the requested feature of auto-login + locked screen provides a > false semblance of security, while the device can easily be compromised. > > In short: > - the original request is a security anti-feature > - suspend2RAM will hopefully be an acceptable workaround (security-wise as > well as usability-wise) -- You are receiving this mail because: You are watching all bug changes.
