Re: How to block system copy commands at driver level
- From: "Maxim S. Shatskih" <maxim@xxxxxxxxxxxxxxxx>
- Date: Sat, 24 May 2008 04:17:09 +0400
At driver level, you cannot distinguish the copy from the new file
creation.
The idea is futile.
--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com
"Bipin Mistry" <bpnmistry@xxxxxxxxx> wrote in message
news:6a3688db-4c57-4671-a27c-30043ef6aa32@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
How can I trace following System Copy commands and block them, so as
secured folder/drive do not react to these commands.
1. [Ctrl + C],
2. Right Click Menu -> Copy
3. File Menu -> Copy
4. Command prompt copy
As per me all above command will be calling a single rutine process at
driver level.
I am unable to identify which rutine dose it call & how can I identify
that the any of above 4 are triggered.
During my RnD till now I reached till IRP_MJ_READ & WRITE where by
related parameters and their properties do not describe about COPY in
specifically.
Some place I read about this can be posible with keeping watch on
Clipboard, dont know how much this will be useful, as there was no
extra informaiton was provided.
If any one can help me out for this situation then please do share
your knowledge with me.
Best regards,
Bipin
.
- Follow-Ups:
- Re: How to block system copy commands at driver level
- From: Bipin Mistry
- Re: How to block system copy commands at driver level
- References:
- How to block system copy commands at driver level
- From: Bipin Mistry
- How to block system copy commands at driver level
- Prev by Date: Re: Ndis Driver Type
- Next by Date: Re: Message Signaled interrupt? more question
- Previous by thread: Re: How to block system copy commands at driver level
- Next by thread: Re: How to block system copy commands at driver level
- Index(es):
Relevant Pages
|
Loading