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

Doc inconsistency in UDS vs UDS seed #191

Open
varuns-nvidia opened this issue May 3, 2024 · 3 comments
Open

Doc inconsistency in UDS vs UDS seed #191

varuns-nvidia opened this issue May 3, 2024 · 3 comments

Comments

@varuns-nvidia
Copy link
Contributor

Should consistently refer to UDS as the output of de-obfuscation and UDS seed as the input.
@FerralCoder , @bluegate010 for thoughts before we jump on this.

@FerralCoder
Copy link
Contributor

I would agree with that suggestion. @JohnTraverAmd do you agree as well? I do think that we should always refer to the fused value as UDS Seed, and only the value after de-obfuscation as UDS.

That said, the UDS Seed itself should still be generated following rules for generating a NIST compliant UDS.

@JohnTraverAmd
Copy link
Contributor

I think that the input to the obfuscation should be called obfuscated UDS while the output is called UDS.
UDS Seed may not make sense at this point. What is the point of creating a term for UDS-Seed? I think that if anything, we are creating an IDevID Seed.

@bharatpillilli
Copy link
Contributor

bharatpillilli commented Aug 8, 2024

If we call it obfuscated UDS, someone will ask how is Caliptra or manufacturing obfuscating the value (infact some folks were already asking this when we stated UDS deobfuscation). So it is better to keep it as UDS seed IMHO.

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

No branches or pull requests

4 participants