K
KR
I'm (newly) working in a corporate environment, and have not had any
experience with security certificates. We have a solution to something we
want to do in powerpoint, but it requires VBA. Our corporate install of MS
office has all MS Office programs' VBA security set to "high" by default.
One option would be to instruct every user to go in and change their VBA
security to medium, and enable macros when opening our file. I'm hoping that
if I learn about security certificates, there might be an easier way.
Questions:
------------
1. If we create a certificate and sign the file, does each PC have to accept
that certificate, or is it possible to (potentially) have an IT department
change a setting (registry or whatever) so all PCs will then automatically
accept that certificate?
2. Will each user has to accept the certificate, will they even be prompted
if the security is already at high, or will they have to set their VBA
security to medium in order to get asked whether or not to accept the
certificate?
3. I understand that certificates are designed to prevent multiple users
from being able to create identical certificates (otherwise they would be
easier to duplicate/hack). We have multiple developers- what would be the
best approach to having all our stuff accepted (e.g. certificates) while
minimizing the need for users to click to add 6+ different certificates as
"safe"?
Many thanks,
Keith
experience with security certificates. We have a solution to something we
want to do in powerpoint, but it requires VBA. Our corporate install of MS
office has all MS Office programs' VBA security set to "high" by default.
One option would be to instruct every user to go in and change their VBA
security to medium, and enable macros when opening our file. I'm hoping that
if I learn about security certificates, there might be an easier way.
Questions:
------------
1. If we create a certificate and sign the file, does each PC have to accept
that certificate, or is it possible to (potentially) have an IT department
change a setting (registry or whatever) so all PCs will then automatically
accept that certificate?
2. Will each user has to accept the certificate, will they even be prompted
if the security is already at high, or will they have to set their VBA
security to medium in order to get asked whether or not to accept the
certificate?
3. I understand that certificates are designed to prevent multiple users
from being able to create identical certificates (otherwise they would be
easier to duplicate/hack). We have multiple developers- what would be the
best approach to having all our stuff accepted (e.g. certificates) while
minimizing the need for users to click to add 6+ different certificates as
"safe"?
Many thanks,
Keith