Skip to content
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

Seperate out CFSSL server components from cf_impl_cfssl #145

Closed
lukehinds opened this issue Aug 30, 2019 · 7 comments
Closed

Seperate out CFSSL server components from cf_impl_cfssl #145

lukehinds opened this issue Aug 30, 2019 · 7 comments
Milestone

Comments

@lukehinds
Copy link
Member

lukehinds commented Aug 30, 2019

Currently CFSSL is automatically set up and run from ca_impl_cfssl.py

I think we should separate out the server components start_cfssl and stop_cfssl and instead just have the ip and port configurable and the operator runs their own cfssl instance wherever they like (it might be on a different host to the keylime_verifier), perhaps behind its own firewall etc. Either way I don't think it should not be possible to run it separately.

In time we should also look to make CA's plugable, so different PKI systems can be utilised.

@jetwhiz @nabilschear - any objections to the above? If not I will give it a key_feature label.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.94. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@nabilschear
Copy link
Contributor

i think this sounds like a great idea. We were trying to make the cert support pluggable already, but it was mostly to fix the limitations of openssl (i.e., no crl support in m2crypto). A new look at what the interface should look like might be in order.

@lukehinds lukehinds added the key_feature immune from stale bot. label Sep 2, 2019
@lukehinds lukehinds added this to the 5.1 milestone Sep 12, 2019
This was referenced Sep 30, 2019
@lukehinds
Copy link
Member Author

lukehinds commented Apr 3, 2020

This might be an interesting one for you @bu3alwa , let me know if you want to chat it over and understand more.

@bu3alwa
Copy link
Contributor

bu3alwa commented Apr 4, 2020

@bu3alwa
Copy link
Contributor

bu3alwa commented Apr 10, 2020

Should making the ca cert be decoupled from keylime as well? Since we want the ca implementations to be a plugin to be added the mk_cacert() shouldn't be a called in ca_util.py:cmd_init(). Instead, it should just grab the ca cert from the api. Is this a safe thoughtprocess to move forward with?

@nabilschear
Copy link
Contributor

Should making the ca cert be decoupled from keylime as well? Since we want the ca implementations to be a plugin to be added the mk_cacert() shouldn't be a called in ca_util.py:cmd_init(). Instead, it should just grab the ca cert from the api. Is this a safe thoughtprocess to move forward with?

that sounds good.

@THS-on
Copy link
Member

THS-on commented Jun 3, 2022

#1012 removed CFSSL support.

@THS-on THS-on closed this as completed Jun 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants