RE: [PATCH 00/25] Current autofs patch queue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>> I'm not sure what you mean.

Just that I've not seen it, so thanks for the example.

>> Users can create user-specific CIFS mounts today with "sudo mount -t cifs -o sec=krb5,cruid=$UID,...".
>> The intention of my patch is just to enable autofs to create such mounts.

But that leaves the mount permission dependent on who make the first call.

>> P.S.: You are correct that there is an issue with autofs caching the list of mount points if the
>> list of mountable shares returned by a server depends on the credentials provided. AFAICS that can
>> be fixed by configuring the such that all users can see the same shares (but not necessarily
>> access/mount them all).

And once you've done that the UID that needs to be used for each of these mounts is mount-specific,
not "who caused the mount"-specific. Which is why I see a problem with it.



________________________________

This e-mail was sent by GlaxoSmithKline Services Unlimited
(registered in England and Wales No. 1047315), which is a
member of the GlaxoSmithKline group of companies. The
registered address of GlaxoSmithKline Services Unlimited
is 980 Great West Road, Brentford, Middlesex TW8 9GS.

--
To unsubscribe from this list: send the line "unsubscribe autofs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux Ext4]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux