Signature Verification on testnet
I have a question regarding the signature verification behavior on testnet. I would like to understand whether the signature verification process on the testnet is intentionally lax or if there are specific settings or reasons for this behavior. 

For instance, if I change my request data to a faked or even empty signature, rpc still responds with `'good': True`.  

Is the signature verification process on testnet intentionally less strict compared to mainnet? Is there a monerod or rpc flag I can use to force testnet sig ver to be strict like it would be on mainnet?

Thanks a lot