Hi Norbert,

You are absolutely right. In my case though, I am protecting a small
application with a small number of users. More than a bullet proof system, a
deterrant is enough. I could even feel flatered if someone took seriously
cracking it  ;-)

All the best,

                     Javier

On Wed, Apr 23, 2008 at 10:03 PM, Norbert Hartl <norbert at hartl.name> wrote:

> On Wed, 2008-04-23 at 11:28 -0700, tim Rowledge wrote:
> > On 23-Apr-08, at 10:35 AM, Norbert Hartl wrote:
> >
> > > On Wed, 2008-04-23 at 15:00 +0200, Javier Reyes wrote:
> > >> Hi Edgar,
> > >>
> > >> It's for a licensing server. I think I've found a way to do it using
> > >> the ethernet physical ID trough:
> > >>
> > >> Applescript doIt: 'do shell script "ifconfig en0"'.
> > >>
> > >> And then filtering the physical address.
> > >>
> > > This won't work. Usually the MAC address shown is only a copy
> > > of the number stored on the device. You can alter this address
> > > easily.
> > I assume simply replacing the ethernet card - or even just adding one
> > and reassigning which is en0 - would mess it up pretty badly.
> >
> > Many CPus have an actual unique ID that is findable somewhere. Even
> > there you're in trouble if the cpu has to be replaced due to failure
> > of upgrade.
> >
> >
> Yes, that is hardly avoidable. I think that's the reason so many
> companies still use some sort of dongle.
>
> Norbert
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20080424/674b2b53/attachment.htm