From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] services_ftp.patch
Date: Tue, 27 Apr 2010 08:55:18 -0400 [thread overview]
Message-ID: <4BD6DEB6.7040100@redhat.com> (raw)
In-Reply-To: <1272309647.32279.232.camel@gorn>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/26/2010 03:20 PM, Christopher J. PeBenito wrote:
> On Tue, 2010-02-23 at 17:12 -0500, Daniel J Walsh wrote:
>> http://people.fedoraproject.org/~dwalsh/SELinux/F13/services_ftp.patch
>>
>> Better handling of proftpd
>
> Why does ftpd_t need sys_admin?
mounting file system on login?
>
> The change for ftp_home_dir is not acceptable. Enabling that tunable
> shouldn't allow access to all files.
>
Perhaps we need another boolean, to allow full access. If some wants to
allow an ftp server to provide access to all files on the machine.
> Why does ftp need to connect to a db?
>
You can use a mysql database as a back end for ftp.
>> Added handling of sftpd from sshd
>
> Otherwise merged.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkvW3rYACgkQrlYvE4MpobNmXACg6tElqZUPBgxM7sRM52ApIjpv
pvsAn3NodMz+sw+ysgmqU67O3B0MI/ZT
=RXkF
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-04-27 12:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 22:12 [refpolicy] services_ftp.patch Daniel J Walsh
2010-04-26 19:20 ` Christopher J. PeBenito
2010-04-26 19:36 ` Chris Richards
2010-04-26 20:02 ` Paul Howarth
2010-04-26 21:13 ` Chris Richards
2010-04-27 12:55 ` Daniel J Walsh [this message]
2010-04-27 12:58 ` Dominick Grift
-- strict thread matches above, loose matches on Subject: below --
2010-08-26 21:18 Daniel J Walsh
2009-11-12 21:32 Daniel J Walsh
2009-03-05 16:40 Daniel J Walsh
2008-09-24 20:34 Daniel J Walsh
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=4BD6DEB6.7040100@redhat.com \
--to=dwalsh@redhat.com \
--cc=refpolicy@oss.tresys.com \
/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.