Well the cat is out of the bag and it is not getting in again, REAL will
have to make a new Encryption scheme or better yet, to have it one way
precompiled classes and not encrypted classes which would prevent this from
happening over and over again like it has over the years.
Björn
----- Original Message -----
From: "Mark O'Neill" <[EMAIL PROTECTED]>
To: "REALbasic NUG" <[email protected]>
Sent: Monday, May 15, 2006 3:24 PM
Subject: Re: Encrypt class is not safe?! URGENT
TO REAL SOFTWARE:
PLEASE DELETE THIS POST FROM THE NUG ASAP.
I had not even realized the implications when posting
the question.
Apologies to all, and again, please remove all references
to this post from the NUG.
Sincerely, and humbly,
Mark.
On 15 May 2006, at 15:40, Mark O'Neill wrote:
RB2006r2 OS X 10.4.6
Hi All,
If you encrypt a class, isn't it supposed to stop people
being able to view your code?
However, if you encrypt "Class 1" and then create
a new class called "Class 2" and use "Class 1" as
the interface for "Class 2" then all "Class 1"'s methods
and code is visible in "Class 2". Is this normal
behaviour?!
Seems wrong to me - if that's correct behaviour then
what's the point of the encrypt feature at all?
Is it a bug?
All the best,
Mark.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
