Status
Not open for further replies.
Want to kick them in the nuts? Release your decoder as open source for the world to have, that way they can't prosecute every single user and they will have 2 options, to release their code themselves or to completely re-design their encryption engines.
 
Well 2 things to say.

I tried decoding a file.. and always get some weird stuff.

** SplitIce Ioncube Decoder **<br />
Opening ../phptmp//gifts.php
- Supported version type (3).
int(14422)

or

** SplitIce Ioncube Decoder **<br />
Opening ../phptmp//ribbons.php
- Supported version type (3).
float(1522402229)

As for Ioncube.. They SHOULDN'T be threatening you. If they asked you nicely that's different. If they send a we will take you to court... jail etc.. I would ownz them right now. They need to learn like ALL encryption services. ALL encryption can be broken. I've taken classes on data encrpytion and found anything can be reverse engineered and broken no matter what type of of system it is... so if ioncube gets their broken.. it's THERE fault. They can make a new one.

They already ripp people off getting the ioncube encoder.. so now they can stop sitting on their fat asses and work for their money.

I say you mass release it later.

I know earlier a group had built a server, and users could download the user client and connected to the server. That way no one got the source code to deioncube, but could still get their files decionubed and a zip was created for them at the end.
 
Well 2 things to say.

I tried decoding a file.. and always get some weird stuff.



or



As for Ioncube.. They SHOULDN'T be threatening you. If they asked you nicely that's different. If they send a we will take you to court... jail etc.. I would ownz them right now. They need to learn like ALL encryption services. ALL encryption can be broken. I've taken classes on data encrpytion and found anything can be reverse engineered and broken no matter what type of of system it is... so if ioncube gets their broken.. it's THERE fault. They can make a new one.

They already ripp people off getting the ioncube encoder.. so now they can stop sitting on their fat asses and work for their money.

I say you mass release it later.

I know earlier a group had built a server, and users could download the user client and connected to the server. That way no one got the source code to deioncube, but could still get their files decionubed and a zip was created for them at the end.

lol obviously ioncube can be decubonized (lol my word)
the people who coded ioncube probably have the decoder, its just for their company probably.
 
Ya I bet they do. Although it makes me wonder what a programmer would do.. if he ioncubed his files and lost his source code? I guess hes screwed and I doubt ioncube would let him use the decoder? LOL :D
 
not really, how is decoding something illegal?
if people abuse it, its them doing something illegal.
the coder has nothing to do with it =P
Depending on the country live in this may or may not be the case.

Well 2 things to say.

I tried decoding a file.. and always get some weird stuff.



or



As for Ioncube.. They SHOULDN'T be threatening you. If they asked you nicely that's different. If they send a we will take you to court... jail etc.. I would ownz them right now. They need to learn like ALL encryption services. ALL encryption can be broken. I've taken classes on data encrpytion and found anything can be reverse engineered and broken no matter what type of of system it is... so if ioncube gets their broken.. it's THERE fault. They can make a new one.

They already ripp people off getting the ioncube encoder.. so now they can stop sitting on their fat asses and work for their money.

I say you mass release it later.

I know earlier a group had built a server, and users could download the user client and connected to the server. That way no one got the source code to deioncube, but could still get their files decionubed and a zip was created for them at the end.
The decoder has been disabled temporarily while we sort things out in Ukraine.



I wont ditching the project put it that way, I have a host for it and decod.in has already moved over to the new host.

The person who was kindly hosting the old ioncube decoder on their server fowarded me the message they sent him so here you all go (I have removed some parts for privacy/good will):
> Dear [Name Removed]
>
> I am emailing concerning your activities to reverse engineer the
> technology of ionCube Ltd. for the purpose of facilitating intellectual
> property theft.
For real? Under what statutes or precedents are you persuming this. Oh and dont say UK or American law as not everyone resides in the 2 major population centers of the world.

>
> While reverse engineering can be a fun exercise and satisfying
> intellectual challenge, I need to make you aware that attempts to reverse
> engineer ionCube technology, including but without limitation the ionCube
> Loader, the ionCube PHP Encoder and encoded files, is a violation of the
> ionCube license agreement. While exploring privately for ones own personal
> satisfaction is one thing, moving this into the public arena is a
> different ballgame entirely, and is something that is taken extremely
> seriously.
>
> Your exact motivation is unclear, but your actions suggest and constitute
> an attack not only on the PHP script development community at large, but
> also on the PHP project itself, the continued success and evolution of
> which is in a large way due to the widespread adoption of PHP as a serious
> language for commercial development, which has only been made possible by
> tools such as the ionCube Encoder.
>
> When the ionCube Encoder was launched in 2002, the only way to protect PHP
> software was with Zend encoder, but this was, and remains, priced far out
> of reach of most developers, who might have dreamed of making a living
> from PHP development but for whom this was simply not feasible. The
> ionCube Encoder dramatically changed this, giving developers for the first
> time the opportunity to stop working for someone else, with the potential
> to support themselves and their families from developing and marketing
> their creative ideas full time and not just as a part time evening hobby.
> The rest you could say is history.

As a person who develops and provides a comercial PHP development service I think I am adept to say that ioncube is dangerous. Dont play your backup cards right and you can end up with encoded versions of your scripts and no source product, hence why I end up sponsoring [name removed] by hosting him on my server (Now you got my motivation). Never used the ioncube encoder in the past 3 years because of that, cant say I made any less money as a result.

>
> While your actions thus far are already extremely serious and punishable
> by effective legal action within your region,

Which would be? Last time I checked Reverse engineering between certain paramaters still remains legal over here.
- it applies only to computer programs. It does not apply to associated works or subject matter that may be included in the program. For example, it will not allow reproduction of the film, music, or sound recordings embodied in a computer game
- it only applies for the purpose of obtaining information necessary to enable the [person] to make independently another program [or] article;
.... I could go on. But let me just quote EFA
Section 47D (and the other computer-related exceptions in the Copyright Act) are protected from exclusion by contract in s 47H. This means that, a provision of the EULA or ToS that states that the licensee has no right to reverse engineer the product is invalid. This operates in favour of the reverse-engineer, and is in stark contrast to the position in the United States, where such contractual clauses have proved fatal to a claim of fair use.


we are prepared to turn a
> blind eye at this time should they henceforth be taken and remain private.
> We would therefore kindly request that you remove with immediate effect
> all references to your project from sites such as thewarezscene.org and
> wjunction.com,

I have no control over wjunction, feel free to contact them or their ISP, I wish you good luck in that area. [REMOVED CONTENT]

that you make best efforts to do the same for any systems
> not under your control, and that you cease and desist from any further
> public dissemination of information related to reverse engineering of
> ionCube technology.


>
> Recognising that despite evidence to the contrary you might not be anti
> PHP and that you might actually appreciate and enjoy PHP, should you have
> any questions I would be more than happy to discuss via email or IM.

Your thoughts would be best taken up with.. [REMOVED CONTENT]
Bold is my response / [] is removed content
 
Yes, that's more or less the reply that I would have sent (I'm a lawyer and PHP developer myself).

There's one thing to add, it "might" be illegal to reverse engineer the ioncube code and spread it, as it's covered by copyright laws, but it's not illegal to decode a third party product (the encoded php script) as by acquiring that piece of software you're accepting the 3rd party's terms and that doesn't include IonCube's terms of service.
 
Im still waiting on a response to the email, if I dont get one within 3 days I will be forced to aptly persume that the email was some kind of hoax.
 
Kudos on the domain choice, and the work overall.

Having a license to the encoder myself, I'm tempted to whip some stuff up and check out what I get back.
 
Status
Not open for further replies.
Back
Top