Harddisk-cloning: possible to log that the source disk has been cloned?

  • Thread starter Thread starter StefanMueller65535
  • Start date Start date
S

StefanMueller65535

Hello!

I hope you can answer me a question:
I read in a magazine an article about copy protection and cloning. In
that article a programmer of a big software company said, it would be
possible to recognize, that a harddisk has been cloned or imaged.

?

Hmmm, I don't think so. If I connect a harddisk as slave to my PC and
don't start any software of that drive, how can this be identified? At
least a program which logs it anywhere must be executed as soon as the
source disk will be accessed. But how will this program be executed?

May be here is one assembler-programmer reading this:
Is it possible to add a small routine to the boot area of a
harddisk...or something like that...I guess you know what I mean)?

It would be interesting to read your thoughts about this!

Best,
Stefan
 
I hope you can answer me a question:
I read in a magazine an article about copy protection and cloning. In
that article a programmer of a big software company said, it would be
possible to recognize, that a harddisk has been cloned or imaged.

Hmmm, I don't think so. If I connect a harddisk as slave to my PC and
don't start any software of that drive, how can this be identified? At
least a program which logs it anywhere must be executed as soon as the
source disk will be accessed. But how will this program be executed?
May be here is one assembler-programmer reading this:
Is it possible to add a small routine to the boot area of a
harddisk...or something like that...I guess you know what I mean)?
It would be interesting to read your thoughts about this!

All drives have a readable serial number and
that can be used to check if that has changed.

It isnt rocket science and nothing to do with assembler at all.
 
Why should the serial number change when I read from a harddisk? I'm
talking about the source harddisk and not the target/new/cloned disk.

Stefan
 
Why should the serial number change when I read from a harddisk?

It doesnt, but it obviously changes when you clone a drive.
I'm talking about the source harddisk and not the target/new/cloned disk.

Ghost does write its own turd to a drive thats been the source with a clone.
 
It doesnt, but it obviously changes when you clone a drive.

No, it does not. Here the issue is that someone as a drive A
containing data he does not want to be copied. If someone can take the
drive A, and clone it on a B drive, putting back the A drive in the
computer, how can the owner of A know that the data as been cloned ?
Ghost does write its own turd to a drive thats been the source with a clone.

Ghost is one clone software among dozens.

Nick
 
No, it does not.

Corse it does. The original and the clone have to have different serial numbers.
Here the issue is that someone as a drive A
containing data he does not want to be copied.

There are obvious and completely bulletproof ways to secure that data.
If someone can take thedrive A, and clone it on a B
drive, putting back the A drive in the computer, how
can the owner of A know that the data as been cloned ?

The only viable approach is to ensure that even if the drive is
cloned, the clone will be completely useless access to data wise.

Completely routine and has been available for years and years now.

Most commonly used with laptops.
Ghost is one clone software among dozens.

You quite sure you aint one of those rocket scientist fellas ?
 
Corse it does. The original and the clone have to have different serial numbers.


There are obvious and completely bulletproof ways to secure that data.

Can I remind you the original question :
"
I hope you can answer me a question:
I read in a magazine an article about copy protection and cloning. In
that article a programmer of a big software company said, it would be
possible to recognize, that a harddisk has been cloned or imaged."

The question is not : "what happen if I change a drive?" or "how can I
secure the data?"

Nick
 
Can I remind you the original question :

I restored it to the quoting for a reason, stupid.
"I hope you can answer me a question:
I read in a magazine an article about copy protection and cloning. In
that article a programmer of a big software company said, it would
be possible to recognize, that a harddisk has been cloned or imaged."
The question is not : "what happen if I change a drive?"
or "how can I secure the data?"

Just another example of the wrong question, stupid.
 
I restored it to the quoting for a reason, stupid.

You went astray from the beginning, and again in the second answer. If
you clone a drive, you do not change the serial number of the source.
All this thread is about the source drive, not the destination.

Nick
 
You went astray from the beginning,

Nope. I answered the question that should have been asked.

I always do that when the wrong question is asked.
and again in the second answer.

Wrong again.
If you clone a drive, you do not change the serial number of the source.

Never said you did, ****wit.
All this thread is about the source drive, not the destination.

Thanks for that completely superfluous proof
that you've never ever had a ****ing clue.
 
Speedo wacko.

Rod Speed said:
Nope. I answered the question that should have been asked.

I always do that when the wrong question is asked.


Wrong again.


Never said you did, ****wit.


Thanks for that completely superfluous proof
that you've never ever had a ****ing clue.
 
Nope, he asked the wrong question and that was meaningless.

YOU say so. I feel it is an interesting question to know if there is a
way to detect the cloning of a drive

Nick
 
I hope you can answer me a question:
I read in a magazine an article about copy protection and cloning. In
that article a programmer of a big software company said, it would be
possible to recognize, that a harddisk has been cloned or imaged.

All hard drives have a unique serial number embedded in their firmware.
If an application can access this serial number it can tell whether it was
moved to a different drive.
That is, it can hide an encrypted number in the Windows registry
during the application Setup process then refer to this anytime you run
the app.

Now to obtain the number - for windows NT, 2000 and XP/2003 Server the
installer has to be running as "LocalSystem" to be able to issue the
system call that returns device ID.

hope this helps....
 
Rod Speed said:
Nope, he asked the wrong question and that was meaningless.

The question was fine.
Whether he truly understood the article he read is an entirely other matter.
 
Its obvious to anyone with a clue so.


Corse there cant be.

So that's what you should have said from the beginning, and only after
you could have said anything you find relevant. Not the other way
round.

Nick
 
Back
Top