* How should we handle automount.
@ 2005-05-02 15:01 Daniel J Walsh
2005-05-02 17:12 ` Stephen Smalley
0 siblings, 1 reply; 3+ messages in thread
From: Daniel J Walsh @ 2005-05-02 15:01 UTC (permalink / raw)
To: Stephen Smalley, SELinux
Needs to be able to create/remove mounton arbitrary directories in
arbitrary locations?
file_domain_auto_trans(automount_t, file_type, autofs_t, dir) ????
Then how do we allow automount to delete the directory?
--
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How should we handle automount.
2005-05-02 15:01 How should we handle automount Daniel J Walsh
@ 2005-05-02 17:12 ` Stephen Smalley
2005-05-02 17:32 ` Daniel J Walsh
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Smalley @ 2005-05-02 17:12 UTC (permalink / raw)
To: Daniel J Walsh; +Cc: SELinux
On Mon, 2005-05-02 at 11:01 -0400, Daniel J Walsh wrote:
> Needs to be able to create/remove mounton arbitrary directories in
> arbitrary locations?
Allowing it to do so on arbitrary directories doesn't seem desirable,
any more than allowing mount to mount on arbitrary directories. Can we
identify a reasonable set of mount point directories that might be used
by automount?
> file_domain_auto_trans(automount_t, file_type, autofs_t, dir) ????
s/domain/type
autofs_t is for the autofs inodes themselves, so I don't think you want
to apply them to the mount point directories. Does automount always re-
create the mount point directory, or does it re-use one if it already
exists?
> Then how do we allow automount to delete the directory?
It would need permissions to the parent, so you need to be able to
enumerate or identify by attribute what directory types might be used.
--
Stephen Smalley <sds@epoch.ncsc.mil>
National Security Agency
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How should we handle automount.
2005-05-02 17:12 ` Stephen Smalley
@ 2005-05-02 17:32 ` Daniel J Walsh
0 siblings, 0 replies; 3+ messages in thread
From: Daniel J Walsh @ 2005-05-02 17:32 UTC (permalink / raw)
To: Stephen Smalley; +Cc: SELinux
Stephen Smalley wrote:
>On Mon, 2005-05-02 at 11:01 -0400, Daniel J Walsh wrote:
>
>
>>Needs to be able to create/remove mounton arbitrary directories in
>>arbitrary locations?
>>
>>
>
>Allowing it to do so on arbitrary directories doesn't seem desirable,
>any more than allowing mount to mount on arbitrary directories. Can we
>identify a reasonable set of mount point directories that might be used
>by automount?
>
>
Automount Maintainer response:
Unfortunately, no. The users of automount create a varied array of
directory hierarchies.
>
>
>>file_domain_auto_trans(automount_t, file_type, autofs_t, dir) ????
>>
>>
>
>s/domain/type
>
>
>
Typo.
>autofs_t is for the autofs inodes themselves, so I don't think you want
>to apply them to the mount point directories. Does automount always re-
>create the mount point directory, or does it re-use one if it already
>exists?
>
>
>
I was just looking for a type with mounton type. Maybe we could create
an automont_mnt_t
file_type_auto_trans(automount_t, file_type, automount_mnt_t, dir)
>>Then how do we allow automount to delete the directory?
>>
>>
>
>It would need permissions to the parent, so you need to be able to
>enumerate or identify by attribute what directory types might be used.
>
>
>
Yup that is the problem. If there was a way to say automount can only
remove automount_mnt_t directories.
Dan
--
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-05-02 17:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-02 15:01 How should we handle automount Daniel J Walsh
2005-05-02 17:12 ` Stephen Smalley
2005-05-02 17:32 ` Daniel J Walsh
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.