Is there any way to unlock and mount encrypted volume automatically on KDE4 session login via KDM?
I've had such setup on GDM/Gnome, achieved that with tricky pam_mount configuration. I have no idea how to do it in KDE4.
I've been experimenting to change settings via Systemsettings→Administration→Actions Policy→org.freedesktop→The udisks Project but with no success. Every time I need to access encrypted volume KDE4 asks me for few passwords: first for kwallet, another one to unlock volume, next for kwallet again (why? O_o) and last for superuser access. That's way to much. I think one password upon login is enough. One password to unlock them all!

I'd appreciate any useful tips. TYIA.

Hi r4e3z, I accomplished auto mounting of my encrypted drive on my Debian Squeeze server simply by editing /etc/security/pam_mount.conf.xml and adding

<volume user="USERNAME" fstype="crypt" path="/dev/sdc1" mountpoint="/home/USERNAME"/>

You'll need to change the usual suspects (user and path settings), and look here for more information: http://www.nanonanonano.net/linux/debian/enchome

Anyway, if your already using Pam_mount, you can just configure it as a system wide thing, regardless of GUI, without changing anything in KDE.

Not sure why it is asking for the KWallet password, but I suspect it is offering the option to you of saving the password. It needs to open it to check if you have a password stored (which you don't) so it prompts, then it wants to open it to save it (even though you haven't ticked the option - otherwise the previous prompt and this prompt wouldn't have happened).

You can reduce it by 1 prompt if you set KWallet to remain open for a specified length of time instead of closing when nothing needs it. If you save it in KWallet, then you can reduce it by another prompt.

I can't get it working with KDM.
I don't know how Debian's pam is configured but tips from Gentoo forum make auto unlocking working with GDM: http://forums.gentoo.org/viewtopic-t-837066.html

PAM should be the same with both KDM and GDM. KDM may be using a seperate PAM configuration file for it's authentication chain however.