Protect input data stored in external files (or Deserialize encoded xml file? (serialized and encoded))

[Magnus]

I'm currently developing an application with classified information as
input to a couple of algorithms.
Which strategy should I use to protect the input data from beeing read?

The files should be files on the local computer in the application
directory structure and it must be possible to update the input data
with an external application.

My current approach is to deserialize the input data in the "external
application" and then encode the xml file line by line. But how do I
decode the data before I deserialize it without using the harddisk to
store a temporary decoded file. I do not want to store it temporarily
if the application crash before the temp file is removed...

I have specified the input data in an xml schema.

Are there other ways to solve the problem?

Regards
/Magnus

[Laura T.]

I assume you are using XmlSerializer.
You could read the file, decode it and put it in a MemoryStream that you
then pass to XmlSerializer as the input stream.

Laura.

"Magnus" <su*****@hotmail.com> ha scritto nel messaggio
news:11**********************@e56g2000cwe.googlegr oups.com...

I'm currently developing an application with classified information as
input to a couple of algorithms.
Which strategy should I use to protect the input data from beeing read?

The files should be files on the local computer in the application
directory structure and it must be possible to update the input data
with an external application.

My current approach is to deserialize the input data in the "external
application" and then encode the xml file line by line. But how do I
decode the data before I deserialize it without using the harddisk to
store a temporary decoded file. I do not want to store it temporarily
if the application crash before the temp file is removed...

I have specified the input data in an xml schema.

Are there other ways to solve the problem?

Regards
/Magnus

[Magnus]

Correct, XmlSerializer.
I'll try the MemoryStream approach, thank you!

Magnus