Small oops, Radi's reply was missing the CC to list.

Le lundi 18 octobre 2010 à 16:31 +0100, Radi, Rami a écrit :

> I was looking actually for a system unique identifier, exactly as you
> say using the IMEI on phones.
> 
>  
> 
> Thinking that since MeeGo will in most cases run on x86 IA,  this
> would be something nice to add to the SDK, so that the developer
> doesn’t have to worry about how to get the CPUID, etc.
> 
>  
> 
> Plus, do you really think that getting the CPUID would be sufficient? 


From what I've read so far, there exist a controversy about privacy with
those API. As an example, a special version of Android (TaintDroid), has
been used to demonstrate that many applications can throw your phone
number or IMEI over the Internet, not maliciously, but as a unique
identifier. It would have been very easy for those application to hash
the information prior to sending it, but I do think that having a
function that will always do it right is a better solution.

Now, we could create a Meego specific API, or try and generate the
file /etc/hostid (or call sethostid()) with platform specific backend
(IMEI/phone numbers on phones, CPUID, etc) and use gethostid(). That is
unless there is other issues I'm not aware about this POSIX function.

regards,
Nicolas

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to