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

Update Security Considerations to not use BCP14 keywords #323

Open
SteveLasker opened this issue Dec 16, 2024 · 1 comment
Open

Update Security Considerations to not use BCP14 keywords #323

SteveLasker opened this issue Dec 16, 2024 · 1 comment

Comments

@SteveLasker
Copy link
Collaborator

From @mcr
https://mailarchive.ietf.org/arch/msg/scitt/sOGI7xcUaOJx5Zag8uqsygooLrc/

Please do not use BCP14 keywords in the Security Considerations.
SC should instead always reference some section in the Protocol specification where that was said, while explaining what threat was being mitigated.

Like the bit about TEEs, and the other bit about consensus algorithms, and finally the self-statements (Attestation results I guess?) about the TCB.
"Redundant Replicas" ought to be an entire section on it's own.

"remote attestation Evidence was appraised by a Relying Party "
HENK! Evidence iis appraised by a Verifier :-)

person-in-the-middle is not a term that I proposed in
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-richardson-saag-onpath-attacker%2F&data=05%7C02%7C%7Ce9ee8d279969424877f708dd1ba04c88%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638697097466980054%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=UgSf4s3sv%2BirzoyYbc%2BRTq0Mx92uor3HwvCDzbQq8UM%3D&reserved=0

some of have proposed MITM be expanded now to:
*Meddler" in the Middle

(if cookies are the thing being stolen, then "Monster in the Middle".
This, btw, is a nom-nom-nom attack. Coming to an I-D repo near you)

@mcr
Copy link

mcr commented Dec 23, 2024 via email

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

3 participants
@mcr @SteveLasker and others