When you put so much time, effort and creativity
into writing a script that solves a very difficult problem or accomplishes a distinguished task,
it is understandable for you to want to
protect your work. Why? If you don't protect your creative work, there are people with far more resources than you who can and will use the fruits of your hard labor as a basis to launch their own work and will never give you credit for it. If the likelihood of that happening does not worry you, then this is surely NOT the site for you. I repeat, this is surely not the site for you and it would be wise for you to stop reading now.
However, if you never want to be in a position where someone else gets credit for your hard work, I strongly recommend you read this page thoroughly, over and over again.
When seeking to encrypt, release and distribute scripts written in an interpreted language, some of the most common questions I'm sure you've pondered upon were; can it be done, if so, how? Unfortunately, the generally accepted answers to those questions are that you can't, or that
it doesn't really work, or you shouldn't, or it costs lots of money.
And no matter what you do, someone smart enough or someone with enough
time on their hands can get to it, so don't bother.
These answers are somewhat true to a very small degree but they're also a huge copout.
Ignoring the practicality of securing your code JUST BECAUSE
someone can get to it is similar to deciding not to lock the doors to your house
anymore JUST BECAUSE locks can be picked. It makes no sense. Yes, locks can be picked but
fortunately it is difficult for most people to do, so I still strongly recommend
you lock your doors. Besides, if you make it hard enough to get to your
code, most people won't bother and the ones that do persist will be reported to you through alert notifications, just as you would expect to be notified if thieves were to try to break into a house of yours that is protected.
In my particular case, I had to begin heavily encrypting all my important scripts due to not one, but two very bad experiences.
Here's my Story:
Years ago, I worked at a company that rewarded me quite handsomely with significant monetary awards.
My inventions (in the form of automated scripts) were categorized,
for the purposes of the company, to be very creative and a major time saver.
With the many accolades I received came unexpected envy from
coworkers. Back then, there was no way to hide the content of my scripts
nor was it possible to compile them. Therefore, all the work that I
did was open for the world to see. Frankly, at the time, even if there
had been a way to conceal my source code, I dont think I would have. I had no
reason to. I was quite happy to share my scripts with whomever was
interested in viewing them.
Sadly however, the envy of my coworkers didn't stop there.
It rapidly morphed into jealousy, which then led to them invading my privacy at a rather alarming frequency. I was spied on regularly.
My home directories on several hosts were being ravaged through whenever I'd leave the office for the day. Their nefarious objective was to
try to figure out how I was doing the magical things I do, and possibly beat me to the completion of my next surprise project. I didnt like being watched at all. It infuriated me.
But there was nothing I could do, except seeth with anger.
At that company, everyone on my team had root access so there weren't any
permissions or ownerships I could have set to restrict or protect access to
my files. So I found myself in a dilemma; shall I embark on the torturous endeavor of learning a new compilable
language, or should I just continue to
cope with the relentless disrespect. Due to a lack of time and the fear of risking
further alienation at work with my coworkers, I chose to deal with the disrespect and opted to
instead slow down on my creative projects. I didn't want to give my unscrupulous colleagues any new
materials to mooch off of anymore.
I eventually left that job. But, my worries did not end there. Fast forward a couple of years later. I came up with a new invention
which I was very excited about. To gain exposure, I uploaded this invention onto a popular
monitoring application website, as a free plugin. This website took
down my tool after a few months, and brazenly came up with their own
commercialized version of it. I was shocked. Took me a while to come to terms with the fact that
this was happening to me yet again. I of course couldn't fight the perpetrators.
They were a major company and I was just a lone wolf. I stood no chance. Given my history of
having been taken advantage of in the past, this was the
last straw for me. I couldn't take it anymore. I refused to be used (without being given due credit) by others as a springboard to great success. This had to stop and I was going to make sure of that!
So I set forth on a journey into the vast canvas of the unknown. My goal was to obtain a particular set of skills that is both unique and impossible to replicate. I needed a way to harness all the technical knowledge I had accumulated over the span of 15 years and put it all towards inventing a one of a kind utility, a tool built on a massively complicated but efficient algorithm - This algorithm must allow me
to not only encrypt my scripts but also make the encrypted, obfuscated copies of the scripts executable. In addition to that, I wanted this desperately needed tool to notify me whenever nefarious attempts are made to unseal my protected code.
At the onset of this distinguished project, the likelihood for success was grim. The journey was tough. It was brutal.
It was discouraging. It was long. It cost me thousands of hours but, at the end of it all,
I found a way - hence the birth of www.EnScryption.com. Simply put, EnScryption.com was built with several years worth of programming and system administration expertise, coupled with bitter,
unforgettable life experiences.
If you want peace of mind knowing your scripts (written in interpreted languages) are secure, congratulations! You are exactly where you need to be. EnScryption.com is the most effective security guard for your scripts. I spend almost every single day hardening the different algorithms used in my encryption process. I'm motivated by the memories of the pain of my past and by the countless hours I was forced to spend lamenting in absolute helplessness. I'm here to ensure what happened to me does not happen to anyone else. I believe if YOU work hard to create something of great worth, a work of art, YOU deserve to claim and get 100% credit for it and that's what I'm here to help you do!
script to my site, and we’ll automatically produce an encrypted,
executable version of it for you. Or if you’re paranoid (as you should
be) and don’t want to paste it to an external site, purchase a copy of
my encryption tool and use it on your own private hosts on as many scripts as you wish!