Can't get *.r2rwm working, saying “Signature verification failed!” when executing using Wine. Tried multiple releases by R2R on sister site.
I know R2R System is not for Linux though, any help is appreciated.
I'm using Arch Linux BTW.

 

Same here! Don't hesitate to keep us updated if there's anything new

 

It seems there are troubles on Windows 11 too ... It may not be related to Linux itself.
Didn't seen any fix for now.

 

What are the issues in Win11?
I'm still on the interimistic r2r Network runtime and thought I might upgrade to the latest r2r system this week. Shall I wait for the next version?

 

The user Karnot posted this under TEAM R2R System v1.0.2-R2R on the sister site.

"Thanks to the R2R witches for your hard work!

For the few people trying to getting the keygens to run on Linux via wine, it doesn't seem to work at the moment and will throw "Signature Verification failed". Even if you have the root certificate installed and get the 'All OK' through WitchDiag.
It seems wine hasn't the necessary bcrypt functions implemented or translated to gnutls:


fixme:bcrypt:BCryptCreateHash ignoring object buffer
fixme:bcrypt:key_asymmetric_verify flags 0x8 not supported
fixme:bcrypt:key_asymmetric_verify hash size 64 not yet supported


Time to play around in a Windows VM."

 

Last edited: Mar 28, 2026 at 4:31 AM

There are no "issues" related to winOS that I have seen reported. Other than user error and not following instructions. The "system" works fine when installed correctly and verified using witchdiag. The only real issues encountered were with the undocumented behaviors of a couple of release keygens that didn't apply the magic directly although when applied the magic was sound and worked flawlessly.

There are users who have been complaining about the certificate install, but this is a non-issue where folks are being paranoid for no good reason.

 

try running it from the main drive where the certificate is installed.

 

Follow up to the comment left under TEAM R2R System v1.1.0-R2R

"Fixed it. The problem is actually extremely trivial: a missing case statement for 64-byte keys. Adding this single line to the key_asymmetric_verify function in dlls/bcrypt/dlls/gnutls.c and rebuilding works perfectly (only tried on R2R System 1.10):

case 64: hash_alg = GNUTLS_DIG_SHA512; break;

N.B. I've only tried this with Wine 9.21 due to the yabridge mouse positon bug."



Also R2R have mentioned a fix for emulated windows environments in the latest TEAM R2R System v1.2.0-R2R

"v1.2.0
- New : Added new WitchUnIns to create batch uninstaller for R2R installers.
- New : WitchWand shows error when the WitchMagic is built for newer R2R
System.
- New : R2R Signature is updated to V2. V2 is (stronger than V1 and) more
compatible for emulated Windows environment. Upcoming Magic will be
signed by V2. Verification of V1 signature in R2R System will be
dropped in the future.
- Fixed : The text output from EZKG_Juce*() functions are not ZERO terminated.
- Fixed : Slightly improved performance of R2RSys_GetVersion().

------------------------------------------------------------------------------

Comments for this update :

* Uninstalling plugin bundle is now much easier than before!
* We din't thought we need to code version check, because we always write
enough information in Runtime.txt.
* Signature V1 uses ECDSA P256 + SHA512. There are no problems in the real
Windows machine at all. The problem is that P256 + SHA512 combination is not
that popular and it tend to have problems in emulated Windows environment.
That's the reason we switched to V2 (ECDSA P521 + SHA512). Please
note that we won't change the signature scheme anymore unless there is
vulnerability. If the Windows emulation is still not working as expected,
please ask the fix to the emulator developer, or contribute yourself."