When signing with the same address, the same message, different signatures will appear, as below :

HMVYgVEWUrQBS3smivNZsNpvVvISDpd+R2diIDMH2oqJfKToo9IrkAkrdnAP3xEc2GRfkEjyWwkG6A+SB8JuLrY=

G7Yu0tzrcroQWcXYjCUZMPFH+5G5EvxhfNQHouSk2KjNYWbmU2yROb5x/trFxrhSNzSvlCCVJAUFLU1K/M8Ql0A=

HIRGOvcVxG1ebcl7hSXMh0U7A2+A9ywt2SM9mfgu9GXDDYNDVABjahnZIOiGFXpcF+7IRnyeXpgmlqMXHSjkLP0=

All of the signatures are shown as valid in the "verify bare signature" tab

thank you for your reply.

About RFC6979 by default on windows, using the latest Armory version (0.96.5), each signature is different, using a newly generated wallet and also on an old wallet.

With the argument "--enable-detsign" added to the shortcut, this does not change the behavior of Armory and continues to generate new signatures each time.

Is there another way to do it? ty

Hello,
Is it safe to sign multiple messages using the same bitcoin address with Armory? Each signature produced is different (i am assuming that RFC6979 is not enabled). Can we trust Armory's random k generation? If someone would know the signed messages, would it be possible to derive the private key? ty