I was recently asked whether a certain library supports the ECDSAwithNone Signature algorithm. Clearly this would mean ECDSA with the identity function as the hash function. I know this is a really bad idea. And I also know that there's a trivial attack if two messages have the same prefix as the "hash" gets truncated to the first q bits (q being bitlength of the order of the curve).
However I wanted to know: What are the "worst" possible attack(s) against this signature scheme?
The worst attack is hereby defined to be the attack that needs the least known or chosen signatures while being executable in reasonable amount of time.
…because the customer needs it
– May be me, but when it comes to cryptography (and other things touching information security) I rather tend to gently educate “customers” to use something safer, instead of simply following the easiest path towards writing the next bill that’ll pay someone’s rent. On the long run, putting an emphasis on security instead of the feelings of “customers” always turned out to be the smarter choice – at least for those I interacted with. But maybe that’s merely rooted in the fact I have yet to meet my first (as you call it)stupid
customer. $\endgroup$ – e-sushi Oct 24 '15 at 10:13