should config be protected?
Right, will be in my next patch set.
Was this issue fixed?
Actually no, because I promised something I actually never did. It _was_ already config protected. Must have been a local problem.