Avoid Cloning

[Guest]

Hi,
I have a question regarding cloning.

Can someone give a tip what can I do in order to avoid somebody to clone my
embeded image after release?. I'm using fbreseal; I get different SID, and
computer name for each image I install in a system, but I have noticed that
after running the first boot (FBA) the HD can be cloned and works without
problem. Is there a way windows can identify that is running in different
hardaware than the first time?. I'm using Sp1.

Thanks for your help.
GL

 

[Slobodan Brcin \(eMVP\)]

Hi GL,

AFAIK there is no way integrated in XPe to prevent such thing :-(
You must create your solution that will lock to certain hardware and refuse
to work on other hardware types.

Also you should send feedback on your concers to MS:
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx

Regards,
Slobodan

 

[KM]

GL,

A while ago we have discussed similar subject in the NG:
http://groups-beta.google.com/group...a661a171e9e/7a1c36be82e1b72f#7a1c36be82e1b72f

Basically, your images with legally purchased runtime licencies should be covered by US law. You can read more details in the EULA.

For the image protection... Technically there is a bunch of simple things you can do to prevent cloning on XPe - e.g. reading disk
serial numbers at run time - but, frankly, any security mechanism can be broke (hacked) unless you lock the hardware itself.
Also, encripting the disk data (some protection code can be implemented in BIOS) with some good certified algorithm provided with
long bit key may help.

KM

 

[JC]

To follow up on this, I would suggest, under the "hardware" locking idea,
that you trim the OS down to prevent PnP acquisition of new devices, and
only install the drivers for the devices you have installed... Critical
components, like Display adapters, Chipsets, Ethernet controllers, etc will
cause BSOD's often times if windows does not detect the correct ones at
boot. I have done that to better secure the device... it's kind of a pain,
but it works... then if they clone it, it's useless without a TON of work

just a thought.

HTH,
JC

 

[Guest]

I got the Idea that XpE can do something for this because in the way of
looking for Ideas I tried to clone my developer PC HD with Windows XP Pro SP1
and I noticed that when I installed the HD in a computer with exactly the
same hardware ( Motherboard, Processor, Video Card and RAM ) at boot up
Windows sent a message regarding licensing issue and I was unable to work
with it. So I got happy!. but this does not happen with my XpE image.

Why is this?
GL

 

[KM]

GL,

Was the size of that HDD very different from the size of the HDD used during FBA? (different from partition size specified in TD
Configuration Target Device Settings) then the SYSTEM_LICENSE_VIOLATION BSOD is explainable.

Also, please think about the potential use of your image if stolen. The image itself is probably useless to anybody. For end users
it is also not useless (not XP Pro, no Office, etc.). The image, however, is protected legally by US law.
So, you may really want to think about protecting (encrypting, hiding, etc.) your own applications data.

KM

 

[Slobodan Brcin \(eMVP\)]

GL,

On XP Pro activation is connected to serial numbers of HDD, network
adapters, amount of memory, procesor type, and few other things. And only
one or two changes of those are tolerated.
XPe on the other hand is locked to OS partition size, and even this work
strange it looks more than a bug then a intended feature.
Anyhow like Konstantin said you will have to make your protection, althouh
you should send feature request feedback to MS asking for some kind of
optional protection. (At least is will rise awarenes in product team that
there is a semand for this option)

Regards,
Slobodan

 

[KM]

Was the size of that HDD very different from the size of the HDD used during FBA? (different from partition size specified in TD

Configuration Target Device Settings) then the SYSTEM_LICENSE_VIOLATION BSOD is explainable.

Also, please think about the potential use of your image if stolen. The image itself is probably useless to anybody. For end users
it is also not useless (not XP Pro, no Office, etc.).

I meant to say the image is useless to regular XP Pro users too.

Sorry for any confusion created.

KM