)]}'
{"specs/pike/software-firewall.rst":[{"author":{"_account_id":15993,"name":"Amy Marrich","display_name":"Amy Marrich (spotz)","email":"amy@demarco.com","username":"amarrich"},"change_message_id":"d5b02e03c24fbd107f8d48c128617996afb4a30c","unresolved":false,"context_lines":[{"line_number":6,"context_line":"Blueprint link:"},{"line_number":7,"context_line":"  * https://blueprints.launchpad.net/openstack-ansible/+spec/example"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"OpenStack-Ansible deployments have plenty of security mechanisms in place to"},{"line_number":10,"context_line":"limit access to critical services, but there is not a strong set of software"},{"line_number":11,"context_line":"firewall configurations to ensure that only the valid traffic is allowed. This"},{"line_number":12,"context_line":"can provide additional protection for misconfigured services as well as"},{"line_number":13,"context_line":"mitigate some types of vulnerabilities until they can be patched."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Problem description"},{"line_number":16,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f1a1f67_744901b5","line":13,"range":{"start_line":9,"start_character":0,"end_line":13,"end_character":65},"updated":"2017-07-18 18:05:44.000000000","message":"OpenStack-Ansible deployments have numerous security mechanisms in place to limit access to critical services. However, there is not a strong set of software firewall configurations to ensure that only the valid traffic is allowed. This spec provides additional protection for misconfigured services as well as the mitigation of some types of vulnerabilities until they can be patched.","commit_id":"f5a76124c89007c05a2b85e5c1b548b15b1cb010"},{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"d2282daf76f33942137a09dffe4d1a421d59d8c0","unresolved":false,"context_lines":[{"line_number":10,"context_line":"limit access to critical services, but there is not a strong set of software"},{"line_number":11,"context_line":"firewall configurations to ensure that only the valid traffic is allowed. This"},{"line_number":12,"context_line":"can provide additional protection for misconfigured services as well as"},{"line_number":13,"context_line":"mitigate some types of vulnerabilities until they can be patched."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Problem description"},{"line_number":16,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f1a1f67_2d2e9c91","line":13,"updated":"2017-07-18 19:18:01.000000000","message":"Thanks for that. I must have been thinking about something else entirely when I wrote the intro paragraph. ;)","commit_id":"f5a76124c89007c05a2b85e5c1b548b15b1cb010"},{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"bcf1a7a1b2b8a98f7e45f03506395a17bb078465","unresolved":false,"context_lines":[{"line_number":178,"context_line":"   which ``firewalld`` zones (may require defining custom zones) and apply the"},{"line_number":179,"context_line":"   role to each `(Phase One)`"},{"line_number":180,"context_line":"4. Add variables to service roles that define which ports and protocols are"},{"line_number":181,"context_line":"   allowed into the host or container `(Phase Two)`"},{"line_number":182,"context_line":"5. Restrict source/destination traffic at the physical host level"},{"line_number":183,"context_line":"   `(Phase Three)`"},{"line_number":184,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"1f1a1f67_46fee905","line":181,"updated":"2017-07-21 13:14:29.000000000","message":"Ah, good point. We do this with haproxy stuff for now, so we could follow the same pattern.","commit_id":"8a834d036f0fe7a89a4c072f0b9bec62e9aabfbc"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"33610b2f4985526c2d42ee49fb7ba339f4e466a6","unresolved":false,"context_lines":[{"line_number":178,"context_line":"   which ``firewalld`` zones (may require defining custom zones) and apply the"},{"line_number":179,"context_line":"   role to each `(Phase One)`"},{"line_number":180,"context_line":"4. Add variables to service roles that define which ports and protocols are"},{"line_number":181,"context_line":"   allowed into the host or container `(Phase Two)`"},{"line_number":182,"context_line":"5. Restrict source/destination traffic at the physical host level"},{"line_number":183,"context_line":"   `(Phase Three)`"},{"line_number":184,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"1f1a1f67_47516762","line":181,"updated":"2017-07-20 17:35:42.000000000","message":"What do you mean there? Is that a separate variable that goes into each of the service role? (That doesn\u0027t sound a good separation of concerns, but I am not sure I understood you there)\n\nI\u0027d naturally think that this kind of variable is perfect for a group var, this way we can apply it the same way to all the hosts, and still let the users have their own override.","commit_id":"8a834d036f0fe7a89a4c072f0b9bec62e9aabfbc"},{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"8da350102dc2322cbf6c83d3cc007317f213c4be","unresolved":false,"context_lines":[{"line_number":4,"context_line":":tags: used, for, groupings, and, indexing"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"Blueprint link:"},{"line_number":7,"context_line":"  * https://blueprints.launchpad.net/openstack-ansible/+spec/example"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"OpenStack-Ansible deployments have numerous security mechanisms in place to"},{"line_number":10,"context_line":"limit access to critical services. However, there is not a strong set of"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ff346bd7_cbf06d00","line":7,"updated":"2017-07-26 14:38:47.000000000","message":"Hah, I\u0027ll get the BP link added in there. ;)","commit_id":"8893a3d8e0c6d55f09fdc66fa7b0696cc738b52e"},{"author":{"_account_id":23163,"name":"Markos Chandras (hwoarang)","email":"markos@chandras.me","username":"mchandras"},"change_message_id":"138ec459c0dd2a22313f3cde990e418bd37dbeaf","unresolved":false,"context_lines":[{"line_number":4,"context_line":":tags: used, for, groupings, and, indexing"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"Blueprint link:"},{"line_number":7,"context_line":"  * https://blueprints.launchpad.net/openstack-ansible/+spec/example"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"OpenStack-Ansible deployments have numerous security mechanisms in place to"},{"line_number":10,"context_line":"limit access to critical services. However, there is not a strong set of"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ff346bd7_0291ba47","line":7,"range":{"start_line":7,"start_character":61,"end_line":7,"end_character":68},"updated":"2017-07-26 13:32:40.000000000","message":"this is probably not right","commit_id":"8893a3d8e0c6d55f09fdc66fa7b0696cc738b52e"},{"author":{"_account_id":17799,"name":"Logan V","email":"logan2211@gmail.com","username":"Logan2211"},"change_message_id":"0e3845015a3c27927e7c62b737e11fb63d23b228","unresolved":false,"context_lines":[{"line_number":47,"context_line":"1. service in a container to haproxy (example: nova ➜ glance)"},{"line_number":48,"context_line":"2. service in a container to hypervisor"},{"line_number":49,"context_line":"   (example: user ➜ console ➜ VNC/Spice port)"},{"line_number":50,"context_line":"3. service in a container container to physical host"},{"line_number":51,"context_line":"   (example: swift proxy ➜ swift object host)"},{"line_number":52,"context_line":"4. service in a container to service in a container (example: Glance ➜ MariaDB)"},{"line_number":53,"context_line":"5. haproxy to service in a container (example: user ➜ haproxy ➜ horizon)"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ff346bd7_8532a2f0","line":50,"range":{"start_line":50,"start_character":26,"end_line":50,"end_character":35},"updated":"2017-07-24 16:38:22.000000000","message":"\u003csnip\u003e","commit_id":"8893a3d8e0c6d55f09fdc66fa7b0696cc738b52e"},{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"8da350102dc2322cbf6c83d3cc007317f213c4be","unresolved":false,"context_lines":[{"line_number":47,"context_line":"1. service in a container to haproxy (example: nova ➜ glance)"},{"line_number":48,"context_line":"2. service in a container to hypervisor"},{"line_number":49,"context_line":"   (example: user ➜ console ➜ VNC/Spice port)"},{"line_number":50,"context_line":"3. service in a container container to physical host"},{"line_number":51,"context_line":"   (example: swift proxy ➜ swift object host)"},{"line_number":52,"context_line":"4. service in a container to service in a container (example: Glance ➜ MariaDB)"},{"line_number":53,"context_line":"5. haproxy to service in a container (example: user ➜ haproxy ➜ horizon)"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ff346bd7_abf529ef","line":50,"updated":"2017-07-26 14:38:47.000000000","message":"But what about the containers in containers? Just kidding. I\u0027ll fix it up. ;)","commit_id":"8893a3d8e0c6d55f09fdc66fa7b0696cc738b52e"},{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"8da350102dc2322cbf6c83d3cc007317f213c4be","unresolved":false,"context_lines":[{"line_number":49,"context_line":"   (example: user ➜ console ➜ VNC/Spice port)"},{"line_number":50,"context_line":"3. service in a container container to physical host"},{"line_number":51,"context_line":"   (example: swift proxy ➜ swift object host)"},{"line_number":52,"context_line":"4. service in a container to service in a container (example: Glance ➜ MariaDB)"},{"line_number":53,"context_line":"5. haproxy to service in a container (example: user ➜ haproxy ➜ horizon)"},{"line_number":54,"context_line":"6. physical host to container (example: nova-compute ➜ RabbitMQ)"},{"line_number":55,"context_line":"7. physical host or container to internet (example: apt/yum package updates)"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ff346bd7_8bdee56a","line":52,"updated":"2017-07-26 14:38:47.000000000","message":"Good catch. I\u0027ll fix that.","commit_id":"8893a3d8e0c6d55f09fdc66fa7b0696cc738b52e"},{"author":{"_account_id":17799,"name":"Logan V","email":"logan2211@gmail.com","username":"Logan2211"},"change_message_id":"0e3845015a3c27927e7c62b737e11fb63d23b228","unresolved":false,"context_lines":[{"line_number":49,"context_line":"   (example: user ➜ console ➜ VNC/Spice port)"},{"line_number":50,"context_line":"3. service in a container container to physical host"},{"line_number":51,"context_line":"   (example: swift proxy ➜ swift object host)"},{"line_number":52,"context_line":"4. service in a container to service in a container (example: Glance ➜ MariaDB)"},{"line_number":53,"context_line":"5. haproxy to service in a container (example: user ➜ haproxy ➜ horizon)"},{"line_number":54,"context_line":"6. physical host to container (example: nova-compute ➜ RabbitMQ)"},{"line_number":55,"context_line":"7. physical host or container to internet (example: apt/yum package updates)"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ff346bd7_e5404e38","line":52,"range":{"start_line":52,"start_character":0,"end_line":52,"end_character":79},"updated":"2017-07-24 16:38:22.000000000","message":"invalid example. glance does not connect to mariadb, it connects to haproxy for database connections.","commit_id":"8893a3d8e0c6d55f09fdc66fa7b0696cc738b52e"},{"author":{"_account_id":17799,"name":"Logan V","email":"logan2211@gmail.com","username":"Logan2211"},"change_message_id":"4b23cd46b6850b0ea526889ff316afb492117d7b","unresolved":false,"context_lines":[{"line_number":49,"context_line":"   (example: user ➜ console ➜ VNC/Spice port)"},{"line_number":50,"context_line":"3. service in a container container to physical host"},{"line_number":51,"context_line":"   (example: swift proxy ➜ swift object host)"},{"line_number":52,"context_line":"4. service in a container to service in a container (example: Glance ➜ MariaDB)"},{"line_number":53,"context_line":"5. haproxy to service in a container (example: user ➜ haproxy ➜ horizon)"},{"line_number":54,"context_line":"6. physical host to container (example: nova-compute ➜ RabbitMQ)"},{"line_number":55,"context_line":"7. physical host or container to internet (example: apt/yum package updates)"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ff346bd7_28d3c23a","line":52,"range":{"start_line":52,"start_character":0,"end_line":52,"end_character":79},"in_reply_to":"ff346bd7_e5404e38","updated":"2017-07-24 23:50:10.000000000","message":"i was trying to think of an appropriate example here.. \u003csomething\u003e accessing either memcached or rabbitmq would be applicable I think","commit_id":"8893a3d8e0c6d55f09fdc66fa7b0696cc738b52e"},{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"8da350102dc2322cbf6c83d3cc007317f213c4be","unresolved":false,"context_lines":[{"line_number":59,"context_line":"Proposed change"},{"line_number":60,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"The goal would be to utilize ``firewalld`` to manage firewall configurations"},{"line_number":63,"context_line":"for both IPv4 and IPv6. It is available for all of the operating systems that"},{"line_number":64,"context_line":"are supported by OpenStack-Ansible in the Pike release. There are already"},{"line_number":65,"context_line":"Ansible modules that help with ``firewalld`` configurations."}],"source_content_type":"text/x-rst","patch_set":4,"id":"ff346bd7_6bdbc17b","line":62,"updated":"2017-07-26 14:38:47.000000000","message":"I could easily be swayed away from using firewalld. Plain old iptables is fairly predictable and a well-done jinja2 template with easy to use variables could be nice. I might send an email to the ML for more feedback on this.","commit_id":"8893a3d8e0c6d55f09fdc66fa7b0696cc738b52e"},{"author":{"_account_id":17799,"name":"Logan V","email":"logan2211@gmail.com","username":"Logan2211"},"change_message_id":"0e3845015a3c27927e7c62b737e11fb63d23b228","unresolved":false,"context_lines":[{"line_number":59,"context_line":"Proposed change"},{"line_number":60,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"The goal would be to utilize ``firewalld`` to manage firewall configurations"},{"line_number":63,"context_line":"for both IPv4 and IPv6. It is available for all of the operating systems that"},{"line_number":64,"context_line":"are supported by OpenStack-Ansible in the Pike release. There are already"},{"line_number":65,"context_line":"Ansible modules that help with ``firewalld`` configurations."}],"source_content_type":"text/x-rst","patch_set":4,"id":"ff346bd7_453cba92","line":62,"range":{"start_line":62,"start_character":0,"end_line":62,"end_character":42},"updated":"2017-07-24 16:38:22.000000000","message":"I\u0027m questioning a little bit whether firewalld is the ideal implementation for this.\n\nI\u0027ve always steered clear of ufw and firewalld because they offer only a tiny subset of the ruleset match parameters and features that iptables offers. Any rules beyond the basic allow/deny are foreign to these tools, so you can forget hashlimit and other sophisticated match expressions.\n\nSo if using firewalld/ufw comes at the expense of the majority of the iptables feature set, what\u0027s the gain? I don\u0027t think it offers a more consistent configuration syntax than iptables-save/iptables-restore templating, and every distro I\u0027ve seen has the ability to handle autoloading of iptables-restore upon boot.\n\nI\u0027d suggest we build an awesome data structure for iptables-save templating that will enable us to use the full iptables featureset in a well defined data structure, and the associated handler tasks needed to iptables-restore upon changes.\n\nThat\u0027s been the most successful iptables management experience I\u0027ve had with ansible fwiw.","commit_id":"8893a3d8e0c6d55f09fdc66fa7b0696cc738b52e"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"3be2e90804cc610b90afcc546ca0ea68eed3279e","unresolved":false,"context_lines":[{"line_number":59,"context_line":"Proposed change"},{"line_number":60,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"The goal would be to utilize ``firewalld`` to manage firewall configurations"},{"line_number":63,"context_line":"for both IPv4 and IPv6. It is available for all of the operating systems that"},{"line_number":64,"context_line":"are supported by OpenStack-Ansible in the Pike release. There are already"},{"line_number":65,"context_line":"Ansible modules that help with ``firewalld`` configurations."}],"source_content_type":"text/x-rst","patch_set":4,"id":"df3967d1_ad7da2e8","line":62,"in_reply_to":"ff346bd7_6bdbc17b","updated":"2017-07-31 07:28:10.000000000","message":"Either we make this blueprint implementation independant, or we\u0027ll have t modify the references in firewalld in the blueprint/propose another one.\n\nI like Logan\u0027s idea: Having a good data structure is important, and even be an abstraction of the implementation if successfully done.","commit_id":"8893a3d8e0c6d55f09fdc66fa7b0696cc738b52e"},{"author":{"_account_id":7307,"name":"Matt Thompson","email":"mattt@defunct.ca","username":"mattt416"},"change_message_id":"23adb40a395ef91df86520fbf2bcabdec4ce548a","unresolved":false,"context_lines":[{"line_number":23,"context_line":"  If an attacker finds a weakness in a particular service, they can use that"},{"line_number":24,"context_line":"  weakness as a foothold to attack other parts of the environment."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"  For example, Glance has no reason to talk to RabbitMQ, but it has a usable"},{"line_number":27,"context_line":"  network path to the RabbitMQ containers. If an attacker exploits a"},{"line_number":28,"context_line":"  vulnerability in Glance, they could use that access to reach the RabbitMQ"},{"line_number":29,"context_line":"  containers and cause problems."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f436f4f_f67f5163","line":26,"updated":"2017-08-15 16:26:26.000000000","message":"Perhaps a bad example since Glance can be configured to send notification to RabbitMQ.","commit_id":"cad3d7df2387b9dbc12d0454774ed3073467f367"}]}
