Tom Glod wrote:
> When I change pricing models in the future with a major new release
> I will go and look to see if any cracks exist, and then close
> the holes.
Be sure to run cracked copies and keygens only in disposable VMs. Most
of the the ones I've seen are malware delivery vehicles,
Hi everyone, thanks for partaking in the thread.
Hey Sean, Currently I authorize the license key via a web api running on a
WordPress site.
But at the end of the day, its still "if license = trial then this if not
then this." ...and thats is place of attack.. using his debugger
tool... My
Questions. How do customers access/buy your software? How does it know it is on
an authorised machine or with an authorised user?
I have a couple of methods that I remember I thought were very clever (although
ultimately pointless) you might like to add in to the mix but it depends on the
Hi
The fact you can acquire via nefarious means nearly all software out there
demonstrates how easily crackable software is. Adobe, Avid, Autodesk, Boris,
Apple and Microsoft (for goodness sake) have all struggled and failed with it.
Make it difficult for the everyday user to bypass, look at
One other thing about that - it doesn't have to be a thieving hacker.
I wrote a invoicing system for a company years ago (Foxpro for DOS ) and
years later I got
a phone call saying the system was coming up "I'm Melting " - I could't
for the life of me
remember why I put that message in. Went
On 22 Oct 2019, at 4:02, kee nethery via use-livecode wrote:
it would look for Hypercard itself on their disk and start erasing
stuff in it
I applaud the ingenuity and totally understand the reasons for her doing
that, but it should be said that damaging *other* software – beyond
the stack
On 22 Oct 2019, at 20:47, Tom Glod via use-livecode wrote:
i am counting on
his limited willingness to put hours into it.
Either way, it will be absolutely fascinating to read about the outcome.
Good luck!
k
___
use-livecode mailing list
lol... that may be true...cuz i don't think he'll check the mailing list
:) There is only bragging rights at stakeso i just need to add time to
his workloadbut not affect the user experience..i am counting on
his limited willingness to put hours into it.
On Tue, Oct 22, 2019 at 3:02
And if you tell us what you are going to do
he will never catch on .. ..
JB
> On Oct 22, 2019, at 11:57 AM, Tom Glod via use-livecode
> wrote:
>
> yeah... the key is to crank up the difficulty and time investment...much
> like decryption...sure...you can decrypt this in a billion years!
>
yeah... the key is to crank up the difficulty and time investment...much
like decryption...sure...you can decrypt this in a billion years!
On Tue, Oct 22, 2019 at 2:49 PM JJS via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Everything is crackable.
>
> There was once this version
Everything is crackable.
There was once this version of Cubase 5.1 a audio/midi sequencer, very
popular among musicians.
People from H2O cracked it. It was protected by a USB dongle.
They used 1500 manhours for it. And most of the time was not in the
program itself, figuring out when it
On Oct 21, 2019, at 8:02 PM, kee nethery via use-livecode
wrote:
>
> My wife built a Hypercard stack standalone that was protected by a dongle.
> But, every call to the dongle was something you could search for in the
> scripts. So she had scripts that did hashes of the scripts that talked
Yeah...He might call me within 24 hours ..laughing ...and that
wouldn't surprise me at all. :D
Luckily ...none of it is life or death.
On Tue, Oct 22, 2019 at 1:44 PM JB via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Well considering he writes assembly and other languages
>
Well considering he writes assembly and other languages
and is communicating with other people he might be able
to do things that would surprise you.
JB
> On Oct 22, 2019, at 10:38 AM, Tom Glod via use-livecode
> wrote:
>
> Funny, I just sat down to fire up LC to check on the encryption
Funny, I just sat down to fire up LC to check on the encryption option.
That will be the first thing I will do.
My dad will do this using a C++ / assembly debugger, and he finds the point
at which the trial limitation is lifted or enforced, and does all his work
there. So he'll be looking at
That was my first thought too, password protecting the stack makes the
scripts unreadable. The hacker would have to read the memory directly and
I'm not sure what that would show, but I don't think it would be
particularly organized.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
I'd be curious to know how well simply pass protecting the stacks does. Given
the "hacker" doesn't know the key that was used for the encryption, it
shouldn't be possible.
Bob S
> On Oct 22, 2019, at 07:46 , Tom Glod via use-livecode
> wrote:
>
> JB, of course thats true, its just a
JB, of course thats true, its just a matter of how long it takes and how
skilled the cracker must be. Its definitely not a reason not to try.
Kee, that sounds like quite the scheme a self-destructing stack. My
initial instinct is to create some trap using hashing also.
Thanks. :)
On Mon,
My wife built a Hypercard stack standalone that was protected by a dongle. But,
every call to the dongle was something you could search for in the scripts. So
she had scripts that did hashes of the scripts that talked to the dongle. And
she had scripts that did hashes of the scripts that
rumor has it.. .. Anything Can Be CRACKED!
JB
> On Oct 21, 2019, at 7:39 PM, Tom Glod via use-livecode
> wrote:
>
> Hi guys,
>
> My father and I have gotten to talking recently and I shared with him the
> product I will the launching (shortly). My dad father is a kind of white
> hat hacker
Hi guys,
My father and I have gotten to talking recently and I shared with him the
product I will the launching (shortly). My dad father is a kind of white
hat hacker and loves the challenge of it.
My software will have a 30 day trial. He wants to help me by testing how
hard it will be to
21 matches
Mail list logo
