svcprop of PGs with read_authorizations are ugly
If you svcprop a pg with a read authorization, and you lack that authorization, the first property name and type are available to you, but the value is not (this is in my testing usually the read_authorization property, but I'm not sure it has to be)
So you get output like:
svcprop -p pkg_secure pkg/server svc:/application/pkg/server:nightly-nd/:properties/pkg_secure/read_authorization astringsvcprop: Permission denied.
svcprop should, at the least, get the error message onto a fresh line if it occurs mid-property.
Also, arguably, a read-protected property group should either be readable, or not readable, rather than having readable keys but unreadable values (we'd have to look at the original read_authorization spec to figure out if that's reasonable).