You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
import{Buffer}from"../buffer.ts";import{ERR_INVALID_ARG_TYPE}from"../_errors.ts";import{isArrayBufferView}from"../_util/_util_types.ts";exportclassX509Certificate{constructor(buffer: string|Buffer|DataView){if(typeofbuffer==="string")buffer=Buffer.from(buffer);if(!isArrayBufferView(buffer)){thrownewERR_INVALID_ARG_TYPE("buffer",["string","Buffer","TypedArray","DataView",],buffer);}}getsubject(): string{}getsubjectAltName(){}getissuer(): string{}getissuerCertificate(){}getinfoAccess(){}getvalidFrom(): string{}getvalidTo(): string{}getfingerprint(): string{}getfingerprint256(): string{}getkeyUsage(){}getserialNumber(): string{}getraw(){}getpublicKey(){}toString(): string{}// There's no standardized JSON encoding for X509 certs so we// fallback to providing the PEM encoding as a string.toJSON(){returnthis.toString();}getca(): boolean{}checkHost(name,options){}checkEmail(email,options){}checkIP(ip,options){}checkIssued(otherCert){}checkPrivateKey(pkey){}verify(pkey){}}
The text was updated successfully, but these errors were encountered:
This issue seems closely related to a similar request made in denoland/std#981. So we may want to merge them in a unique thread.
Also, as Deno std lib is closely modeled from Go std lib inspiration, https://pkg.go.dev/encoding/pem may also be worth implementing as dealing with PEM is often related to handling X509 certificates.
Node.js docs reference
https://nodejs.org/api/crypto.html#crypto_class_x509certificate
Implementation interface
The text was updated successfully, but these errors were encountered: