I recently had an issue with restricted filenames.
Normally windows will not let you create a file that has one of the restricted filenames, this is a hangover from windows past.
CON, AUX, COM1, COM2, COM3, COM4, LPT1, LPT2, LPT3, PRN, NUL
One of the systems used a UNC reference to access storage on a remote server share. By using the UNC the access allowed the system to create a file called con.xxxxx.doc, this file was in fact an uploaded user file.
The problem came when a backup process tried to access the file locally and compress and encrypt it. The process failed because of the file name.
So what to do. In the end I used the same trick that allowed the file to be created. I just referenced the file using a unc (\\servername\c$\…. etc..) rather than locally (c:\…. etc..)
No comments:
Post a Comment