Outstanding bugs/todo for libicd-{tor,wireguard,openvpn}-* and related cpa/status applets

[MerlijnWajer]

General:

• Make sure that the dh script for libicd module network_type does not mess up, maybe port to Python for maintenance ease (maemo-leste/maemo-system-services@cfd708a)
• Run valgrind with icd and the modules loaded/active
• WLAN_ADHOC not yet supported

Wireguard:

• CPA does not work with peers reliably (it segfaults in any other case than when you select peers on selection) maemo-leste/wireguard-network-applet@4a4caa4
• Have gconf option to use a predefined config rather than a generated one (like openvpn)
• interface monitoring seems to also act on unrelated interfaces (that's a bug)
• Make DNS optional, or just remove it for now
• Depend on resolvconf (??? maybe??? for DNS only though)
• Remove all validation that is incomplete, in other words, just do not validate if the validation is incomplete, since it blocks usage. Alternatively make validation complete
• Deleting a peer does not remove it from gconf
• Editing an existing config with a peer doesn't really have an obvious way to add a peer, you have to 'save' the current peer
• Unchecking the 'add peers' checkbox doesn't get saved to gconf, and the peers are also not removed
• Changing config name in edit dialog results in duplicating config

Tor:

• Status applet crashes/segfaults on Tor disconnect: maemo-leste/tor-network-applet@bfd1670
• iptables rules are not set yet for transparent proxying
• Debian upgrading the Tor package will cause it to be re-added to the runlevel

OpenVPN:

• Make sure Debian does not attempt to start openvpn on boot
• Add interface monitoring to support the "Connecting/Starting" signal
• changing system wide status does not work (?)

[MerlijnWajer]

Another one: do the status applets actually send the new requested active config, and do the icd applets honours that new config? Or is this done through gconf, and does icd2 not get the new active config because of some sync problems?