Skip Menu |

This queue is for tickets about the Crypt-DSA CPAN distribution.

Report information
The Basics
Id: 27144
Status: new
Priority: 0/
Queue: Crypt-DSA

People
Owner: Nobody in particular
Requestors: lloy0076 [...] adam.com.au
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.14
Fixed in: (no value)



Subject: Crypt::DSA::Signature->new( Content => 'the content' ) - Suggested Improvement?
Currently Crypt::DSA::Signature will try to decode_base64 what is passed to it. If what's passed to it fails to decode, the module simply croaks. Wouldn't it be better to do this: 1. Determine encoding * eg. watch out for MIME::Base64 exceptions * eg. use some other means to detect encoding 2. Decode it if needed (it may be plain text) 3. Then get the values I could implement this in a way that doesn't disturb the current workings however before I submit a patch or something: 1. Would this be useful? 2. Would it break some compatibility that I'm not aware of? One issue would be people who expected to see it break spectacularly if it saw a non-base64 encoded Content parameter.