This bug is really simple, it's just a matter of a typo in the code.

Example of the incorrect error message that gets shown to users:

Worth mentioning, this only affects which driver version is displayed to the user, not what version Sodium actually uses for determination.

Also, we probably want to backport this to affected versions, because it's a really stupid bug that confuses a lot of people.