New Version

[Barbuxx]

Just in case you came here before the eziriz website, there is a new
version up on the website dated 17 May 2012! If anyone has done any
testing, do you know if it breaks the existing anti-reactor tools?

[Tim Haughton]

That's good news, thanks for the update!

Tim

--
You received this message because you are subscribed to the Google Groups ".Net Reactor Support" group.
To post to this group, send email to net-react...@googlegroups.com.
To unsubscribe from this group, send email to net-reactor-sup...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/net-reactor-support?hl=en.

[cocowalla]

Good to know he's spending time working on a new version, rather than actually providing any support for existing versions... :/

[leblancmeneses]

upgrading isn't free - renewal license (it's been over a year since i
purchased commercial version)

residual income trick? I was already using sl5 with previous version
of .net reactor.

I'm considering trying out some others before renewing. - although
their stuff has worked for over a year.

lm

[Ivan Borges]

For those interested, I have upgrade and tested the new version. It works really fine and solves Anti ILDASM and has some new features.

And according to support there are some more features coming soon. I highly recommend it. And honestly, the upgrade price is unbeatable.

 

--
You received this message because you are subscribed to the Google Groups ".Net Reactor Support" group.

[Robson Felix]

Has anyone verified what Barbuxx is saying?

Has anyone tried using a different product?

I have seen many cracks on the internet that even reverse the whole
obfuscation.

I really need something that can protect intellectual property. Then I will
be concerned with licensing the copy. Only then.

Thoughts??

-----Mensagem original-----
De: net-react...@googlegroups.com
[mailto:net-react...@googlegroups.com] Em nome de Barbuxx
Enviada em: quarta-feira, 23 de maio de 2012 22:00
Para: .Net Reactor Support
Assunto: New Version

Just in case you came here before the eziriz website, there is a new version
up on the website dated 17 May 2012! If anyone has done any testing, do you
know if it breaks the existing anti-reactor tools?

[Glen Harvy]

Hi,

I don't normally respond to these questions simply because you obviously
haven't done much research.

Get this firmly planted in your mind:

1. There are hackers out there that are super whiz-kids and get their
lifes' thrills out of the de-obfuscation of anyone's code. These guys
are really quite brilliant and will always be able to crack anyone's
de-obfuscation algorithms.

2. If you accept the above then you realise that you can only protect
your code from people that probably are bad or inept programmers. They
use readily available tools created by 1. If they were decent coders
then they wouldn't really bother.

3. You need to try to keep one step ahead of 2 as you will never get
ahead of 1.

4. In time, all obfuscators will be cracked. You need to change them
frequently OR the creator of the obfuscator must keep one step ahead by
changing their algorithms.

5. I understand .Net Reactor protected code has been cracked for some
time. It always will be unless you upgrade or install a new release of
the obfuscator. You can only be protected if you scan the internet for
every released version of your product and delete it - impossible.

Whether you like it or not, if you continue to use .Net based products,
you will never be able to fully protect your intellectual property.

If someone pinches any of my code, their nuts.

If someone can read my passwords or other encrypted/sensitive data then
I am worried - but that is NOT obfuscation.

If someone can use my software for free forever I am really pissed off -
but that is NOT obfuscation.

In short, accept your code can be read by the whiz-kids but if your
chosen obfuscator is frequently updated then take some solace that at
least your latest version stands a good chance of not being cracked
within a few days of release.

I know the above isn't what you want to hear but it's as close to the
truth as you will get.

Regards,

Glen.