[Bug 14226] New: Busybox md5sum fails to support backslashes in filenames

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=14226

            Bug ID: 14226
           Summary: Busybox md5sum fails to support backslashes in
                    filenames
           Product: Busybox
           Version: 1.33.x
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at busybox.net
          Reporter: nils.rennebarth at web.de
                CC: busybox-cvs at busybox.net
  Target Milestone: ---

GNU coreutils md5sum since 2016 has a feature to make its output unambiguous
even in the presence of linefeeds in filenames: It prints the filename with
linefeeds escaped as \n. Of course that means is has to escape backslashes in
filenames as
well. To mark a line as containing an escaped filename, it then adds a '\' at
the start.

The busybox md5sum does not support this feature, and when run in check mode on
a file generated by GNU coreutils md5sum, it will mark the corresponding file
as 'FAILED'.

I checked the current sources and indeed, a line with an initial backslash is
not handled differently. I only reviewed the code that implements -c, for full
compatibility with GNU coreutils, generating md5sums will have to be adapted as
well.

I might provide a patch if requested, currently I am working around this
limitiation. Unfortunately, systemd decided to introduce filenames containing
backslashes (sigh).

-- 
You are receiving this mail because:
You are on the CC list for the bug.