Add support for EC keys #3
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "ec-key-support"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Didn't find replacement for forge.pki.certificateToAsn1() and forge.asn1.toDer().
formatPEM.js
andpkcs12chain
, where are they from, why aren't they installed vianpm
and are you surepki.js
orasn1js
doesn't already provide this? Whenever you pull in external files please add them in separate commit and add into commit description where they came from and why they were addedHASH_ALG
,RSA_SIGN_ALG
,EC_SIGN_ALG
,KEY_SIZE
should all really go away and they should be pulled from/api/bootstrap
instead. Looks like at least hash algorithm is missing, please add it undercertificate.authority
dict. There's more hardcoded stuff that should really be pulled from/api/bootstrap
https://git.k-space.ee/pinecrypt/frontend/src/branch/master/static/js/certidude.js#L250case 'p12':
pki.js
orasn1js
doesn't include what you needcrypto.generateKey
is the only long running function call, I don't see reason to complicate code withsequence
here?PKI terminologiy is a mess, to clarify:
----- BEGIN ... -----
and----- END ... -----
Did you test downloading StrongSwan profile (.sswan)? It should contain sensible JSON and the
local.p12
attribute should contain P12 bundle that you should be able to parse withopenssl pkcs12
. For more info see https://wiki.strongswan.org/projects/strongswan/wiki/AndroidVPNClientProfilesbe409827f5
tobaa6acbf77
f4768689ba/examples/examples_common.js
.pkcs12chain.js wraps boilerplate for generating a PFX instance with a cert chain, comes from https://github.com/PeculiarVentures/PKI.js/issues/104.
Change
to