Re: Encryption FAQ

Is anyone else interested in working on this? I would at least prefer that
someone else does proof reading; I am far too technical to create something that is
good reading :wink:
Some questions you would like answered would also come in handy, in case I can’t
remember all.

I am currently using Help&Manual to create the FAQ, which I think will be the
perfect way for now. It will be fairly easy to transfer to a wiki type page later,
and easy to read and navigate for now.

Dejan.

“David J. Craig” wrote:

Why not make it a generic active filter instead of just encryption? Compression and
encryption are closely related, though compression does mean that the file size as
it exists on the storage is, I hope, smaller than the real size of the file. With
headers or trailers encryption encounters some of the same issues as whole file
compression. Also denying access or redirecting a file to another file are also
issues about which I have seen a lot of posts. Luckily with the minifilter
swapBuffers, some of the more
difficult questions have been answered.

Are you are planning to answer questions about encryption such as:
How do I store the symmetric encryption key?
How do I create a symmetric encryption key?
How much data should a symmetric encryption key be used to encrypt?
How do I handle cipher block chaining (CBC), or do I need it?
How many bits should the encryption key contain?
If the encryption key is provided by a user prompt, how long should it be
and how to redistribute the bits so it is a strong key?
Should an ADS be used to store the key? What about FAT?
What encryption algorithm should I use?
Should I use the TPM?
How do I identify the encrypted files? What IRP should be used to trigger
the identification? Dispatch or completion?
What data is available in dispatch that will be needed in the completion
routine and also in the converse?
What legalities must I consider in considering the above questions?

–
King regards, Dejan
http://www.alfasp.com
File system audit, security and encryption kits.