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
While the current setup is extremely convenient, it would be preferable - both conceptually and from a performance perspective - to pull the certificates directly from the proxy, especially since Portal gives us that flexibility.
Ideally the replacement is somewhat "drop in":
It should still account for captureCertificatesAsAttachment and attachmentsBypassLimits options
It should still add certs to Scoop.provenanceInfo.certificates
It should still only capture certs once per origin
captureCertificatesAsAttachmentTimeout and crip dependencies would be removed.
Implements #138
---
- Removes `crip` dependency, dedicated certificates capture step and associated options.
- Intercepts certificate chain at `ScoopProxy` level using `socket.getPeerCertificate()` to assemble a PEM on the fly. Runs once per origin.
- Removes duplicate processing of `noarchive` checks
---
**Still working through:** The certificates interception currently happens at `ScoopProxy.onResponse()` level. It should be in `ScoopProxy.onConnected()`, but in some cases it appears to be _"too early"_. TBD, but this version works.
The current implementation of SSL certs capture:
While the current setup is extremely convenient, it would be preferable - both conceptually and from a performance perspective - to pull the certificates directly from the proxy, especially since Portal gives us that flexibility.
Ideally the replacement is somewhat "drop in":
captureCertificatesAsAttachment
andattachmentsBypassLimits
optionsScoop.provenanceInfo.certificates
captureCertificatesAsAttachmentTimeout
andcrip
dependencies would be removed.Progress:
#140
The text was updated successfully, but these errors were encountered: