All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tetsuji Maverick Rai <tetsuji.maverick.rai@gmail.com>
To: russell@coker.com.au
Cc: selinux@tycho.nsa.gov
Subject: Re: Is SELinux appropriate for my use?
Date: Fri, 19 May 2006 05:05:17 +0900	[thread overview]
Message-ID: <446CD37D.1020500@gmail.com> (raw)
In-Reply-To: <200605171558.43653.russell@coker.com.au>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Russell Coker wrote:
> On Wednesday 17 May 2006 03:33, Tetsuji Maverick Rai 
> <tetsuji.maverick.rai@gmail.com> wrote:
>> I am dubious SELinux is necessary if I use only apache2 with phpBB and
>> other php based web applications.   Am I correct?   I am the only shell
>> user of the machine.
> 
> If an attacker cracks phpBB (which has been done before as you note) then 
> without SE Linux there is no restriction on their ability to try and crack 
> SETUID programs on the system.  When running SE Linux Apache is not permitted 
> to run /bin/passwd and other privileged programs so that someone who cracks 
> phpBB can not go on to attack such programs.
> 

Thank you for your reply.  But I still wonder....

What if apache's permission is set so that it isn't allowed to execute
most commands?    But actually most commands (i.e. even cat, ls) can be
dangerous, because it will display files containing mysql password.   So
does SELinux exist to prevent attackers from executing these "usual"
programs with http server's permissions(role)?   If so, I can understand
a bit....actually I understand this is secure.

And what's more?

I am writing this because SElinux isn't available with my favorite
reiserfs.   I need to use xfs or jfs to use SELinux (I don't like
ext2/3).  If reiserfs is compatible with SELinux, I'm sure I use
SELinux....or I am wondering I should move to jfs...(xfs is too slow.)

Regards,

- -tetsuji
- --
Tetsuji 'Maverick' Rai
Main http://maverick6664.bravehost.com/
Profile:
http://setiweb.ssl.berkeley.edu/beta/view_profile.php?userid=123
pubkey http://mav.atspace.com/tmr_at_gmail.txt
PGP Key ID: 82335CD9
Key fingerprint = 41CA 94B4 2A89 3FF1 5B11  BC37 D597 E667 8233 5CD9

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEbNN81ZfmZ4IzXNkRAj9zAJ9Vu+bq8nhFAo2i4GX3ycM2YLQZCQCfVfpj
Xvw97AKcjydhjeJfd3awKA8=
=vThj
-----END PGP SIGNATURE-----

--
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.

  reply	other threads:[~2006-05-18 20:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 17:33 Is SELinux appropriate for my use? Tetsuji Maverick Rai
2006-05-17  5:58 ` Russell Coker
2006-05-18 20:05   ` Tetsuji Maverick Rai [this message]
2006-05-19  7:08     ` Valdis.Kletnieks
2006-05-19 13:54       ` Russell Coker
2006-05-19 18:03         ` Christopher J. PeBenito
2006-05-19 18:08           ` Christopher J. PeBenito
2006-05-21  3:47         ` Valdis.Kletnieks
2006-05-21  7:59           ` Russell Coker
2006-05-19 17:34       ` Tetsuji Maverick Rai
2006-05-19  9:58     ` Russell Coker

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=446CD37D.1020500@gmail.com \
    --to=tetsuji.maverick.rai@gmail.com \
    --cc=russell@coker.com.au \
    --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.