All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaun Savage <savages@pcez.com>
To: selinux@tycho.nsa.gov, courier-users@lists.sourceforge.net
Subject: thanks, and new issue
Date: Thu, 13 Dec 2001 12:38:14 -0800	[thread overview]
Message-ID: <3C1911B6.5000607@pcez.com> (raw)

HI

Thanks, when I did a "make load" that fixed the newrole problem.

New Issue:

I am trying to add/make a new security policy for the courier mail 
server.  Sendmail is easy compared with qmail or courier.  This will 
also be a good learning experiance for me (and others) to go through the 
thinking behind creating a security policy.    I am not a courier 
expert,   but I think selinux and courier would be good togther.

The problem is how fine grained a security policy I should make?
Should every processes have a seperate policy or should the whole 
package be one security?
Should the certs be protected more than other parts?
Courier writes to the users Maildir in their home dir, only 
courier_local writes to users dir.  ????



Background:
Courier is a all inclusive mails server.  It is like qmail with 
different processes doing different tasks. It also has imap,pop3 secure 
imap,pop3 also.  It has a web interface to help with configuration.  And 
webmail client.

File structure
/etc/courier                courier_conf_t        configuration files

/var/spool/courier      courier_spool_t      spool directories for courier
/var/spool/courier/msgq    courier_msgq_t
/var/spool/courier/msgs     courier_msgs_t
/var/spool/courier/authdaemon

/usr/lib/courier          courier_t                 courier
/usr/lib/courier/bin    courier_bin_t
/usr/lib/courier/sbin   courier_sbin_t
/usr/lib/courier/share  courier_share_t
/usr/lib/courier/share/rootcerts    courier_certs_t               esmtp, 
imap, pop3 certs for SSL
/usr/lib/courier/share/htmldoc

Running processes:

courierd            main daemon            courier_daemon_t
courierXXXX   transport daemons    courier_trans_t
courieresmtp    input daemon             courier_esmtp_t
authdaemon      authorize connections courier_auth_t
couriertcpd       courier tcpd                  courier_tcpd_t
pop3d, pop3d-ssl, imapd, imapd-ssl       courier_XXXX_t
courierfilter      spam killer   (not used now)  courier_filter_t







--
You have received this message because you are subscribed to the selinux 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.

             reply	other threads:[~2001-12-13 20:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13 20:38 Shaun Savage [this message]
2001-12-14 14:30 ` thanks, and new issue Stephen Smalley

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=3C1911B6.5000607@pcez.com \
    --to=savages@pcez.com \
    --cc=courier-users@lists.sourceforge.net \
    --cc=selinux@tycho.nsa.gov \
    /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.