From: dac.override@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Enable ftpd_connect_all_unreserved boolean by default
Date: Thu, 10 Mar 2016 16:17:42 +0100 [thread overview]
Message-ID: <56E19016.7000207@gmail.com> (raw)
In-Reply-To: <56E17FD8.5030607@tresys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 03/10/2016 03:08 PM, Christopher J. PeBenito wrote:
> On 3/10/2016 9:07 AM, Dominick Grift wrote:
>> On 03/10/2016 03:05 PM, Christopher J. PeBenito wrote:
>>> On 3/10/2016 8:04 AM, Lukas Vrabec wrote:
>>>> Hi all,
>>>>
>>>> In current selinux-policy we have two booleans related to ftp
>>>> active/passive mode communication. Both of these booleans
>>>> are turned off by default. ftpd_use_passive_mode
>>>> (off , off) ftpd_connect_all_unreserved (off , off)
>>>>
>>>> In this situation, ftp daemon cannot start without changing
>>>> one of this booleans.
>>>>
>>>> I suggest enabling "ftpd_connect_all_unreserved" boolean by
>>>> default.
>>>>
>>>> Your ideas?
>>>>
>>>>
>>>> Thank you for discussion.
>>
>>> It sounds like there may be some port labeling problems. The
>>> passive mode Boolean allows TCP binding on all unreserved ports
>>> and the connect_all allows TCP connecting to all unreserved
>>> ports. (unreserved ports means 1024-65535 that are not
>>> otherwise labeled)
>>
>>
>> Might be related to fedoras' ephemeral_port_t?
>
> That's a good point. I'm looking at refpolicy.
>
I think, but i am not sure that at anything one of the two booleans
must be set. passive mode requires binding , active mode requires
connecting. The problem is that it could be either any time. So i
think it would be reasonable to leave both off just to make no
assumptions.
- --
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQGcBAEBCAAGBQJW4ZARAAoJECV0jlU3+Udp5U4L/R/LUK3YcL3IVX8mAwUrtPyx
UFWYI5+/hLUzgYEMbiyobps/n63mgQCBArPDQsCdr6iqBwSKzFVIZm8pfzkUayRP
bPf+MJVmeSHQp/pMim3WxUy8em7TsS8Y4SbtD3Sq3pTST7KeCjtN7+kcLcrZJAVz
rm5DIlamB9wu/J1wDDg+8NWyjLC8mYaWAtPvC/SyjI2aCHIHjt5oFo256v8s7w8h
9oVh/hLsDFtmneWeTL0yXQqLlGwrtq6iEwxJeL8WGAsn652C/7soOgZVQC8rIiW1
LZleSJ1ZAThACJD6vF5A9F19WVSLLOfyuwa+3mbsGIxtU61jDgNTZHkqIipaMgg8
0OJbe2lbZOc3hO23BY+u+E5g0xjgQZGf6p7r7LsuXWUpYGLhNlBkjC8U4dnZa5IJ
vnFLMdq8ulxlVAZoUT6x0FQGNm/0ZQ/YPrCiaExBFG68aG+TYbkzDh8Mp6QrDs73
6C6BNdSWDQAVArTTR+Z7yIR2CqIDlc4aAETp6kF53A==
=sW2f
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2016-03-10 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 13:04 [refpolicy] Enable ftpd_connect_all_unreserved boolean by default Lukas Vrabec
2016-03-10 14:05 ` Christopher J. PeBenito
2016-03-10 14:07 ` Dominick Grift
2016-03-10 14:08 ` Christopher J. PeBenito
2016-03-10 15:17 ` Dominick Grift [this message]
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=56E19016.7000207@gmail.com \
--to=dac.override@gmail.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.