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
Private gateways don't need the identity certificate of their public peer, but we're still storing as a "leftover" from the days when we used to encrypt cargo with that certificate (before integrating the Channel Session Protocol).
The only thing we need from that certificate is its public key, so that we can:
Issue Cargo Delivery Authorisations (CDAs)
Compute the public gateway's private address
The text was updated successfully, but these errors were encountered:
Private gateways don't need the identity certificate of their public peer, but we're still storing as a "leftover" from the days when we used to encrypt cargo with that certificate (before integrating the Channel Session Protocol).
The only thing we need from that certificate is its public key, so that we can:
The text was updated successfully, but these errors were encountered: