<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Good info. Keep talking.<br>
<br>
<div class="moz-cite-prefix">On 8/17/21 11:34 AM, Jammer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:6bd50673-f5c7-d338-7c4e-fc9cdf7d309a@jammer.biz">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><font face="Segoe UI">BOOM.</font></p>
<p><font face="Segoe UI">Exactly this. I think people get really,
REALLY convoluted in these things. All these crazy processes
and obfuscation can introduce stability risks imho and for
minimal real world gain. There isn't a system out there that
hasn't been hacked. iLok et al are just silly imho. <br>
</font></p>
<p><font face="Segoe UI">At best you're just going to to try to
keep people honest, the people that use cracked versions were
unlikely to pay for it anyway.</font></p>
<p><font face="Segoe UI">Partial Key validation can be a good
approach too.</font></p>
<p><font face="Segoe UI">I just wrote my own based around public /
private keys. Wrote a little tool to query my sales back-end
and automates producing a key and emailing it to the user.
Email has a button to click that launches the app and stuffs
the code in. They don't even have to type anything or even
copy+paste anything (unless it's web based email client). I
also didn't want the user to *have* to have an internet
connection, nor any calling home.</font></p>
<p><font face="Segoe UI">Horses for courses though.<br>
</font></p>
<div class="moz-cite-prefix">On 17/08/2021 16:14, Joost
Schuttelaar wrote:<br>
</div>
<blockquote type="cite"
cite="mid:49F1C1C1-495B-4D24-8B77-76B9B418F15B@joostschuttelaar.nl">
<pre class="moz-quote-pre" wrap="">On 17 Aug 2021, at 16:07, Matt Picone <a class="moz-txt-link-rfc2396E" href="mailto:matt@mysticworks.com" moz-do-not-send="true"><matt@mysticworks.com></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Does anyone here have skills or know anyone who is strong in the area of development around audio software anti piracy?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">No expertise, but a very interesting topic!
Aren’t most copy protection schemes quite trivial to break these days, when Mac’s for instance enforce memory as non-executable, and have features like address space randomization on by default? I remember that things like iLok basically do tons of self inspections to see if code was modified, right?
I think the best copy protection schemes are: user loyalty, some quite useful cloud features and frequent updates (just make it hard to stay up to date…)
Cheers,
</pre>
</blockquote>
<div class="moz-signature">-- <br>
<b>Jammer<b><br>
<a href="http://www.jammer.biz" moz-do-not-send="true">WWW.JAMMER.BIZ</a></b></b></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
music-bar mailing list
<a class="moz-txt-link-abbreviated" href="mailto:music-bar@lists.music-bar.org">music-bar@lists.music-bar.org</a>
<a class="moz-txt-link-freetext" href="http://lists.music-bar.org/cgi-bin/mailman/listinfo/music-bar">http://lists.music-bar.org/cgi-bin/mailman/listinfo/music-bar</a>
Listen to Music-Bar Radio! <a class="moz-txt-link-rfc2396E" href="http://www.music-bar.org/radio.html"><http://www.music-bar.org/radio.html></a>
</pre>
</blockquote>
<br>
</body>
</html>