Hi Norbert,<br><br>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 ;-)<br>
<br>All the best,<br><br> Javier<br><br><div class="gmail_quote">On Wed, Apr 23, 2008 at 10:03 PM, Norbert Hartl <<a href="mailto:norbert@hartl.name">norbert@hartl.name</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, 2008-04-23 at 11:28 -0700, tim Rowledge wrote:<br>
> On 23-Apr-08, at 10:35 AM, Norbert Hartl wrote:<br>
><br>
</div><div class="Ih2E3d">> > On Wed, 2008-04-23 at 15:00 +0200, Javier Reyes wrote:<br>
> >> Hi Edgar,<br>
> >><br>
> >> It's for a licensing server. I think I've found a way to do it using<br>
> >> the ethernet physical ID trough:<br>
> >><br>
> >> Applescript doIt: 'do shell script "ifconfig en0"'.<br>
> >><br>
> >> And then filtering the physical address.<br>
> >><br>
> > This won't work. Usually the MAC address shown is only a copy<br>
> > of the number stored on the device. You can alter this address<br>
> > easily.<br>
</div><div class="Ih2E3d">> I assume simply replacing the ethernet card - or even just adding one<br>
> and reassigning which is en0 - would mess it up pretty badly.<br>
><br>
> Many CPus have an actual unique ID that is findable somewhere. Even<br>
> there you're in trouble if the cpu has to be replaced due to failure<br>
> of upgrade.<br>
><br>
><br>
</div>Yes, that is hardly avoidable. I think that's the reason so many<br>
companies still use some sort of dongle.<br>
<font color="#888888"><br>
Norbert<br>
<br>
<br>
</font></blockquote></div><br>