BIND 10 #577: b10-auth -u and message socket permission

[BIND 10 Development]

#577: b10-auth -u and message socket permission
------------------------------------------+---------------------------
                 Reporter:  jreed         |                Owner:
                     Type:  defect        |               Status:  new
                 Priority:  minor         |            Milestone:
                Component:  Unclassified  |           Resolution:
                 Keywords:                |            Sensitive:  0
Estimated Number of Hours:  0.0           |  Add Hours to Ticket:  0
                Billable?:  1             |          Total Hours:  0
                Internal?:  0             |
------------------------------------------+---------------------------

Comment (by vorner):

 I guess the socket should be readable by the user for these reasons:
  - There are processes started as the user (xfrout, xfrin, zonemgr,
 stats…), they couldn't read it.
  - In the long term, we don't want to start -auth as root either. We want
 the socket creator to be started as root and others just request for
 sockets.

 How did you get the socket that is unreadable? If it is created
 automatically, then it would be a bug.

-- 
Ticket URL: <https://bind10.isc.org/ticket/577#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development