Scott,
I have a similar problem on blocking data write to CD. I would appreciate if you can tell me your “trick” that makes your filter work.
Thanks in advance, Jürgen.
Lower filter below CdRom and above storage port will suite. You will filter
the SCSI-level traffic. One of the ideas is to patch the response to READ DISK
INFORMATION to say that the disk is not writeable, or even fully emulate the
write protection according to MMC-5 spec.
Also note - Alcohol 120% hooks the storage port. So, I would suggest your
product to find the Alcohol’s driver and kill it. Yes, intentionally introduced
interop issue - warn the users about it.
Nero and IMAPI will still work - if your product’s settings will permit
this.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From:
To: “Windows System Software Devs Interest List”
Sent: Friday, November 03, 2006 12:15 PM
Subject: RE:[ntdev] CD /DVD read only filter
Scott,
I have a similar problem on blocking data write to CD. I would appreciate if
you can tell me your “trick” that makes your filter work.
Thanks in advance, Jürgen.
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
I would suggest you to write such a code snippet yourself. Write and sell it
not only to OP but also to Data Link Security, StarForce and Sony Multimedia
f.e. They are all incapable of having such a universal “seek and destroy”
solution for years… “With all the king’s horses and all the king’s men”
(c) … You could make a lot of money!
Anton
P.S. And I think finding binary image in memory and making it non-working is
still
illegal in U.S. I know you don’t care much about such a things in Russia but
guy from Germany could end his days in jail. Following your bright advices
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Friday, November 03, 2006 1:41 PM
To: Windows System Software Devs Interest List
Subject: Re: RE:[ntdev] CD /DVD read only filter
Lower filter below CdRom and above storage port will suite. You will
filter
the SCSI-level traffic. One of the ideas is to patch the response to READ
DISK
INFORMATION to say that the disk is not writeable, or even fully emulate the
write protection according to MMC-5 spec.
Also note - Alcohol 120% hooks the storage port. So, I would suggest
your
product to find the Alcohol’s driver and kill it. Yes, intentionally
introduced
interop issue - warn the users about it.
Nero and IMAPI will still work - if your product’s settings will permit
this.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From:
To: “Windows System Software Devs Interest List”
Sent: Friday, November 03, 2006 12:15 PM
Subject: RE:[ntdev] CD /DVD read only filter
Scott,
I have a similar problem on blocking data write to CD. I would appreciate if
you can tell me your “trick” that makes your filter work.
Thanks in advance, J?rgen.
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
>P.S. And I think finding binary image in memory and making it non-working is
still
illegal in U.S. I know you don’t care much about such a things in Russia but
guy from Germany could end his days in jail. Following your bright advices
We are speaking about the security software which is intended to disable
some of the computer/software functions according to some policy. The all
security software authors (let’s start from MS themselves with their IEAK) must
go to jail.
Also note that nobody will go to jail due to interop issues in the software
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
I have now implemented a filter driver below CdRom and above StoragePort (atapi in my test case) as a lower filter to CdRom. I see all the traffic and specifially GET_CONFIGURATION resp READ_DISC_INFORMATION opcodes depending on the drive.
My questions: To say that the disk is not writable, is it enough to patch the
- CurrentProfile in the GET_CONFIGURATION response resp
- the Erasable bit in the READ_DISC_INFORMATION response
I would tend to do the patch work in the respective completion routine and thus, take the srb->DataBuffer and amend the content appropriately. Is this the right way / place to do it? Could the SRB’s DataBuffer be accessed directly?
Before you get too far, you might want to know your solution isn’t going to work 100%. A lot (I emphasize a LOT) of 3rd party disc writing software sends SCSI commands not down the storage stack, but directly to the PDO. Hence, your filter is out of the loop. It has no chance of doing any write protection for this.
This situation is weakness in the driver architecture that was introduced with the advent of WDM. Before that, if a SCSI command was sent in such a way that it did not go through the layered stack that had claimed the device, it was rejected.
eof