Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ncm-ssh: extend AllowTcpForwarding to support valid values #1691

Closed
wants to merge 13 commits into from

Conversation

duncanatwork
Copy link
Contributor

AllowTcpForwarding in ncm-ssh uses legacy_binary_affirmation_string, but other options such as "remote" and "local" are valid, so change schema to support valid values

Address #1690

AllowTcpForwarding in ncm-ssh uses legacy_binary_affirmation_string,
but other options such as "remote" and "local" are valid, so change
schema to support valid values
stdweird and others added 12 commits September 5, 2024 11:22
- See https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html
- Added to the global section because, even though
  `remoteipproxyprotocol` can be defined at the vhost level, only
  one such definition will take affect, and do so globally.
…p config for filebeat.yml (quattor#1700)

* ncm-metaconfig: add seccomp config to beats schema

Amend the beats schema to support configuration seccomp default action. This is because in Linux >3.16 (such as Rocky 9+) filebeat may be prevented from starting.
This is dramatically faster than having to install all the dependencies on every run.
Switch from using nobody to the quattortest user provided by our image.
@jrha jrha added this to the 24.next milestone Sep 5, 2024
@duncanatwork
Copy link
Contributor Author

Apologies, I've made a mess of this branch somehow, so I'll just create a new PR

@jrha jrha removed this from the 24.next milestone Sep 5, 2024
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.

9 participants