Re: Examine "Saved" IDL procedures now too! [message #29968 is a reply to message #29874] |
Tue, 26 March 2002 04:47   |
Randall Skelton
Messages: 169 Registered: October 2000
|
Senior Member |
|
|
On Mon, 25 Mar 2002, Pavel Romashkin wrote:
> I am sure many people would love to be able to decompile commercial products
> into source code. Also known as hacking. This is what I think we are seeing
> here.
Decompilers and other such tools have existed and been used for years. I
think you are confusing the difference between the existence of a tool and
the malicious use of a tool. Software licenses are what should prevent a
user from maliciously hacking code.
For those 'programmers-for-hire' that are annoyed by Craig's library, I
suggest that you contact RSI. However, I doubt that RSI ever claimed the
IDL sav file format was a secure way to distribute source code as they
knew the source code was relatively easy to recover.
> I am sure it is far from impossible to, say, fish out IDL's license code
> from its binary and post the hack all over the internet, but I doubt it
> would be the right thing to do.
I agree it is wrong. Moreover, it would violate the IDL license agreement
and therefore give RSI the opportunity to take legal action.
> I indeed agree that ability to make executables is what we all want but I
> don't think that this way we are any closer to that. And a lot of code that
> developers might not want to disclose is wide open now.
I honestly hope this isn't the case. Nevertheless, most developers should
be distributing license agreements or have contracts with customers that
clearly state the software terms of use.
Cheers,
Randall
|
|
|