Re: Locking Down a File
- From: "Lloyd Dupont" <net.galador@ld>
- Date: Wed, 25 Jan 2006 19:34:32 +1000
One idea, though..
You might use a trusted (so it has right to write on the file system) click
once application?
If you can, the you're back in business ;-)
"Corey B" <theburnetts@xxxxxxxxx> wrote in message
news:1138156410.455241.297020@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> I'm not sure I understand what you mean. How can I keep a FileStream
> reference to the file open when the file has been downloaded to their
> PC? It won't be on the web server. The system will process their data
> and then just stream the XML file down to the browser. So the file
> won't actually ever live on the web server. The file will be on the
> user's PC. Then after some time (Could be a day - could be a year) the
> user can re-upload the file to the web server and continue working. I
> just wondered if there was some way that I could protect the file so
> that the user doesn't tamper with it. I will probably encrypt it
> before streaming it down to the user. But in the end the file is just
> a simple text file and the user could open it up in a text editor and
> mess with it. And then the uploading of the file would fail and they
> would lose their work. I was hoping that there is some sort of built
> in .NET method of protecting the file. Or even a 3rd party component
> would work too.
>
> Corey
>
.
- References:
- Locking Down a File
- From: Corey B
- Re: Locking Down a File
- From: Lloyd Dupont
- Re: Locking Down a File
- From: Corey B
- Locking Down a File
- Prev by Date: Re: Locking Down a File
- Next by Date: RE: Dynamic configuration file?
- Previous by thread: Re: Locking Down a File
- Next by thread: Re: Locking Down a File
- Index(es):
Relevant Pages
|
