-
Notifications
You must be signed in to change notification settings - Fork 982
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
[v1.9.x] do not panic when loading a V2 CA certificate #1279
base: release-1.9
Are you sure you want to change the base?
Changes from 1 commit
6fc2dfe
6be1c10
13f2971
11648f8
40b6925
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -237,6 +237,8 @@ func loadCAPoolFromConfig(l *logrus.Logger, c *config.C) (*cert.NebulaCAPool, er | |
return nil, errors.New("no valid CA certificates present") | ||
} | ||
|
||
} else if errors.Is(err, cert.ErrInvalidPEMCertificateUnsupported) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We should ensure there is at least 1 valid CA in the pool otherwise it won't work There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We do a few lines up. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We did not. Added. |
||
l.WithError(err).Warn("At least one configured CA is unsupported by this version of nebula. It has been ignored.") | ||
} else if err != nil { | ||
return nil, fmt.Errorf("error while adding CA certificate to CA trust store: %s", err) | ||
} | ||
|
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.
Kind of a wild situation but we could have an expired and a too new cert and we wouldn't know about the too new one until the expired one was removed.
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.
I read this yesterday with "too new" meaning "current time is before notBefore". I get it now lol. I didn't want to change the semantics of this function to handle it, but maybe I actually should? Passing a logger in would let us tell the user which CA is too new.
Or we bubble the bools up? I don't really like that.
Or a "expired-and-too-new-present" error? Also gross.
Maybe
return pool, hasExpiredCerts, err
is the way to go?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.
I was thinking maybe we hold back one of the errors and if the other appears then we wrap that. Then we can check if the error appears in the chain instead of direct equality.
It would be a bummer to log from this here IMO
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.
@wadey suggested
(pool CAPool, warnings []error, err error)
so I gave that a try. It feels pretty nice. Checking a return value other thanerr
first feels illegal, but it's still anerror
so it's okay.