• 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
protecting software & uniquely identifying the machine
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

protecting software & uniquely identifying the machine


  • Subject: protecting software & uniquely identifying the machine
  • From: Marco Ippoliti <email@hidden>
  • Date: Tue, 18 Jun 2002 15:26:38 +0200

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.

  • Follow-Ups:
    • Re: protecting software & uniquely identifying the machine
      • From: Rosyna <email@hidden>
  • Prev by Date: Re: Protecting Software w/ Software License Keys...
  • Next by Date: Re: Protecting Software w/ Software License Keys...
  • Previous by thread: Re: looking for a method to read 'production information'
  • Next by thread: Re: protecting software & uniquely identifying the machine
  • Index(es):
    • Date
    • Thread