On Di, 12.02.19 11:57, Daniel Tihelka (dtihelka@xxxxxxxxx) wrote: > Hello, > OK, thanks for the clarification. > > I was afraid that the situation is like you have described. Still it > surprises me that even the sshfs case cannot be handled by user > instance of systemd ... it should work if you only use .mount but not .automount. > Do you have any information that the kernel is going to open autofs > for unpriv clients? No. To my knowledge nobody is working on that. > Or, could it be a way to write a d-bus capable daemon (or use/extend > udisks or systemd capabilities?) which would handle the mounts for a > particular user, i.e. a user would provide remote host+fs > type+username+passwd+required mount point+access permissions and the > daemon would mount it then for the user as required. Or has this way a > security flow I don't see? I think the energy adding that would be better spent on fixing the kernel's autofs logic to be available unpriv... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel