Password Changer for AMS

[Ulrich]

Hello,

I have released a new tool today. Licensed users of AutoPlay Media Studio may use this program to set a personalized password in the software that will be used to protect the *.cdd file created upon export of the project.

By setting a new password in the editor and runtime binaries, works distributed to third parties become more resistant (but not immune, of course) to reverse engineering. With one single execution of this tool, every licensed user is able to create a new and unique autorun.exe file. Evaluation and modified programs will not be recognized by the tool.

The use of this tool is not endorsed by Indigo Rose Software in any way, and you should use it on your own risk. Your original files are backed up, and should you need to get the original versions back (like before you perform a software update, for example) just rename them back, but please don't complain if something does not work as expected. Although the operation should be reasonably safe, I cannot guarantee that there won't be any side effects.

You may download the tool here: Password Changer. In the zip you will find documentation in PDF format - please read it before you do anything else!

Ulrich

[ShadowUK]

Can't wait until it does the memory as well.

[jackdaniels]

Just what I needed,,, spot on upeters
Thanks

[ezasabc]

it says under the win32rt.dat file no original commercial binaries found? any help

[Ulrich]

I have not included support for all versions yet. What is the full version number, shown as detected in the dialog?

Ulrich

[ezasabc]

the 7.5.1000.0

[Ulrich]

I have now updated the tool to recognize this version, please download and try again. But you should, if possible, update your installation to the most recent version as this release has some known problems.

Ulrich

[jassing]

this tool changes 29 bytes in both the ams70.exe win32r.dat file (from the 'stock' 29 bytes to the new 29 bytes in both files)

Anyone that could crack the original password, would be able to id the change, and use that to crack the new password...

Not saying this isn't a step in a good direction; but it's definately not "fool proof".

This is like locking a screen door... Keeps the honest people more honest...

[Ulrich]

Anyone that could crack the original password, would be able to id the change, and use that to crack the new password...

You have not read the explanations in the enclosed documentation, or failed to understand what I wrote. If you process the runtime with yP.exe, it becomes much more difficult to access the password after it was changed.

Ulrich

[jassing]

You have not read the explanations in the enclosed documentation, or failed to understand what I wrote. If you process the runtime with yP.exe, it becomes much more difficult to access the password after it was changed.

Sorry ulrich, I didn't think I needed to spell it all out....

Posting "I have encrypted my file with AES 16bit encyrption, using alphanumeric characters" -- that DRASTICALLY reduces the time to crack it.

Pushing Yoda's protector (btw: it's an old version) also drastically reduces the time to get it to an "unpacked" state. There are at least 2 unpackers out there that work on yoda's. So "here use yoda's" also says to hackers "Oh, it's protected with Yoda's... I have the unpacker for that right here...."

As I said; it's a good step in a good direction.... It keeps honest people more honest....
Any binary can be decompiled if someone wants the code...

Of course, these comments are null-n-void if you've taken yoda's source & altered it such that the unpackers are thwarted.

I think what you've done is good.... It's just not "the answer" to security/encryption.... IOW: Good Job Ulrich!

btw: as I (also) said; I think if you're developing applications using AMS that require your code to be "protected" I think ams is probably the wrong tool...

[slota]

I'm found CDD Protection flash video tutorial on one russian forum (with tools for protect):

(URL removed, virus "Trojan horse PSW.Agent.FNL" reported in one of the tools of the package)

Upeters - maybe some tricks you use in next releases of Password Changer?

[Ulrich]

Upeters - maybe some tricks you use in next releases of Password Changer?

I doubt it. This goes way too far. As it was already said, there is no way to avoid completely to break a software protection. My intention was to hinder the decompression of the resource files, changing the default password in a secure and accessible way. This objective was reached, and while not a perfect solution, this is where I stop.

By the way, the yP.exe shipped in this "tutorial" is the one that I compiled and shipped with my tool. I must have done something right.

Ulrich

[Tomasin]

I'm found CDD Protection flash video tutorial on one russian forum (with tools for protect):

(URL removed, virus "Trojan horse PSW.Agent.FNL" reported in one of the tools of the package)

Upeters - maybe some tricks you use in next releases of Password Changer?

This is Hupigon trojan (By ESET)...

[slota]

(URL removed, virus "Trojan horse PSW.Agent.FNL" reported in one of the tools of the package)

This is Hupigon trojan (By ESET)...

This is not virus! Some packer signatures coincide with virus signatures. Sorry.