https://bz.apache.org/ooo/show_bug.cgi?id=126891
--- Comment #35 from orcmid <[email protected]> --- (In reply to orcmid from comment #33) > > Ah, so. The built-in help on Windows is different. It says, under > "Managing Your Certificates", > > If you are using Microsoft Windows, you can manage your certificates > from the Control Panel applet "Internet Options" on the "Contents" > tab page. Import your new root certificate into the Trusted Root > Certification Authorities list. > > In reality, the certificate generation process between the CA and a Windows > PC computer happens with the browser (unless you use Symantec which has now > screwed this up royally.) The above procedure only really applies if you do > a self-issued cert. And in the case, the cert ends up in the certificate store and the Import statement is unnecessary. I should be clear. The above remark on certificate generation is with respect to the certificate generation process for email certificates. These work and I would expect that to be the avenue of choice for also signing Microsoft Office (ooxml and odf) and Apache OpenOffice (odf) documents. SSL and code-signing certificates arrive via other mechanisms. Also the "Trusted Root Certification Authorities" list is only for installing CA certificates and that's completely not what we are talking about here. So even the simpler Windows statement is off-base. -- You are receiving this mail because: You are the assignee for the issue.
