From: Daniel J Walsh <dwalsh@redhat.com>
To: Alice Mynona <alice_mynona@bian-fu.net>
Cc: SELinux@tycho.nsa.gov
Subject: Re: Developing a SELinux policy for antivirus - How to access /home?
Date: Fri, 18 Jun 2010 12:53:36 -0400 [thread overview]
Message-ID: <4C1BA490.5030807@redhat.com> (raw)
In-Reply-To: <4C1B9CDC.2000802@bian-fu.net>
On 06/18/2010 12:20 PM, Alice Mynona wrote:
> Hello,
>
> I'm planning to develop a SELinux module for an antivirus software. This software should protect the system from beeing infected by
> malicious files in /home. Of course, the software will be executed in a separate domain i. e. antivirus_t.
>
> What do you recommend to allow the antivirus software to access (and manage) files und directories under /home?
>
> My first thought was to allow the antivirus software to manage files of the type "user_home_dir_t" and directories of the type "user_home_dir_t" by using the corresponding interfaces in the reference policy (i. e. "userdom_manage_user_home_dirs"). But what's about other filetypes like "gnome_home_t", "irc_home_t", "screen_tmp_t" and so on? Is there a general method to manage files under "/home" or do you have an another idea? Am I missing something?
>
> Thanks in advance.
>
> Best regards,
> Alice
>
All files types stored in the home dir have an attribute of user_home_type.
What is your goal of this antivirus tools? Scan all files in the
homedir for bad content?
--
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.
next prev parent reply other threads:[~2010-06-18 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 16:20 Developing a SELinux policy for antivirus - How to access /home? Alice Mynona
2010-06-18 16:52 ` Jeff Johnson
2010-06-18 16:53 ` Daniel J Walsh [this message]
2010-06-18 18:14 ` Alice Mynona
2010-06-18 18:50 ` Daniel J Walsh
2010-06-18 18:55 ` Stephen Smalley
2010-06-19 10:46 ` Alice Mynona
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C1BA490.5030807@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
--cc=alice_mynona@bian-fu.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.