Skip to content

Conversation

@huitema
Copy link
Contributor

@huitema huitema commented Jul 7, 2022

Not really sure that we have to do that, but I did it anyhow.
Also fixed a couple of random line length issues that were causing errors in xml2rfc

@martinduke
Copy link
Contributor

Thanks for doing this. One comment:

I don't think the Security Considerations section here fully captures our doubts about the need for this. IIRC, the 4-pass is only vulnerable to known-plaintext attacks, which seem hard to mount here. And as you state, if the consequence is the attacker discovering that the CID is not random, it's not obvious to me that it's a serious problem.

@martinduke
Copy link
Contributor

Per offline discussion with @huitema: we are disinclined to include this in the draft, because we don't think people will implement it. We will keep it around in case reviews demand it, but have no plans to merge.

@huitema
Copy link
Contributor Author

huitema commented Jul 8, 2022

@martinduke the latest commit have resolved potential merge conflicts between this PR and the main branch, making it easier to "pull the PR off our back pocket" if we really have to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants