-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TrustStore: Implement TRC fetching/serving #3115
Labels
c/CPPKI
SCION Control-plane PKI
Comments
oncilla
added a commit
to oncilla/scion
that referenced
this issue
Sep 27, 2019
The crypto provider handles crypto material requests. If the requested crypto material is in the database, it is returned. Otherwise, the crypto provider decides based on the recurser whether it can issue a network request. If it is allowed to, it selects the path and remote using the router and calls resolver to resolve all the missing material. This PR is the start of a series of PRs that make the new trust store operational. The individual components are then glued together into the trust store. To the client package, the trust store appears as a single unit. Contributes to scionproto#3115
oncilla
added a commit
to oncilla/scion
that referenced
this issue
Sep 30, 2019
The crypto provider handles crypto material requests. If the requested crypto material is in the database, it is returned. Otherwise, the crypto provider decides based on the recurser whether it can issue a network request. If it is allowed to, it selects the path and remote using the router and calls resolver to resolve all the missing material. This PR is the start of a series of PRs that make the new trust store operational. The individual components are then glued together into the trust store. To the client package, the trust store appears as a single unit. Contributes to scionproto#3115
oncilla
added a commit
to oncilla/scion
that referenced
this issue
Oct 2, 2019
The crypto provider handles crypto material requests. If the requested crypto material is in the database, it is returned. Otherwise, the crypto provider decides based on the recurser whether it can issue a network request. If it is allowed to, it selects the path and remote using the router and calls resolver to resolve all the missing material. This PR is the start of a series of PRs that make the new trust store operational. The individual components are then glued together into the trust store. To the client package, the trust store appears as a single unit. Contributes to scionproto#3115
oncilla
added a commit
to oncilla/scion
that referenced
this issue
Oct 2, 2019
The crypto provider handles crypto material requests. If the requested crypto material is in the database, it is returned. Otherwise, the crypto provider decides based on the recurser whether it can issue a network request. If it is allowed to, it selects the path and remote using the router and calls resolver to resolve all the missing material. This PR is the start of a series of PRs that make the new trust store operational. The individual components are then glued together into the trust store. To the client package, the trust store appears as a single unit. Contributes to scionproto#3115
oncilla
added a commit
that referenced
this issue
Oct 2, 2019
The crypto provider handles crypto material requests. If the requested crypto material is in the database, it is returned. Otherwise, the crypto provider decides based on the recurser whether it can issue a network request. If it is allowed to, it selects the path and remote using the router and calls resolver to resolve all the missing material. This PR is the start of a series of PRs that make the new trust store operational. The individual components are then glued together into the trust store. To the client package, the trust store appears as a single unit. Contributes to #3115
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: