Re: MS Certification Authority Question
hmmm... an interesting problem, that I think sadly has no answer.
certs are signed to say that the issuing authority, (the computer) is secure, not that the development team are secure...
the only things that I can suggest are.
use multiple certs and install the certificates on the departments PCs using group policies so that take a lot of the work out of it.
or finish all the documents /macros etc with a build machine, then it's only that one machine that will need to have a certificate.
this works well with most software development teams as there is usually a 'head' coder/team leader who will quality check the code or compile final executables etc anyway.
I'm assuming that all your code is tested before it's delivered, so you could make signing the code a final step of your test process, i.e functionality is signed off and then the documents are signed on a single test machine or something.
I didn’t fight my way to the top of the food chain to be a vegetarian…
Im sick of people saying 'dont waste paper'. If trees wanted to live, they'd all carry guns.
"The inherent vice of capitalism is the unequal sharing of blessings; The inherent vice of socialism is the equal sharing of miseries."