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
In #113 (comment) a framework was announced and described as "work in progress". To my knowledge no details about this framework has ever been published. Hence it is very unclear where these efforts stand and how much is still needed to complete this. Can we learn the progress already made and see what is still needed?
The reason why I ask is that I have a number of new tests written against a variety of libraries (mostly, rust, python and javascript) and that it would make sense to organize these tests and combine them with the tests written for Wycheproof (i.e. Java and C++).
Additionally, I would be open to contribute to alternative projects that collect and organize test results (E.g. something like cargo-crev but for automatic testing).
The text was updated successfully, but these errors were encountered:
As a quick and simple alternative to a review system, a web page maintaining an up-to-date list of implementations that include the Rooterberg/Wycheproof test vectors in their test suites (along with details about the language, algorithms, versions of test vectors, etc.) would be very useful.
In #113 (comment) a framework was announced and described as "work in progress". To my knowledge no details about this framework has ever been published. Hence it is very unclear where these efforts stand and how much is still needed to complete this. Can we learn the progress already made and see what is still needed?
The reason why I ask is that I have a number of new tests written against a variety of libraries (mostly, rust, python and javascript) and that it would make sense to organize these tests and combine them with the tests written for Wycheproof (i.e. Java and C++).
Additionally, I would be open to contribute to alternative projects that collect and organize test results (E.g. something like cargo-crev but for automatic testing).
The text was updated successfully, but these errors were encountered: