<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">8.11.2013 16:18, Marcin M.:<br>
</div>
<blockquote
cite="mid:CANaCrSTbyy3qxQtGozJ0EcYmhUQpsAYo8AG5P_QVEczFSd+LFQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>Well, this all anty-piracy campaign is going too far!
:) Who lives by the sword, dies by the sword. <br>
<br>
1. People who won't have money - won't buy. If they
can't use the apps, they won't use the system. And
choose Android/Jailbroken iOS<br>
</div>
2. It's becoming a little spy-like to send data from
device to the manufacturer's servers! It's not IE to
access internet from your device and vice versa<br>
</div>
</div>
</div>
</div>
</blockquote>
I'll point to all the criticism Canonical is currently facing due to
the DASH privacy issues & their botched handling of it (most
recent being the fixubuntu case).<br>
<br>
Also regarding the previously mentioned IMEI checking, just
something to think about in regards of leaking the IMEI:<br>
<a class="moz-txt-link-freetext" href="http://mobile.slashdot.org/story/12/09/08/2126234/whatsapp-is-using-imei-numbers-as-passwords">http://mobile.slashdot.org/story/12/09/08/2126234/whatsapp-is-using-imei-numbers-as-passwords</a><br>
<br>
<blockquote
cite="mid:CANaCrSTbyy3qxQtGozJ0EcYmhUQpsAYo8AG5P_QVEczFSd+LFQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>3. How can we detect if someone installed a free version
from "<a moz-do-not-send="true" href="http://talk.maemo.org"
target="_blank">talk.maemo.org</a>" instead of buying the
same version from Harbor? What about being given the package
by the developer?<br>
<br>
</div>
<div>I think that there's no use in write a complicated copy
protection library. The optimal option is to just make
installing (just using CLI would discourage many). If
someone wants to crack, he'll crack anyway or not use the
platform at all.<br>
<br>
</div>
<div>And... Losing warranty after dev mode? Please elaborate.<br>
</div>
</div>
</div>
</blockquote>
Also interested to hear a clarification to this.<br>
<blockquote
cite="mid:CANaCrSTbyy3qxQtGozJ0EcYmhUQpsAYo8AG5P_QVEczFSd+LFQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<br>
</div>
Regards,<br>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div>--</div>
Marcin<br>
</div>
<br>
<br>
<div class="gmail_quote">2013/11/8 Andrey Kozhevnikov <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:coderusinbox@gmail.com" target="_blank">coderusinbox@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Well. As Harmattan havent copy protection at all, developers
started creating own methods for detecting if application is
*really* bought by user. And it was done using osa binaries.
You can always get application source, and if it osa -
application installed from Store (means paid applicatioin
was bought).<br>
<br>
I see following:<br>
<br>
Lightweight library provides methods for developer to detect
if application installed from Harbour (bought actually) or
not. Daemon side of library handles this calls and send
negative results to Harbour servers. This protection library
should provide also some kind of *sandbox*. Functions,
included into sandbox will be executed in safe threads and
will be self-obfuscated and protected from modifications.
Any byte changing *sandbox* part of application cause
showing warning screen when application starting,
application became misbehave or quiting after some period of
time, and sending information to Harbour servers.<br>
<br>
And developer can choose which strategy application will
use: easy or hard, or make own methods based on easy *is
bought?* checks.
<div class="HOEnZb">
<div class="h5"><br>
<br>
On 08.11.2013 12:02, Jonni Rainisto wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
That's good, but what I don't get in that case is...
does that<br>
coincidentally mean "enable developer mode" ==
"disable copy protection"?<br>
</blockquote>
It doesn't mean that. It will be lightweight, does
not limit resources and does not care what mode you
are on. People will just have to wait for untill its
ready before more datails will be available. But feel
free to give suggestions what kind of API's you would
prefer to have as a developer in Harbour to make your
life easier.<br>
<br>
re, Jonni<br>
________________________________________<br>
From: <a moz-do-not-send="true"
href="mailto:devel-bounces@lists.sailfishos.org"
target="_blank">devel-bounces@lists.sailfishos.org</a>
[<a moz-do-not-send="true"
href="mailto:devel-bounces@lists.sailfishos.org"
target="_blank">devel-bounces@lists.sailfishos.org</a>]
on behalf of Attila Csipa [<a moz-do-not-send="true"
href="mailto:qt@csipa.in.rs" target="_blank">qt@csipa.in.rs</a>]<br>
Sent: Friday, November 08, 2013 2:37 AM<br>
To: Mohammed Hassan; Sailfish OS Developers<br>
Subject: Re: [SailfishDevel] Jolla Harbour and Jolla
Store<br>
<br>
On 07-Nov-13 15:51, Mohammed Hassan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Not quite :) What I'm interested in is what *will*
be there (or,<br>
rather, what resources will it limit) as opposed
to what is NOT<br>
going to be there (whether not having Aegis there
is good, or bad,<br>
depends on what you will have there instead is
better or worse than<br>
Aegis).<br>
</blockquote>
As Jonni said:<br>
After you enable developer mode, you have _true_
root access to the device<br>
and can freely replace system binaries and do what
ever you want with your<br>
device (you may lose warranty when you enable
developer mode).<br>
</blockquote>
That's good, but what I don't get in that case is...
does that<br>
coincidentally mean "enable developer mode" ==
"disable copy protection"?<br>
<br>
Best regards,<br>
Attila<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
</blockquote>
<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SailfishOS.org Devel mailing list</pre>
</blockquote>
<br>
</body>
</html>