Running modprobe ecryptfs was all I needed. I guess this is something that should really be fixed at the package level, but now that I know what's going on I can easily kludge around it. :) (Although, I don't know if this makes sense, but wouldn't it be better in a situation like this to *try* to load both keys, even if we don't know the kernel supports filename encryption, and only fall back to showing the encrypted filenames if that fails?) Thanks again! Benjamin -- To unsubscribe from this list: send the line "unsubscribe ecryptfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
