[Dnssec-trigger] Install issues on MacOS 10.8: user, config

[Phil Pennock]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

On 2013-03-20 at 17:10 +0100, W.C.A. Wijngaards wrote:
> The 0.12 had no progress because apart from annoyances there are no
> bugs or activities to perform,

Well, on MacOS 10.8 it leaves the system with no functioning DNS, which
is problematic.

> Is this some sort of conflict between MacPorts and dnssec-trigger, if
> you uninstalled unbound macports did that also stop the unbound that
> came with dnssec-trigger somehow?

No: the system where I had unbound installed via MacPorts is the system
where dnssec-trigger worked.

Installing dnssec-trigger on a clean 10.8 system, where there is no sign
of MacPorts, fails.  Because the user creation is broken.  And then
something _else_ going wrong, such that dnssec-trigger-control-setup.sh
appears to not be called, because unbound.conf does not get the auto
trust anchor and remote control settings added to it.

On my laptop, with MacPorts, it had been flawless.

> Perhaps we should have website instructions to use the DMG for OSX
> users.  Or get it signed via Apple somehow.  Or even the App Store,
> alhough I believe that stuff is sandboxed and dnssec-trigger needs root.

Heck, just a PGP detached signature on the DMG would be nice.  :)
Otherwise, developer signing keys would avoid some installation
warnings, without needing to go through the App Store.

- -Phil
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlFKCsQACgkQQDBDFTkDY39EawCfQVJu4iQ8CZFreswqlv6aIBgT
p5IAnjTDZOmvrpvznsfg6G7uVtKZQoJj
=pDw4
-----END PGP SIGNATURE-----