Is there a cross-platform Java method to remove filename special chars?

后端 未结 8 1575
太阳男子
太阳男子 2021-01-31 13:26

I\'m making a cross-platform application that renames files based on data retrieved online. I\'d like to sanitize the Strings I took from a web API for the current platform.

相关标签:
8条回答
  • 2021-01-31 14:06

    This is based on the accepted answer by Sarel Botha which works fine as long as you don't encounter any characters outside of the Basic Multilingual Plane. If you need full Unicode support (and who doesn't?) use this code instead which is Unicode safe:

    public class FileNameCleaner {
      final static int[] illegalChars = {34, 60, 62, 124, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 58, 42, 63, 92, 47};
    
      static {
        Arrays.sort(illegalChars);
      }
    
      public static String cleanFileName(String badFileName) {
        StringBuilder cleanName = new StringBuilder();
        int len = badFileName.codePointCount(0, badFileName.length());
        for (int i=0; i<len; i++) {
          int c = badFileName.codePointAt(i);
          if (Arrays.binarySearch(illegalChars, c) < 0) {
            cleanName.appendCodePoint(c);
          }
        }
        return cleanName.toString();
      }
    }
    

    Key changes here:

    • Use codePointCount i.c.w. length instead of just length
    • use codePointAt instead of charAt
    • use appendCodePoint instead of append
    • No need to cast chars to ints. In fact, you should never deal with chars as they are basically broken for anything outside the BMP.
    0 讨论(0)
  • 2021-01-31 14:07

    As suggested elsewhere, this is not usually what you want to do. It is usually best to create a temporary file using a secure method such as File.createTempFile().

    You should not do this with a whitelist and only keep 'good' characters. If the file is made up of only Chinese characters then you will strip everything out of it. We can't use a whitelist for this reason, we have to use a blacklist.

    Linux pretty much allows anything which can be a real pain. I would just limit Linux to the same list that you limit Windows to so you save yourself headaches in the future.

    Using this C# snippet on Windows I produced a list of characters that are not valid on Windows. There are quite a few more characters in this list than you may think (41) so I wouldn't recommend trying to create your own list.

            foreach (char c in new string(Path.GetInvalidFileNameChars()))
            {
                Console.Write((int)c);
                Console.Write(",");
            }
    

    Here is a simple Java class which 'cleans' a file name.

    public class FileNameCleaner {
    final static int[] illegalChars = {34, 60, 62, 124, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 58, 42, 63, 92, 47};
    static {
        Arrays.sort(illegalChars);
    }
    public static String cleanFileName(String badFileName) {
        StringBuilder cleanName = new StringBuilder();
        for (int i = 0; i < badFileName.length(); i++) {
            int c = (int)badFileName.charAt(i);
            if (Arrays.binarySearch(illegalChars, c) < 0) {
                cleanName.append((char)c);
            }
        }
        return cleanName.toString();
    }
    }
    

    EDIT: As Stephen suggested you probably also should verify that these file accesses only occur within the directory you allow.

    The following answer has sample code for establishing a custom security context in Java and then executing code in that 'sandbox'.

    How do you create a secure JEXL (scripting) sandbox?

    0 讨论(0)
  • 2021-01-31 14:09

    Paths.get(...) throws a detailed exception with the position of the illegal character.

    public static String removeInvalidChars(final String fileName)
    {
      try
      {
        Paths.get(fileName);
        return fileName;
      }
      catch (final InvalidPathException e)
      {
        if (e.getInput() != null && e.getInput().length() > 0 && e.getIndex() >= 0)
        {
          final StringBuilder stringBuilder = new StringBuilder(e.getInput());
          stringBuilder.deleteCharAt(e.getIndex());
          return removeInvalidChars(stringBuilder.toString());
        }
        throw e;
      }
    }
    
    0 讨论(0)
  • 2021-01-31 14:09

    If you want to use more than like [A-Za-z0-9], then check MS Naming Conventions, and dont forget to filter out "...Characters whose integer representations are in the range from 1 through 31,...", like the example of Aaron Digulla does. The code e.g. from David Carboni would not be sufficient for these chars.

    Excerpt containing the list of reserved characters:

    Use any character in the current code page for a name, including Unicode characters and characters in the extended character set (128–255), except for the following:

    The following reserved characters:

    • < (less than)
    • > (greater than)
    • : (colon)
    • " (double quote)
    • / (forward slash)
    • \ (backslash)
    • | (vertical bar or pipe)
    • ? (question mark)
    • * (asterisk)
    • Integer value zero, sometimes referred to as the ASCII NUL character.
    • Characters whose integer representations are in the range from 1 through 31, except for alternate data streams where these characters are allowed. For more information about file streams, see File Streams.
    • Any other character that the target file system does not allow.
    0 讨论(0)
  • 2021-01-31 14:10

    It is not clear from your question, but since you are planning to accept pathnames from a web form (?) you probably ought block attempts renaming certain things; e.g. "C:\Program Files". This implies that you need to canonicalize the pathnames to eliminate "." and ".." before you make your access checks.

    Given that, I wouldn't attempt to remove illegal characters. Instead, I'd use "new File(str).getCanonicalFile()" to produce the canonical paths, next check that they satisfy your sandboxing restrictions, and finally use "File.exists()", "File.isFile()", etc to check that the source and destination are kosher, and are not the same file system object. I'd deal with illegal characters by attempting to do the operations and catching the exceptions.

    0 讨论(0)
  • 2021-01-31 14:13

    There's a pretty good built-in Java solution - Character.isXxx().

    Try Character.isJavaIdentifierPart(c):

    String name = "name.é+!@#$%^&*(){}][/=?+-_\\|;:`~!'\",<>";
    StringBuilder filename = new StringBuilder();
    
    for (char c : name.toCharArray()) {
      if (c=='.' || Character.isJavaIdentifierPart(c)) {
        filename.append(c);
      }
    }
    

    Result is "name.é$_".

    0 讨论(0)
提交回复
热议问题