-
Notifications
You must be signed in to change notification settings - Fork 162
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: Ensure referenced TRC is available #3629
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 0 of 2 files reviewed, 2 unresolved discussions (waiting on @karampok and @oncilla)
a discussion (no related file):
This is one mechanism how TRC updates are disseminated.
what does it mean?
go/lib/infra/modules/trust/verifier.go, line 114 at r1 (raw file):
AllowInactive: true, } if _, err := v.Store.GetTRC(ctx, TRCID{ISD: src.IA.I, Version: src.TRCVer}, tOpts); err != nil {
I find this not very intuitive:
you run a function that will load the correct TRC in the db (is it a blocking operation?)
then you ran another function that will do something (no idea if TRC is being used).
So I would like to see how trc, trcVer,asCert is connected to the verification process.
Something like this
...
trc, err := v.Store.GetTRC()
as, err:= getAS()
if !valid(trc, as){
return error
}
...
alternatively you could put the getTRC call when you actually try to get and use the TRC (inside GetASKey
)
066152f
to
eff8fcb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 5 of 5 files at r2.
Dismissed @karampok from a discussion.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @karampok)
go/lib/infra/modules/trust/verifier.go, line 114 at r1 (raw file):
Previously, karampok (Konstantinos) wrote…
I find this not very intuitive:
you run a function that will load the correct TRC in the db (is it a blocking operation?)
then you ran another function that will do something (no idea if TRC is being used).So I would like to see how trc, trcVer,asCert is connected to the verification process.
Something like this... trc, err := v.Store.GetTRC() as, err:= getAS() if !valid(trc, as){ return error } ...
alternatively you could put the getTRC call when you actually try to get and use the TRC (inside
GetASKey
)
The issuer here is that the source contains two kinds of information,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dismissed @karampok from a discussion.
Reviewable status: all files reviewed, 1 unresolved discussion
When verifying a signature, the verifier now makes sure to have the referenced TRC available locally. This is one mechanism how TRC updates are disseminated.
eff8fcb
to
15ad30d
Compare
When verifying a signature, the verifier now makes sure to have the referenced TRC available locally.
When verifying a signature, the verifier now makes sure to have the
referenced TRC available locally.
This is one mechanism how TRC updates are disseminated.
This change is