Actually, because of Hudson project based matrix authorization is additive, it's
not possible to do what we need :

Anonymous can view, create, configure, build... a job expect for one job.
For this specific job, just some users can configure, build this one.

We need that Hudson project based matrix authorization is restrictive. We don't
want to always add all authorization for anonymous user for each new job.

One possibility is to be able to choose between additive or restrictive
permission for project based matrix authorization in Hudson configure system panel.

cf. mailing list hudson-user :
http://www.nabble.com/Project-based-Matrix-Authorization-Strategy-td24940667.html