certificate

问题 I have problem with loading certifiacate to key store. I can create that certificate in console with this command openssl pkcs12 -export -out cloudCA.p12 -inkey Cloud\ privateLey.key -in cloudCa.pem -certfile rootCa.pem -name "cloudCA" I figured out how to load cloudCA.pem with privateKey.key but I can't find a way how to add there rootCA.pem. This is my current code. Thank 's for help. //Regular patterns for certificate. private static final Pattern CERT_PATTERN = Pattern.compile( "-+BEGIN\

问题 my situation: I am working on a application that is using openssl and rsa-certificates for secure communication with other parties. so we need to exchange certificates. so far so good. mostly the partners certificate is a from a CA signed certificate (not a root certi or a selfsigend certi). on my notebook (debian) I have from the distribution the most common rootCA-certificates installed in my openssl infrastrucutre. so I can verify the most partner-certificates because I have the issuer

问题 I am a newbie for Objective C. I am working on chained certificates in iOS for VPN connection. My problem statement is I need to implement user-cert based VPN connection. I have the working VPN connection model for the normal certs that is without chained certificates and it is working fine. But when I use chained certificates it is not connecting. I am using 3 intermediate certificates that are self signed and a .p12 certificate. I have imported .p12 certificate programmatically into iOS app

问题 I have a server application and a client application. The server uses https, and has a .jks file. Apart from that, I use authentication with login and password. I wonder if the client side should use a .cert certificate. I thought the client's certificate should match servers certificate, but it seems that I was wrong. I have some troubles understatding the topic, so please be understanding. 回答1: Keystore A Java KeyStore (JKS) is a repository of security certificates – either authorization

问题 I have a server application and a client application. The server uses https, and has a .jks file. Apart from that, I use authentication with login and password. I wonder if the client side should use a .cert certificate. I thought the client's certificate should match servers certificate, but it seems that I was wrong. I have some troubles understatding the topic, so please be understanding. 回答1: Keystore A Java KeyStore (JKS) is a repository of security certificates – either authorization

问题 I am trying to secure a self hosted service. Calling the service returns this: The underlying connection was closed: An unexpected error occurred on a receive. The service endpoint looks like this <endpoint address="https://MACHINE:8010/rest/users" binding="webHttpBinding" bindingConfiguration="certificate" contract="Online.DomainObjects.Remote.IUserManagerRemote" /> I have done this to open up access: netsh http add urlacl "url=https://+:8010/" user=BUILTIN\Users I have turned WCF tracing on

问题 Few month ago a was able to successfully sign CAB file with test certificate I have created on my server. Here are the steps I have taken: makecert.exe -sv "Demo.pvk" -n "CN=Demo Company,E=demo@gmail.com" "Demo.cer" cert2spc.exe "Demo.cer" "Demo.spc" pvk2pfx.exe -pvk "Demo.pvk" -pi "pvk_password" -spc "Demo.spc" -pfx "Demo.pfx" -po "pfx_password" signtool.exe sign /f "Demo.pfx" /p "pfx_password" /v "D:\Setup.cab" All the steps are successfull except the last one with signtool that returns:

问题 In Apple's Doc, generateIdentityVerificationSignatureWithCompletionHandler, you are to concatenate into a data buffer 4 parameters, one of which being "The timestamp parameter in Big-Endian UInt-64 format ", and then generate a SHA-1 hash value for verification. Has anyone accomplished this successfully in Node.js/Javascript? The main issue I am having is that Javascript/Node.js does not seem to have any support 64-bit unsigned big endian integers; it seems to max out at 32-bit, unsigned. PS:

问题 In Apple's Doc, generateIdentityVerificationSignatureWithCompletionHandler, you are to concatenate into a data buffer 4 parameters, one of which being "The timestamp parameter in Big-Endian UInt-64 format ", and then generate a SHA-1 hash value for verification. Has anyone accomplished this successfully in Node.js/Javascript? The main issue I am having is that Javascript/Node.js does not seem to have any support 64-bit unsigned big endian integers; it seems to max out at 32-bit, unsigned. PS:

问题 In the past, I had to codesign a .dmg file. The old certificate has since expired, and I have a new one to sign with. No problem, right? Do what I did last time? Yes. I exported the new certificate chain and private key as a .pfx file, in windows. It would seem I can import that directly into the OS X keychain tool, without converting to .p12 first. So I did. When it comes time to actually codesign, first try says it can't determine which certificate to use. So I put the old certificate chain