Is your feature request related to a problem? Please describe.
Return the input primitive as a recommendation if the recommended primitive would have the same or similar level of security.
Describe the solution you'd like
For example, currently the user might have a SHA3-256 and assessing its compliance, they might get recommended the SHA256. In most cases this would not be necessary and thus it might be better to return SHA3-256 instead, explicitly encoding that a switch need not be made.
Describe alternatives you've considered
Leave things as is. In most cases the default recommendation is a widely used primitive such as SHA256 that has been around longer and thus might have better hardware and library support than newer primitives (notwithstanding issues around its lack of resistance against length extension attacks in this particular case).
Is your feature request related to a problem? Please describe.
Return the input primitive as a recommendation if the recommended primitive would have the same or similar level of security.
Describe the solution you'd like
For example, currently the user might have a
SHA3-256and assessing its compliance, they might get recommended theSHA256. In most cases this would not be necessary and thus it might be better to returnSHA3-256instead, explicitly encoding that a switch need not be made.Describe alternatives you've considered
Leave things as is. In most cases the default recommendation is a widely used primitive such as
SHA256that has been around longer and thus might have better hardware and library support than newer primitives (notwithstanding issues around its lack of resistance against length extension attacks in this particular case).