Issue

• What exactly does oo-gear-firewall bring to the table that wasn't already present prior to 2.1? The release notes read:

"The new oo-gear-firewall command creates firewall rules and SELinux policy to contain services running on gears to their own internal gear IPs. This prevents access to unprotected network resources running in another developer's gear."

• So prior to 2.2 and this tool services running on gears were/are not contained to their own internal gear IPs? And network resources in gears are not protected?