Skip to content

Conversation

@aleksandrychev
Copy link
Contributor

Ticket: ENT-13666

Ticket: ENT-13666
Signed-off-by: Ihor Aleksandrychiev <ihor.aleksandrychiev@northern.tech>
@aleksandrychev
Copy link
Contributor Author

aleksandrychev commented Feb 10, 2026

with this fix:

sudo ausearch -m avc -ts recent
<no matches>

allow cfengine_apachectl_t user_devpts_t:chr_file getattr;

#============= cfengine_execd_t ==============
allow cfengine_execd_t http_port_t:tcp_socket name_connect;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any clue why cf-execd (and cf-serverd below) want to be able to connect to HTTP? Something new in pre-eval?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, would be good to reference masterfiles. Maybe it is us trying to query the aws api in inventory!?

@@ -0,0 +1,69 @@
require {
type cfengine_reactor_t;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am suspicious about all the requires. I remember this biting us in the past. Look at other policies for hints on using macros for many includes instead.

}

#============= cfengine_apachectl_t ==============
allow cfengine_apachectl_t devpts_t:dir { getattr search };
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be interesting to compare this to a standard apache httpd policy.

allow cfengine_apachectl_t user_devpts_t:chr_file getattr;

#============= cfengine_execd_t ==============
allow cfengine_execd_t http_port_t:tcp_socket name_connect;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, would be good to reference masterfiles. Maybe it is us trying to query the aws api in inventory!?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants