Bill Price wrote:
Can someone post (or reference) sample code showing how to use JSS to create
a PKCS #12 for a RSA key and certs held in the internal token? I am having
trouble getting the private key into a keybag, safecontents, and
authenticated safes. I have seen the example of creating
I was looking at how the password was getting converted to bytes today.
The PKCS12 spec (downloaded from
http://www.rsa.com/rsalabs/node.asp?id=2138, page 14) says the password
bytes are BMPStrings with a null terminator and no byte order marks. It
shows a sample password of Beavis and the bytes
Eddy Nigg (StartCom Ltd.) wrote:
Could you please be so kind and provide me with the a URL or document of
the audit attestation of KPMG and what exactly it entails including
under which criteria the CA was audited?
The criteria were ETSI TS 101.456, as I believe I mentioned in the bug
Hi Frank,
I've visited that page you are pointing me obviously. However this page
also says:
The standards ETSI TS 101.456 (Europe) and ANSI X9.79 (USA, Canada)
*may* also serve *as a basis* for the certification of a Public Key
Infrastructure (PKI) respectively a Certification Service
Frank Hecker wrote:
Yes, the later would be my concern (ETSI TS 101.456 as the relevant
criteria according to the Mozilla CA policy as opposed to ZertES as
the criteria).
From our point of view it would be perfectly fine if the audit criteria
encompassed both ETSI TS 101.456 and
Eddy Nigg (StartCom Ltd.) wrote:
I've visited that page you are pointing me obviously. However this page
also says:
The standards ETSI TS 101.456 (Europe) and ANSI X9.79 (USA, Canada)
*may* also serve *as a basis* for the certification of a Public Key
Infrastructure (PKI) respectively a
Hi Frank,
Could you please be so kind and provide me with the a URL or document of
the audit attestation of KPMG and what exactly it entails including
under which criteria the CA was audited?
--
Regards
Signer: Eddy Nigg, StartCom Ltd. http://www.startcom.org
Jabber: [EMAIL
Eddy Nigg (StartCom Ltd.) wrote:
Yes, I saw that under Certification Service Provider (CSP)...so if I
understand you correctly, the standards listed under this section were
the requirements used for the audit. In that case it's most likely that
they do have a document confirming that by
--- Comment #39 from Nelson Bolyard
(In reply to comment #38)
Would it be possible to provide us with a URL or document of
the audit attestation by the auditor?
I believe that should be (is?) a requirement.
Ideally it would be a URL from the auditor's web site.
As I have
Eddy Nigg (StartCom Ltd.) wrote:
As I have mentioned previously on this list and in private, for various
reasons I'd like to suggest to change the procedures and the process of
CA root requests to require an official request made by the CA in real
paper by registered postal mail, which
Hi Frank,
Frank Hecker wrote:
The Details SwissSignAG page seems pretty clear that ETSI TS 101.456
was (one of) the criteria used in the audit.
Yes, I saw that under Certification Service Provider (CSP)...so if I
understand you correctly, the standards listed under this section were
the
The CA/Browser Forum (a.k.a. CABForum), the same people who devised EV
certificates for SSL/TLS servers, are now working on defining EV for
code signing. They're really working on defining code signing, what it
means, how it works, etc. They're addressing such fundamental issues
as whether
Eddy Nigg (StartCom Ltd.) wrote:
As I have mentioned previously on this list and in private, for various
reasons I'd like to suggest to change the procedures and the process of
CA root requests to require an official request made by the CA in real
paper by registered postal mail, which
13 matches
Mail list logo
