The Bat! got keygened
 

After keygening WinRAR, now SeVeN has keygened The Bat!. I think it is using ECDSA-800. It seems he has found a new way to factor the numbers or bought a super-computer ;)

P.S: I don't know much about grid computing

Is it really significant how it was made? You can see this nice release, anything else is a mystery.

Yes, it is very interesting how it was made. It seems the hole exists in the key generation scheme. Anyway, it is great results.

Well anytime a program has gone without a major break in their registration security, (Total Commander, Winrar, etc...) everyone is naturally curious in general, especially if SeVeN found a new attack style on ECDSA or just how in general he did it. Such a tutorial would be an amazing read, but will probably never happen.

I think SeVeN will not give this information. This topic will be a second flood-topic like WinRar with stupid thanx. My post means only that.

Even if exist new style attack on ECDSA, you can not use this technology as your own. So, right way try to find and work hard on another attack. There many examples (ASProtect keygens by TMG & ECLiPSE, RSA protected apps breaked with grids, etc.)

I agree my friend. I was only attempting to explain nanobit's curiosity.

SeVeN is great keygenner :)

I didn't start this thread as a "thanx" one for the keygen. I just wanted everybody to know that ECDSA is defeated AGAIN, and that's not something unnoticeable.

I wish 1536-bit RSA to be vulnerable also, but :(...

I don't think that ECDSA is vulnerable. IMHO, it was attack on implementation.
p.s. Forget about hasp, man :)

ECDSA-800
 

Thank you for your observations, what do you mean by ECDSA-800? Could you please explain in detail what ECDSA-800 is?

http://en.wikipedia.org/wiki/Elliptic_Curve_DSA

And its key has a length of 800 bits.

The Bat! has NID_sect163k1 curve (NIST curve over a 163 bit prime field). I saw a maximum recommended 571 bit prime field. Never heard of 800 bit keys when it comes to Elliptic Curves.

Is SeVeN think that exetools members has not enough persion for get his method?

for user that got download problem:

_http://rapidshare.com/files/273086254/The.Bat_.v4.2.9.1_KEYGEN-FFF.zip.html

It's amazing :). Some years ago I wrote keygens for TheBat 2 and 3, but I have used my own private key to generate licence and replace original public key with mine. I attach source code of tbkg3 (it's history). The algorithm is in keygen.cpp.

Really impressive feat.
Anyone already tried to reverse the keygen?

Main problem is search of private key ECDSA. Coding keygen isn't too hard. Reversing of keygen will not help.

It's great. But if can crack the password of rar file would be greater.

seems EDCSA isn't secure anymore... anyone know about (public) holes? didn't read any news about it.

aren't fff famous for stealing private keys off webservers? ;)

well, D-Jester did a little research. see them here:
ECDSA Books
The Insecurity of the Elliptic Curve Digital Signature Algorithm with Partially Known Nonces

these are hardly relevant, though.

That is true, so we still can do something to find the right way.;)

I also agree with the a few other guys that the attack was started over a vulnerable implementation of the algorithm.
propably somebody who found a weakness in the algorithm would rather say nothing at all or he/she would wrote a very detailed document on it, because of the importance of that fact.

just my 2 cents.

regards,
PAPiLLiON

I'm thinking ... SeVen will be able to keygen CRO 239 bits (120 chars ECC) Flexlm target licenses??? Atm LND and ZWT cant do that, or not? :)

see more here

LND can do almost FlexLM with some experience reversers :) Legends Never Die

thanks for reply but i think that is not right, because LND cracks Pro/Engineer with license.dat + patch, and this is not really *pure* keygening :)

keygen by FFF works 100% with version 4.2.12.4
_http://narod.ru/disk/12146877000/The.Bat!.v4.2.9.1_KEYGEN-FFF.zip.html
_http://rapidshare.com/files/309364279/The.Bat_.v4.2.12.4_KEYGEN-FFF.zip

If FFF/SeVen did indeed break ECDSA on sect163k1 they should (in theory) be able to generate licenses with LM_STRENGTH_163BIT considering the following from the flexlm headers
IMHO it is much more likely that Rarlabs made a poor choice of privkey/pubkey or have other implementation problems whereas
Macrovision/Acresso/Flexera bought their ECC/ECDSA-implementation from Certicom, a respected(?) company dealing exclusively in high security software products...

So to answer your question: I personally don't think we are going to see keygenned flexlm CRO/TRL SIGN2 licenses anytime soon ...

cheers,
dirkmill :cool:

Hello Dirkmill, thanks for reply.
After this result we can compare SeVen with other great keygeners on the past like Dimedrol. But i think you right, probably the choice of WinRAR keys is really poor. Cracking of FlexLM CRO protected applications will be harder of course, maybe it is impossible today. But who knows, freaks of nature (like Se7en) are ready to attack. We will see, alto this is another history.
Bye! :)