You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed a non-negligible gap between the estimations for the dense sublattice attack embedded in the NTRU primal module when comparing the old and new versions of the tool from https://github.com/WvanWoerden/NTRUFatigue/tree/main
Specifically, I observed the following differences for the case where $n=1024$, $q=65537$, and $\sigma=2$:
Old Version: $\beta = 657$, Time complexity: $2^{214.9}$
New Version: $\beta = 936$, Time complexity: $2^{292.8}$
As we can see, the new version reports a significantly higher value for $\beta$ and a larger time complexity. This raises the question of whether this is due to a more precise analysis or if there is an error in the new implementation.
Questions:
Are there any updates or changes in the assumptions, parameters, or methods in the new version that would explain this significant increase in $\beta$ and time complexity?
Could there be an error in the new version of the tool that caused the discrepancy in the time complexity estimation?
Is there any documentation or clarification available that explains this change in the results?
Looking forward to any insights or explanations regarding this discrepancy.
The text was updated successfully, but these errors were encountered:
I noticed a non-negligible gap between the estimations for the dense sublattice attack embedded in the NTRU primal module when comparing the old and new versions of the tool from https://github.com/WvanWoerden/NTRUFatigue/tree/main
Specifically, I observed the following differences for the case where$n=1024$ , $q=65537$ , and $\sigma=2$ :
Old Version:
$\beta = 657$ , Time complexity: $2^{214.9}$
New Version:
$\beta = 936$ , Time complexity: $2^{292.8}$
As we can see, the new version reports a significantly higher value for$\beta$ and a larger time complexity. This raises the question of whether this is due to a more precise analysis or if there is an error in the new implementation.
Questions:
Looking forward to any insights or explanations regarding this discrepancy.
The text was updated successfully, but these errors were encountered: