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
wrap NTL's BKZ #3232
Comments
comment:1
The attached patch wraps the appropriate NTL functions. It has doctests for all new methods. However, someone more familiar with BKZ might want to add an example (possibly #long) which showcases the difference between LLL and BKZ. |
Changed keywords from none to editor_malb |
comment:3
Ralf forwarded the review request to a colleague of his. I'll ping him again by the end of the week to see what happened. |
comment:4
Ralf, can you review the patch without the forwarding which now seems pointless? |
comment:5
state of affairs for editorial meeting 26/06/08 I didn't hear back from rpw yet. Maybe another referee could jump in. |
Attachment: ntru_2_47.sage.gz NTRU derived lattice, n=47 |
comment:6
Patch applied against SAGE 3.0.3. Works fine, doctests OK. Successfully tested on some cryptographically relevant toy sample lattices (NTRU derived, one is attached, provided by Markus Rückert). Two typos found in documentation:
|
comment:7
w00t, I'll fix the typos today-ish. |
comment:8
To highlight BKZ's features here is a Sage session for the NTRU example rpw provided:
|
addresses rpw's review |
comment:9
Attachment: bkz.patch.gz Typos fixed in updated patch, apply |
comment:10
Merged bkz.patch in Sage 3.0.6.alpha0 |
The BKZ algorithm is a lattice reduction algorithm AFAIK only implemented in NTL.
It enjoys more widespread use in cryptography these days and possibly other areas. Since Sage has Damien Stehle's fast fpLLL library and NTL's BKZ this would make Sage a very nice tool for people who care about these algorithms.
Component: linear algebra
Keywords: editor_malb
Issue created by migration from https://trac.sagemath.org/ticket/3232
The text was updated successfully, but these errors were encountered: