I am in the early stages of developing a solution for decrypting the hard drives of several thousand laptops.
I thought it would be useful to create a parent application that will handle all database calls, client updates, client commands, and status updates. This application will start as a service or as .EXE from the startup computer.
Then the child application performs all the responsibilities of decryption and verification when entering the XML file.
This is a child that I think may need to be updated if new functionality is needed. That's where I try to think of the most logical way to update it, my first thought was to store it in SQL as a BLOB, and then, if necessary, pull it from the parent application.
Does that sound reasonable? One of the notes - my target computers are on .NET 2.0.
source
share