Improve the error message when BR's --crypter.key
is invalid
#56388
Labels
component/br
This issue is related to BR of TiDB.
found/gs
found by gs
report/customer
Customers have encountered this bug.
type/enhancement
The issue or PR belongs to an enhancement.
Enhancement
When you run
it will report the error
because the key input should be hexadecimal (2D6D2E8414C4B1752EDCDF3D413BC6E8) rather than base64. But the error message is very unclear.
It should explicitly say something like "crypter key for aes128-ctr should be a hexadecimal string with 32 digits".
The text was updated successfully, but these errors were encountered: