Safedisk 2.80.010
 

New version of SD on Divine Divinity 1.31 patch. Kudos to the person who breaks it. :confused:

AAARGH
 

That's what I call good news!
A new sd2 version, Monty is not amused. :mad: :mad: :mad:

It is highly likely that it has already been cracked.

Just that you'll not see a public release of any cracking app. Unless of course Bools Eye stays up all night!

Hint...hint!!

I think I now see one reason why r!sc decided to pack it in, too many people on his case asking for the latest unwrapper :)

Poor old bools :( Give it up while you've still got your sanity :D

DrA.

LOL

i'll never give up cracking that thing... i just need some more debugging experience & stuff...

anyway, you can expect something in the near future ! ;)

Dedicated to the cause!

hope you don't lose too much sleep then :)

btw, is it possible to 'dump' an exe using your NoCD Loader and 'rebuild' it using Revirgin? I've not tried this as I get a bit lost reading the revirgin docs, but wondered if it was possible.

DrA.

afaik, Revirgin is a tool to rebuild the import functions of a SD protected file. but that's not the real problem in versions 2.60 and 2.70 (and 2.80 ?). cirkutz is right: the biggest problem there is the encryption of some small pieces of code (btw, that's why that vxd is installed !!).
and then there's another new feature: some "call" functions are encrypted (not the same as introduced in Safedisc 1.40.04 "R3", there the "call dword ptr" functions are messed up).
my source is reliable too :)

Thought it sounded a bit too easy :)

It's just that I noticed in a few Revirgin tuts Safedisc mentioned and some Fixed EXE's that are Safedisc protected contain new sections in the file called 'newidata', I assume a new rebuilt Import Table, but obviously they been manually traced, decrypted, dumped and merged back, kinda complicated for newbies :D

Thanks for explaining the reasons why it can't be done CirKutz, bOOls.

DrA.

if this can't be done then how has this been done?

what can't be done ?

Revirgin (and less so imprec) are more designed to rebuild mangled/screwed IAT of packed/compressed PE files which have been infected with things like ASProtect etc. Earler SD2 versions could be rebuilt but like it's been said above, the redirected calls (like Securom's latest versions) call for a lot more debuggging and code replacement.
In the end it will always be possible to rebuild these protection mechs as it MUST be decrpyted in memory to run. Even SMC routines can be rebuilt. It's just a matter of time to step thru all the crap (and obfuscation used by macrovision to slow debugging down) and do a little cut and pasting.
Apps like revirgin will help, but developers are gettting wise to these rebuilders and add fake API calls (just look at the multiple "double-dipping" of the latest ASProtect) to mess up automation.

My patience these days ain't what it used to be so maybe Macrovision has beaten me!

I do remember +tshep or was it Kayaker? saying 'Never Ever give up' or words to that effect :D

And ArthaXerXes saying 'imhotep' (ALL YOUR OBFUSCATION ARE BELONG TO US) when Safedisc was mentioned :)

DrA.

i think that microvision will give it up some day cause she can see that we are all beating her sooner or later....

nah, they're making too much money. Even though their profits fell recently, they're still making very nice profits. :mad:

You mean as long as there are dumb software companies to sell their crap to :D

DrA.