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

Finer grained attack hierarchy? #5

Open
defeo opened this issue Aug 16, 2022 · 4 comments
Open

Finer grained attack hierarchy? #5

defeo opened this issue Aug 16, 2022 · 4 comments

Comments

@defeo
Copy link
Contributor

defeo commented Aug 16, 2022

It could be useful to have a finer hierarchy than just poly < subexp < exp. For example, both Delfs-Galbraith and Biasse-Jao-Sankar break the isogeny path problem in quantum exponential time, but the latter is preferred (and so far not showing up in the row, because of the ordering in the .yml file).

@GiacomoPope
Copy link
Contributor

One option would be to use approximate L notation for all attack strengths for easy ordering. Dunno how realistic this would be for total coverage though, but would help order the various exp / subexp complexities.

@defeo
Copy link
Contributor Author

defeo commented Aug 16, 2022

Yup, should be doable to keep track of exponents in poly, L, exp complexities. Should suffice to capture most clashes. It's a lower priority, though.

@defeo
Copy link
Contributor Author

defeo commented Aug 17, 2022

I added support for writing complexities in the L(a,c) notation. Not closing this issue because one could still do more (e.g., it's not clear why vOW is better than MITM, with this notation), but I don't anticipate doing so.

@GiacomoPope
Copy link
Contributor

This is cool! Agree about the finer finer grained details of things like space / time complexity. If I have a smart idea I'll come back here but nothing comes to mind without creating too much complicated notation (unless memory was somehow backend only to allow selection for best attack)

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

2 participants