nusenu

```ruby + - name: t-guard-IPv6 + driver: + network: + - ["private_network", {ip: "192.0.2.10"}] + - ["private_network", {ip: "198.51.100.10"}] + - ["private_network", {ip: "2001:db8::1"}] + - ["private_network", {ip: "2001:db8::2"}] +...

thanks for this! did you test it? for which platforms?

This is best asked upstream if this is still an issue. Upstream documentation: https://support.torproject.org/apt/tor-deb-repo/

thanks for picking this up! I'm mostly using converge after an initial create, and I'm aiming to cover more test cases with a single converge run.

Generally, I agree. we will have to run a full (no tags) playbook before running the renewkey or reconfigure tags against targets. #176 might be handy then.

tor_ParentDataDir -> lets go with "tor_DataDirsFolder" (the folder that contains all tor DataDirs)

This will start to make (more) sense once tor no longer requires (online) RSA keys.

An example why this feature is worthwhile to implement: Ansible security vulnerability allowing target servers to inject commands on the ansible controller host (CVE-2016-8628).

We will not modify the maintainers service file and wait for upstream AppArmor support.

Yes because it is the same maintainer.