> So to suggest that your perceived EFS flaw can be resolved by over-writing > is naive. The only solution is to encrypt in memory or use some removable > partition as the temp space. > I agree with the use of 'percevied' in this case. Though the behavior is interesting in regard to the creation of the unencrypted .tmp file, I believe this more of a procedural issue than an implementation one. Recommended EFS procedures call for the encryption of a direcory, not file-by-file as the procedure indicated by Berglind suggests. If you copy an unencrypted file and paste it into an encrypted directory, the file and the temporary file are both encrypted. This is actually covered in the docs regarding EFS. HTH. --------------------------------- Attonbitus Deus [EMAIL PROTECTED]
- BugTraq: EFS Win 2000 flaw Rickard Berglind
- Re: BugTraq: EFS Win 2000 flaw Alexander Ivanchev
- Re: BugTraq: EFS Win 2000 flaw Dan Kaminsky
- Re: BugTraq: EFS Win 2000 flaw Russ
- Re: BugTraq: EFS Win 2000 flaw Ryan Russell
- Re: BugTraq: EFS Win 2000 flaw Dan Kaminsky
- Re: BugTraq: EFS Win 2000 flaw Timothy J. Miller
- Re: BugTraq: EFS Win 2000 flaw Jeremy Epstein
- Re: BugTraq: EFS Win 2000 flaw Attonbitus Deus
- Re: BugTraq: EFS Win 2000 flaw Dan Kaminsky
- Re: BugTraq: EFS Win 2000 flaw Attonbitus Deus
- Re: BugTraq: EFS Win 2000 flaw Kirk Corey
- Re: BugTraq: EFS Win 2000 fla... Attonbitus Deus
- Re: BugTraq: EFS Win 2000 flaw Bryce Walter
- Re: BugTraq: EFS Win 2000 flaw Fulmer, John
- Re: BugTraq: EFS Win 2000 flaw Russ
- Re: BugTraq: EFS Win 2000 flaw Grubin, Ben
- Re: BugTraq: EFS Win 2000 flaw Abe Getchell
- Re: BugTraq: EFS Win 2000 flaw John Wiltshire