[Dnssec-trigger] Resolution on resume from hibernate (MacOS 10.8)

[W.C.A. Wijngaards]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Phil,

New version I made with fixes:
http://nlnetlabs.nl/~wouter/dnssectrigger-0.12_20130422.dmg

- - Fixup OSX backquote backslashes.  This is in the installer, and
affects the user creation.
- - Removed wrong OSX version from its installer text.


On 04/19/2013 11:49 PM, Phil Pennock wrote:
> I unpacked the install stuff on my laptop and found one problem,
> but the logic should be the same anyway so it's not the root cause.
> I can't (at this time) take my colleague's laptop away to
> repeatedly probe what's happening.

Something about user permissions, then, likely.

> /Volumes/DnssecTrigger/dnssectrigger-0.12_20130409-i386.mpkg/Contents/Packages/packageroot.pkg/Contents/Resources/postflight
>
> 
- ----------------------------8< cut here >8------------------------------
> #!/bin/bash # stop unbound if launch plist exists OSVERS=10.6 
> INSTLOG=/tmp/dnssectrigger-0.12_20130409-install.log 
> ----------------------------8< cut here
> >8------------------------------
> 
> So makepackage should probably change: OSVERS=`sw_vers
> -productVersion | cut -d . -f 1,2` to: OSVERS=\$(sw_vers
> -productVersion | cut -d . -f 1,2)
> 
> Similarly throughout the written script.  guiuser is hardcoded to 
> "root", which appears to mean it will get hard-set to "wouter"
> because this: guiuser="`basename \$HOME`" becomes this in the
> shipped package: guiuser="wouter"
> 
> and so the attempt to unload the trigger panel runs as wouter on
> other peoples' machines.

That is so silly that it uses my name.  Turned out to be a problem
with more of the script.  Also with the OSVERS used to install the
user under which it runs.  And a directory removal in the uninstall.

Best regards,
   Wouter

> 
> Aside: It appears that Google's Public DNS service, now that it 
> validates, blocks the functioning of tests such as: 
> http://test.dnssec-or-not.org/ by causing the host itself to not
> resolve.  Well, at least we know something's blocking the
> resolution, even if it's not quite right.  So there's some
> weirdness at this location, yes.
> 
> -Phil
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRdOOYAAoJEJ9vHC1+BF+NiA0P+wTy48NPdRAUOTt/uHM2UrO8
txc6bjOuMn17cCJInfooh/oDLA1qLrZLIrKCkUQH2WQ4SSjHbIOZ+ERapoXjMVsv
QpIB15xNv6fTnIsrIZoszMw0woHICRJ2cGCctBJv4to8HZOvpAtKuZQ7fzZYa8d9
BvUIkJPRWmiPF9732/IqEfTfcyfuTeEv8glNmt9rjEXqsqFy1VzArA9ZlnwxO8Qp
0a3SXJGZXA5jQja9rDakf0K9dz/2etV0BMoQ4N97K+bbDmXGBceiBFqPy/dp0GmN
Dn5ylZEAWoWVA/o4gLSZdWuQ0SnPEH8dYy+YCWVOK6QMK/EmfJbEQTnzTW8zF16v
pdjrA5eIaRWIW3P32KZm91rJfqL9WkVsvs6WW8wX/6juaugESTFp1VZp2woASYPf
RWCwapJXUq6wufMjW44h0Ab7AJOaQxs/z5+aKZXCJn2xoOaG9Cvq8nSaqvbDHLnj
bSjdjsat0ff2emr+KMo6IPpq5t6TmDf14+644ipdJL2vJrroCSgNVFinBKO9eWvB
BbwHx5twvWlKiVeKQFLW0FV6Xkr2hQDsBpjblqZFtjRRebiQcokRrQFtiobR5h5i
LncoiOHmOr4xK+Zz7JD2g7Ejrfg3NcVPKR/Z0fa8vY256HA1xh2n7qDEZwFuXD7P
sJRfduGwXVavJqnbUMP5
=El17
-----END PGP SIGNATURE-----