Question

I am in the beginning stages of developing a solution to decrypt the hard drives of a few thousand laptops.

I have a thought that it would be useful to create a parent application that would handle all of the database calls, client updates, client commands and status updates. This application would either run as a service or as a .EXE from the computers start up.

Then have a child application perform all of the decryption and verification duties with logging to a XML file.

It is the child that I am thinking may need to be updated in the event new functionality is needed. That is where I am trying to think of the most logical way of updating it, my first thought went to storing it in SQL as a BLOB, and then pulling it down from the parent application if needed.

Does this sound reasonable? One item to note is that my target computers are all at .NET 2.0.

Answer 1

Possible? Probably. Recommended? Probably not.

Is there any reason why you can’t store the executable on a file share and have an entry in the database which points to a UNC path for the client to collect the file itself.

The file share is best for serving files so use it as such.