Thanks for the ideas! It is good to know what can safely be done to the
binaries and I will look into "embedded mono".
--
View this message in context:
http://mono.1490590.n4.nabble.com/Hardening-Linux-Binaries-tp3899251p3902072.html
Sent from the Mono - General mailing list archive at Nabble.co
> By "harden" I mean provide some protection against disassemblers, debuggers,
> cracking, and reverse engineering. The purpose is to protect the
> intellectual property.
You can use "embedded mono" to load your code from some proprietary archive.
Elmar
___
On 12.10.2011 21:39, Chris Derrick wrote:
> By "harden" I mean provide some protection against disassemblers, debuggers,
> cracking, and reverse engineering. The purpose is to protect the
> intellectual property.
As you can imagine, in the open source scene such protections are
pretty pointless.
By "harden" I mean provide some protection against disassemblers, debuggers,
cracking, and reverse engineering. The purpose is to protect the
intellectual property.
--
View this message in context:
http://mono.1490590.n4.nabble.com/Hardening-Linux-Binaries-tp3899251p3899350.html
Sent from the Mo
What do you mean by "harden"?
--
I may have used dictation software to write this email, please excuse any
confusing mistakes.
Chris Derrick wrote:
>There is a Windows Service that I have been adapting so as to be Linux
>compatible. I'm almost finished and need a way to harden the binaries.
>
There is a Windows Service that I have been adapting so as to be Linux
compatible. I'm almost finished and need a way to harden the binaries. I
was not surprised when my attempt to harden the Mono generated executable
with WinLicense failed (when I tried to pass the result to mono-service2 it
sim
