Re: [PATCH v2 0/1] MR4667: bcrypt: Initialize variable in all cases (Coverity)

[Fabian Maurer (＠DarkShadow44)]

On Sun Dec 10 23:28:12 2023 +0000, Hans Leidekker wrote:
> There should always be either a public key or a private key, or both. If
> both branches can be false that's the bug that should be fixed.

Alright, I added another branch for this error condition. I mean, it should never happen, but IMHO we could still check for it instead of silently corrupting memory should it happen.