Discussion:
bug#31554: Fwd: Re: Potential bug in md5sum
(too old to reply)
Riedy, Bill
2018-05-22 14:52:33 UTC
Permalink
I believe I've found a bug in md5sum when it attempts to calculate on a
hard linked file in NTFS on Windows 7.  Please read below for details.



-------- Forwarded Message --------
Subject: Re: Potential bug in md5sum
Date: Mon, 21 May 2018 19:22:32 +0200
From: Mathias Michaelis <***@gmail.com>
To: ***@users.sourceforge.net



Hi Bill

md5sum is a part of the GNU coreutils package,
http://www.gnu.org/software/coreutils/coreutils.html. It was ported by
the gnuwin32 Project to Windows:
http://gnuwin32.sourceforge.net/packages/coreutils.htm. The cause of the
error you've reported is probably the fact the the gnuwin32 version of
md5sum is from April 21, 2005.

I'm not the programmer neither of the original version nor of the ported
one of md5sum and I have not any skills to change something on the
current state of this tool.

I don't know if it helps but there is also a native windows solution out
there:

https://support.microsoft.com/en-us/help/841290/availability-and-description-of-the-file-checksum-integrity-verifier-u

With best regards

Mathias
Mathias, I'm not sure if your package contains md5sum, but I've been
looking for a way to get in touch with that packages owner. md5sum
appears to have an issue with hard links in NTFS on Windows 7. md5sum
appears to be creating a value from the hardlink itself, not following
the link to the "real" file. An example of this is calc.exe found in
c:\windows\system32. I've included a line of powershell to get this
information.
get-childitem c:\windows\system32\calc.exe | format-list fullname, target
FullName : C:\windows\system32\calc.exe
{C:\Windows\winsxs\amd64_microsoft-windows-calc_31bf3856ad364e35_6.1.7600.16385_none_05b2f2e2346cfea4\calc.exe}
md5sum (get-childitem c:\windows\system32\calc.exe | select-object
-expand fullname)
\60b7c0fead45f2066e5b805a91f4f0fc *C:\windows\system32\calc.exe
md5sum (get-childitem c:\windows\system32\calc.exe | select-object
-expand target)
\10e4a1d2132ccb5c6759f038cdb6f3c9
*C:\Windows\winsxs\amd64_microsoft-windows-calc_31bf3856ad364e35_6.1.7600.16385_none_05b2f2e2346cfea4\calc.exe
If I copy calc.exe to c:\temp and run the md5sum against that file I
get the value that begins with '10e4'
copy-item c:\windows\system32\calc.exe c:\temp -force
md5sum c:\temp\calc.exe
\10e4a1d2132ccb5c6759f038cdb6f3c9 *c:\temp\calc.exe
If you are not the appropriate person (which is likely) would you
happen to know who I can forward this information to? Thanks for any
help you can provide.
------------------------------------------------------------------------
This message was sent to you via the SourceForge web mail form.
You may reply to this message directly, or at
https://sourceforge.net/u/billr1965/profile/send_message
Paul Eggert
2018-05-23 01:00:47 UTC
Permalink
Post by Riedy, Bill
I believe I've found a bug in md5sum when it attempts to calculate on
a hard linked file in NTFS on Windows 7.
Could be, but this doesn't look like it's relevant to the current
codebase for GNU coreutils. 2005 was a looong time ago.
Assaf Gordon
2018-10-30 09:04:37 UTC
Permalink
close 31554
stop

(triaging old bugs)
Post by Paul Eggert
Post by Riedy, Bill
I believe I've found a bug in md5sum when it attempts to calculate on
a hard linked file in NTFS on Windows 7.
Could be, but this doesn't look like it's relevant to the current
codebase for GNU coreutils. 2005 was a looong time ago.
Given the above, I'm closing this bug.
Discussion can continue by replying to this thread.

-assaf
Riedy, Bill
2018-11-18 21:37:34 UTC
Permalink
The wording is vague, could you please clarify which of the following
are true:

1) That you recognize this as a bug and it is going to be fixed

2) That you recognize this as a bug but it will NOT be fixed

3) Some other scenario that I can't think of, but you may have.
This is an automatic notification regarding your bug report
#31554: Fwd: Re: Potential bug in md5sum,
which was filed against the coreutils package.
Thank you for your report, which has now been closed.
You can view the full report at
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31554
debbugs.gnu.org maintainers
(administrator, GNU bugs database)
Assaf Gordon
2018-11-19 00:44:00 UTC
Permalink
Hello Bill,
Post by Riedy, Bill
The wording is vague, could you please clarify which of the following
1) That you recognize this as a bug and it is going to be fixed
2) That you recognize this as a bug but it will NOT be fixed
3) Some other scenario that I can't think of, but you may have.
The original forwarded messaged said the following:

"md5sum is a part of the GNU coreutils package, [...]
It was ported by the gnuwin32 Project to Windows: [...]
The cause of the error you've reported is probably the fact the
gnuwin32 version of md5sum is from April 21, 2005."

( https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31554#5 )

Later, Paul replied:

"Could be, but this doesn't look like it's relevant to the current
codebase for GNU coreutils. 2005 was a looong time ago."

( https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31554#8 )

After which I've closed the bug report.

The meaning is:
The reported problem is happening
on a very old version of the program (from 2005 - 13 years old),
and using a port (GnuWin32) which GNU coreutils developers
did not create and can't easily provide support.

As such, there is no point in investigating further.
It could be a bug in the (very old) version, or it could
be another problem.

If you can reproduce the bug in a recent version (the current is 8.30).
then there would be more incentive to investigate (though once again,
the GnuWin32 is provided by others, and we can not easily support it).

regards,
- assaf

Continue reading on narkive:
Loading...