• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: protecting software & uniquely identifying the machine
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: protecting software & uniquely identifying the machine


  • Subject: Re: protecting software & uniquely identifying the machine
  • From: Joe Morris <email@hidden>
  • Date: Tue, 18 Jun 2002 08:27:27 -0700 (PDT)

I believe this is a good idea and would also get around the brought up problems of restricting a user to a certain username. For those of you who are saying that you should be allowed to install it on multiple machines, that is true, but allowing that for free makes it impossible to prevent arbitrary distribution of the same ability to anyone over the internet. For those of you who say that adding some sort of user identification won't stop piracy: of course it won't. The only hope is to slow it or to stop casual piracy.

My plan, and the way that I've seen it done before that I enjoyed, is to keep a file of everyone who has paid for the software, and if they write an email to my contact point saying they need to reinstall on another machine, for whatever reason, I'll give them a new key. It takes little enough effort combined with the fact that I believe it won't happen very often that it would work well. Or at least the best of any other solutions mentioned here.

I too am interested in seeing code that could do this. :-)

Thanks!

-Joe

On Tuesday, 18, 2002, at 06:26AM, Marco Ippoliti <email@hidden> wrote:

>I am following this thread and I am concerned with the issue of uniquely
>identifying a machine (see also my question 'looking for a method to
>read 'production information').
>
>I understand that not every machine has a serial number (the older
>models don't, but this is not really an issue for me as I am more
>focused to later models and this information would be valuable).
>Nevertheless I am ready to switch to other methods and the Mac address
>as somebody mentioned in the thread (I guess he was meaning the ethernet
>address as method to identification), also seems to me a fairly good
>method as all machines have one (at least all those supporting OS X).
>
>Now, can someone show me an easy implementation (with code example) on
>how to extract this information (or the serial number for the matter)?
>
>Thank you,
>
>Marco
>_______________________________________________
>cocoa-dev mailing list | email@hidden
>Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
>Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: protecting software & uniquely identifying the machine
      • From: Rosyna <email@hidden>
    • Re: protecting software & uniquely identifying the machine
      • From: Chris Ridd <email@hidden>
  • Prev by Date: Image of a view
  • Next by Date: Re: protecting software & uniquely identifying the machine
  • Previous by thread: Re: Image of a view
  • Next by thread: Re: protecting software & uniquely identifying the machine
  • Index(es):
    • Date
    • Thread