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
md2: test doesn't require direct low level access #10821
Conversation
Do we test md2 with evp_test? In that case, I see no use for this test program and would simply throw it away. |
Should we though have in place something that is testing that the legacy low level API is still working? (I see this is not the case anymore for this PR, but I am just wondering about the risk of losing coverage on the ancient API) |
We don't seem to have any other MD2 tests. This test is unchanged by the deprecation work -- i.e. the low level APIs were not tested previously. |
My suggestion would be to copy the test vectors to the appropriate evp_test input file, and refractor this one into testing the low-level API. Otherwise, this program is just redundant cruft. |
I'm more inclined to copy the test cases to EVP and just remove this one. |
Sure. After all, that should still test the low level stuff, just via EVP |
73c9198
to
6371cf8
Compare
The low level calls will be as well tested as they were :) I've pushed the changes. |
Approval is, of course, as long as CIs agree |
The test can be moved into the EVP tests and the separate executable removed.
6371cf8
to
e53a2bf
Compare
CI failure was relevant. Forgot to delete |
@levitte this will need a new approval -- the only change is the file deletion. |
MD2 is disabled by default, isn't it? So of course, only the jobs that enable it explicitly will get failures... |
The test can be moved into the EVP tests and the separate executable removed. Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from #10821)
Merged to master with one end of line space removed. |
Low level access isn't required beyond the block size which remains available.