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

dep/verifier: fix eventlog with extra blank chars #443

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Xynnn007
Copy link
Member

Due to definition of AAEL, a ' ' is allowed as part of content field. Thus we now parse the original eventlog string using ' ' as separator to distinguish domain, operation and content only twice, and the things left are treated as the content of the eventlog, including extra ' 's.

Due to definition of AAEL, a ' ' is allowed as part of content field.
Thus we now parse the original eventlog string using ' ' as separator to
distinguish domain, operation and content only twice, and the things
left are treated as the content of the eventlog, including extra ' 's.

Signed-off-by: Xynnn007 <[email protected]>
@Xynnn007 Xynnn007 requested a review from sameo as a code owner July 17, 2024 02:08
Copy link
Contributor

@mkulke mkulke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a negative test? or even more tests to spec out the log format a bit more (like can we use unicode/emojis in domain and operation, is "my domain" w/ quotes accepted, etc..

deps/verifier/src/eventlog/mod.rs Show resolved Hide resolved
@Xynnn007
Copy link
Member Author

Xynnn007 commented Aug 2, 2024

Maybe add a negative test? or even more tests to spec out the log format a bit more (like can we use unicode/emojis in domain and operation, is "my domain" w/ quotes accepted, etc..

yea, I think you raise really good points that we do not have a spec for the eventlog format. Initially I think it should be letters and numbers, the domain/operation should not have any blanks. Maybe we should make an issue to sync a spec for this, and then publish it on CoCo website due to confidential-containers/confidential-containers#225 (comment) ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants