You could try to flush all the file content and then unlink it. Anyway the information is destroyed.
The Camel Book describes what you need to do to avoid race conditions using sysopen. Using file locking also should help to make it more secure too (but I'm not sure if flock() will work fine in Win32, I never used it there).
In reply to Re: Secure delete ie shred a file
by glasswalk3r
in thread Secure delete ie shred a file
by fluffyvoidwarrior
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |