-
Notifications
You must be signed in to change notification settings - Fork 66
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
New name for the CoCo Attestation project #250
Comments
I think you're right that we need a new name. I like AAA. I have two potential concerns. First, it sounds fairly similar to AA, as in Attestation Agent. Second, I wonder if it sounds too generic. If the idea is for the KBS to catch on outside of CoCo, we might want a slightly more unique name. What do you think about A3? To me it sounds a bit cooler but that might be subjective. |
AAA is nice but unfortunately, at least in security circles, already taken... |
What about |
Just a thought, How about But one concern is we need to right description of the meaning :-) |
Or simply "OpenKBS” ? |
The current state is because of an accidental push (that's what I was told). Before going into the repo naming discussion, we need to agree on the final structure. That topic was not finished properly. |
how about UAH(Universal Attestation Hub)? |
What about AAAA or A4? We just add Attestation onto the existing three As |
Please something that is searchable (bing/google). A proper name first, then an abbreviation of that. And the name should contain more than just generic terms. |
Why not use the descriptive and searchable term "attestation service"? It's namespaced by the CoCo project, so you could reference to it as "CoCo Attestation Service" to differentiate. Arguably the scope of what's in the repo is larger than that, but the main substance is attestation. |
This gives me an idea. |
Ok, I'll rename the repo to Steam-Boaty-McAttestation-Face |
I like names that aren't simple acronyms. :) Stamp seals were used on ancient times to authenticate documents. Then I tried to derive some names from seal:
|
cereal 🥣 "confidentiality-enhanced remote attested ledger" or alternatively "confidentiality-enabling remote attestation library" /s |
OpenATA I think this name is professional and beautiful, which well describes the core goal and logic of this repository, that is, "a complete architecture level solution around Attestation technology". BTW, this name will help us to publicize and promote this project as an independent open source solution on different occasions. In addition, up to now there are no other open source projects with this name, which is a good starting point. |
Suggestions:
|
ProofRock - It's proof, it's a rock, and it's a reference to a great poem. |
CASPR: Confidential Attestation Service for Protected Resources Casper is a friendly ghost, trusted and loved, who often acts as an (invisible) protector of others. and he's fun ;-) |
Please see the poll discussion #302 :-) |
offtopic: I was wondering if we could find a Greek word (following Kubernetes etc) and looked for 'trust'. Looks like that's where Kata containers comes from (I did not know that!). |
IMO that's a great idea (albeit, admittedly the practice is a bit eurocentric): There would be "Pistos" (πιστός) ~ faithful, trustworthy And maybe "Fides" (Pistis, πίστις), a roman-greek goddess of trust |
We finished the poll here, The results show a tie between Trustee and CEREAL, but the last vote for CEREAL came in after we were supposed to have closed the poll (the start of the community meeting), and after we had actually announced the results. Of course we could do another poll with just those two options, but for the sake of everyone's sanity I think Trustee is the answer. Now the question is how we actually go about renaming things |
@fitzthum Maybe we could raise this up in this week's meeting and rename with folks watching :P |
+1 |
With the continuous improvement of the CoCo Attestation project, there is a growing demand to apply it in scenarios outside of CoCo, or to use only certain components (such as using Attestation-Agent to connect to other Attestation-Service). In fact, since the first day of designing the CoCo Attestation project, the project maintainers have anticipated this situation. Welcome everyone to submit their ideas here: https://doodle.com/meeting/participate/id/eEZ7g7ka.
However, before making the CoCo Attestation project more popular, we need to give it a better name to prevent "KBS" (Key Broker Service), which is a temporary name resulting from rebasing related repositories, from becoming the final name. The new name should reflect the inclusiveness and scalability of CoCo Attestation. The highest level of inclusiveness means that CoCo Attestation can even support attestation technologies beyond trusted execution environment attestation (such as build attestation, sbom attestation, platform attestation, etc.); Scalability has already begun to occur, for example, attestation needs to be integrated with traditional identity authentication and authorization, making the device identity for the TEE instance being the one of authentication and authorization factor.
An alternative name I propose is "AAA" (Attestation, Authentication, Authorization). I know that KBS in "AAA" also includes the functionality of storing sensitive information, but this is not the primary and unique capability of "AAA", so I prefer to highlight and emphasize the key features of CoCo Attestation in the new name.
@fitzthum @sameo @confidential-containers/kbs-maintainers @confidential-containers/attestation-agent-maintainers @confidential-containers/attestation-service-maintainers
The text was updated successfully, but these errors were encountered: