Prev: NdisOpenConfigurationKeyByIndex returns KeyName not NULL terminate
Next: Pnpd Test Failure in Vista x64
From: G�nter Prossliner on 27 Oct 2009 10:17
Hello divya!

> A driver has to be written such that when
> Input to MS-Word open is given as Z:base 32 encoded string

(you meen base64?)

If you only have to support Word (or Office), than you can use the "Open by
URL" feature from Word and implement a usermode Web-Server. Even storing is
possible when you implement the needed HTTP Verbs (WebDAV).

You can easyly check which verbs you have to implement by using a HTTP
Debugging Proxy (like "Fiddlertool") and open a .doc File on a local
Web-Share.

The User (or any kind of Office-Automatiation?) would not choose
"Z:\base64string" but "http://localhost/xy/base64string".

If you use the HTTPAPI (or e.g. the HttpListener Class in the .NET
Framework), you have a complete HTTP-Server Implementation provided and you
can concentrate on the logic, not the protocol. And you can listen on Port
80 even if there is an IIS runing on Port 80. Your application justs uses an
URL-Pattern (like http://*.80/xy in the example above).


So you don't need to write a FS (Filter) if that's of for you.


GP


From: Pavel A. on 27 Oct 2009 23:30
"divya" <divya(a)discussions.microsoft.com> wrote in message
news:0D01B1ED-6030-467A-B6BD-ED1C7463B922(a)microsoft.com...
> problem statement:
> A driver has to be written such that when
> Input to MS-Word open is given as Z:base 32 encoded string
> Here, Z: is the drive which is not existing
> base 32 encoded string: path to the encrypted file which is to be
> opened;key;iv

The Office apps have lot of tweakable points.
Opening a file is one for these points for sure.
Just use what Office provides, don't mess with drivers

--pa


From: G�nter Prossliner on 28 Oct 2009 05:50
Hello again (if you are still out there)


> If you only have to support Word (or Office), than you can use the
> "Open by URL" feature from Word and implement a usermode Web-Server.
> Even storing is possible when you implement the needed HTTP Verbs
> (WebDAV).

Just seen that you want to implement encryption. In this case opening from
HTTP will not be the "safest" way to do this ;-), because the unencrypted
data is transfered over local networking.

But be aware of the fact that windows supports encryption out of the box and
that there are other products that allows to do per-file encryption.


GP


From: divya on 30 Oct 2009 06:38
Thank you for your reply.
My actual requirement is as follows:
we have a browser and when we open files through that , they also get opened
in temp folder. In order to prevent the files to be opened in temp, we have
decided to use a driver to open files. whenever browser opens a file, it
should call driver to open that file instead. Therefore, input to the driver
is given as a base 32 encoded string. Driver when called, it decodes and then
reads the encrypted file, decrypts it and writes to a file. This file is
launched using shellExecute() in usermode code.
but, I dont know how to get to know the event of closing the launched file.
Since, after the file is closed, again i have to perform encryption to that
file.

"Pavel A." wrote:

> "divya" <divya(a)discussions.microsoft.com> wrote in message
> news:0D01B1ED-6030-467A-B6BD-ED1C7463B922(a)microsoft.com...
> > problem statement:
> > A driver has to be written such that when
> > Input to MS-Word open is given as Z:base 32 encoded string
> > Here, Z: is the drive which is not existing
> > base 32 encoded string: path to the encrypted file which is to be
> > opened;key;iv
>
> The Office apps have lot of tweakable points.
> Opening a file is one for these points for sure.
> Just use what Office provides, don't mess with drivers
>
> --pa
>
>
First  |  Prev  | 
Pages: 1 2
Prev: NdisOpenConfigurationKeyByIndex returns KeyName not NULL terminate
Next: Pnpd Test Failure in Vista x64