Differences between Commercial and Community versions of LiveCode

Lagi Pittas iphonelagi at gmail.com
Wed Jun 6 13:19:42 EDT 2018


Never tried it for Livecode because as in my previous message - Just encode
their name - you dont even have to tell them its encoded
but check on boot up - which I do and wait 6 Months and then tell them -
that will F**Ck them up when they thought they got away with it.

Revenge is a dish best served cold ;-)

I know it worked with a VB program years ago and the DLL's - but that was
to make the executables smaller

Since its open source and actively updated why don't you tell them - In
fact I might  probably use it on my LC9 executables even though I have
indy/business because they are 3 times larger than my LC6 executables.

Lagi



On 6 June 2018 at 18:05, Tom Glod via use-livecode <
use-livecode at lists.runrev.com> wrote:

> after trying UPX on my win32 standalone executable i got a upx: UMP.exe:
> NotCompressibleException :)
>
> On Wed, Jun 6, 2018 at 1:00 PM, Tom Glod <tom at makeshyft.com> wrote:
>
> > great suggestion Lagi... thats a great solution for anyone who needs an
> > extra layer of obfuscation on the binaries.
> >
> > Yes indeed...the .livecode files must be made available.
> >
> > On Wed, Jun 6, 2018 at 12:51 PM, Lagi Pittas via use-livecode <
> > use-livecode at lists.runrev.com> wrote:
> >
> >> The code doesn't need to be available "in the clear" either in Community
> >> or
> >> Business in the executable.
> >> So there is nothing stopping us using something like
> >>
> >> https://www.pelock.com/products/pelock/buy
> >>
> >> or a free one here
> >> https://upx.github.io/
> >> http://www.pazera-software.com/products/free-upx/
> >>
> >> You must make the source files available though. You cant see the C or
> C++
> >> source text in programs written in those languages except for say
> headers
> >> and library calls and there are programs that can go through and
> obfuscate
> >> those as well.
> >>
> >> Lagi
> >>
> >>
> >>
> >>
> >> On 6 June 2018 at 17:12, Brian Milby via use-livecode <
> >> use-livecode at lists.runrev.com> wrote:
> >>
> >> > Can’t do that with community... code must be available.
> >> > On Jun 6, 2018, 11:09 AM -0500, Tom Glod via use-livecode <
> >> > use-livecode at lists.runrev.com>, wrote:
> >> > > what if for example you want to hard code a hash salt into your
> >> > code?.....
> >> > > if the code is readable, then so is the salt. I would vote for
> >> unreadable
> >> > > code 100% of the time.
> >> > >
> >> > > On Wed, Jun 6, 2018 at 10:38 AM, Brian Milby via use-livecode <
> >> > > use-livecode at lists.runrev.com> wrote:
> >> > >
> >> > > > For commercial I would think so, but don’t see any issue on the
> >> > community
> >> > > > side.
> >> > > > On Jun 6, 2018, 9:34 AM -0500, Bob Sneidar via use-livecode <
> >> > > > use-livecode at lists.runrev.com>, wrote:
> >> > > > > Don't we want that NOT to be possible?? Otherwise bring back the
> >> > runtime
> >> > > > engine and run the app as a stack file of the runtime.
> >> > > > >
> >> > > > > Bob S
> >> > > > >
> >> > > > >
> >> > > > > > On Jun 5, 2018, at 19:37 , Brian Milby via use-livecode <
> >> > > > use-livecode at lists.runrev.com> wrote:
> >> > > > > >
> >> > > > > > Looking at the code, “deflate” is called on the stack as it is
> >> > being
> >> > > > written out (zlib). So while not easy, it should be possible to
> >> > separate a
> >> > > > stack file from the binary if deployed from the community edition.
> >> It
> >> > would
> >> > > > take a bit of work to figure out where the file started and ended.
> >> Well
> >> > > > over what I would be willing to tackle at the moment. For anyone
> so
> >> > > > motivated, the relevant source code is in deploy*.cpp (along with
> >> the
> >> > > > header files).
> >> > > > >
> >> > > > > _______________________________________________
> >> > > > > use-livecode mailing list
> >> > > > > use-livecode at lists.runrev.com
> >> > > > > Please visit this url to subscribe, unsubscribe and manage your
> >> > > > subscription preferences:
> >> > > > > http://lists.runrev.com/mailman/listinfo/use-livecode
> >> > > > _______________________________________________
> >> > > > use-livecode mailing list
> >> > > > use-livecode at lists.runrev.com
> >> > > > Please visit this url to subscribe, unsubscribe and manage your
> >> > > > subscription preferences:
> >> > > > http://lists.runrev.com/mailman/listinfo/use-livecode
> >> > > >
> >> > > _______________________________________________
> >> > > use-livecode mailing list
> >> > > use-livecode at lists.runrev.com
> >> > > Please visit this url to subscribe, unsubscribe and manage your
> >> > subscription preferences:
> >> > > http://lists.runrev.com/mailman/listinfo/use-livecode
> >> > _______________________________________________
> >> > use-livecode mailing list
> >> > use-livecode at lists.runrev.com
> >> > Please visit this url to subscribe, unsubscribe and manage your
> >> > subscription preferences:
> >> > http://lists.runrev.com/mailman/listinfo/use-livecode
> >> _______________________________________________
> >> use-livecode mailing list
> >> use-livecode at lists.runrev.com
> >> Please visit this url to subscribe, unsubscribe and manage your
> >> subscription preferences:
> >> http://lists.runrev.com/mailman/listinfo/use-livecode
> >>
> >
> >
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode



More information about the Use-livecode mailing list