We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello!
For ufw_outgoing_traffic, should it allow to specify the protocol? For example, we would have:
ufw_outgoing_traffic: - 22/tcp - 53 # this means both, as is currently the case - 80/tcp etc...
I can make the PR with the necessary edits to:
ansible-role-hardening/tasks/ufw.yml
Lines 130 to 137 in 9045255
The text was updated successfully, but these errors were encountered:
yeah, that seems like a good addition.
something like, since 22/tcp doesn't work:
22/tcp
vars: ufw_outgoing_traffic: - { port: 80, proto: 'tcp' } - 443 - 53 - 123 - 22 - { port: 1234, proto: 'udp' } tasks: - name: Allow outgoing specified ports become: true community.general.ufw: rule: allow to_port: "{{ item.port | default(item) }}" proto: "{{ item.proto | default('tcp') }}" direction: out comment: ansible managed loop: "{{ ufw_outgoing_traffic }}"
Sorry, something went wrong.
konstruktoid
No branches or pull requests
Hello!
For ufw_outgoing_traffic, should it allow to specify the protocol? For example, we would have:
I can make the PR with the necessary edits to:
ansible-role-hardening/tasks/ufw.yml
Lines 130 to 137 in 9045255
The text was updated successfully, but these errors were encountered: