Re: golang-go.crypto / CVE-2019-11841
Ola Lundqvist <email@example.com> writes:
> Do we have an idea on how a good patch would look like?
OK, I think a patch may not be as simple as I hoped.
CheckDetachedSignature() is where we decode the packet and determine the
hash function used.
But this function is not supplied the headers so it cannot check the
headers. And this function doesn't return the hashFunc used either, so
the calling function cannot check the headers.
Plus the hashFunc is an integer it needs to be decoded into a string -
there is a private function - nameOfHash - that does this.
So some sort of API change is required I think.
I am a bit disappointed actually that the CheckDetachedSignature()
doesn't return the hash used. It means that the calling application only
has access to the insecure value that cannot be trusted.
Brian May <firstname.lastname@example.org>