<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Agree completely. From the user experience side (which is important) things like iLok are just going to create additional support headaches, and those support headaches will probably offset your loss in sales.
</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The best systems I’ve seen will rarely if ever phone home except when asked to for update purposes.
</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I know a guy that makes plugins for a living, and every time Apple released a new OS, they had to spend a lot of time updating their whole catalog to update the copy protection. A few years ago, they decided to drop the copy protection,
and it didn’t put a dent in sales, but made a huge impact on their available resources.
</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If you want, Matt, I can try to get you in touch with them. </p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Tony </p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">
Mail</a> for Windows</p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="border:none;padding:0in"><b>From: </b><a href="mailto:jammer@jammer.biz">Jammer</a><br>
<b>Sent: </b>Tuesday, August 17, 2021 10:35 AM<br>
<b>To: </b><a href="mailto:music-bar@lists.music-bar.org">Music-bar</a><br>
<b>Subject: </b>Re: Software Security</p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-family:"Segoe UI",sans-serif">BOOM.</span></p>
<p><span style="font-family:"Segoe UI",sans-serif">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. </span></p>
<p><span style="font-family:"Segoe UI",sans-serif">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.</span></p>
<p><span style="font-family:"Segoe UI",sans-serif">Partial Key validation can be a good approach too.</span></p>
<p><span style="font-family:"Segoe UI",sans-serif">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.</span></p>
<p><span style="font-family:"Segoe UI",sans-serif">Horses for courses though.</span></p>
<div>
<p class="MsoNormal">On 17/08/2021 16:14, Joost Schuttelaar wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>On 17 Aug 2021, at 16:07, Matt Picone <a href="mailto:matt@mysticworks.com"><matt@mysticworks.com></a> wrote:</pre>
<pre> <o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Does anyone here have skills or know anyone who is strong in the area of development around audio software anti piracy? <o:p></o:p></pre>
</blockquote>
<pre><o:p> </o:p></pre>
<pre>No expertise, but a very interesting topic!</pre>
<pre><o:p> </o:p></pre>
<pre>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?</pre>
<pre><o:p> </o:p></pre>
<pre>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…)</pre>
<pre><o:p> </o:p></pre>
<pre>Cheers,</pre>
<pre><o:p> </o:p></pre>
</blockquote>
<p class="MsoNormal">-- <br>
<b>Jammer<br>
<a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.jammer.biz%2F&data=04%7C01%7C%7C1d31709880ec4ba3a52608d961948ed4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637648113100355766%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=NvSv8Gg0BJOTPLSo%2FRbV4jxL8CIA%2FyLwBbSQDQgX5dA%3D&reserved=0">WWW.JAMMER.BIZ</a></b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>