-
Notifications
You must be signed in to change notification settings - Fork 103
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
remove unneeded rsa references, upgrade krypto #2101
remove unneeded rsa references, upgrade krypto #2101
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.
What about
launcher/pkg/osquery/extension.go
Line 221 in df315fe
// 1. The RSA key. This is stored in the launcher DB, and was the first key used by krypto. We are deprecating it. |
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.
Seems scary, but I think this is something nightly
will test fine. As long as we can manage auth flows, I think we're good.
// There are 3 keys: | ||
// 1. The RSA key. This is stored in the launcher DB, and was the first key used by krypto. We are deprecating it. | ||
// 2. The hardware keys -- these are in the secure enclave (TPM or Apple's thing) These are used to identify the device | ||
// 3. The launcher install key -- this is an ECC key that is sometimes used in conjunction with (2) |
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 think this comment is old -- we don't generate the ECC keys in this function. Thus it's removal is safe
8b9811b
K2 & Krypto PRs
https://github.com/kolide/k2/pull/11371
kolide/krypto#47