Fix a potential leak/incorrect return value in DSA signature generation.

In the very unlikely case where we have to repeat the signature generation,
the DSA_SIG return value has already been allocated. This will either
result in a leak when we allocate again on the next iteration, or it
will give a false success (with missing signature values) if any error
occurs on the next iteration.

ok tb@

0 files changed, 0 insertions, 0 deletions