![]() ![]() I don't understand what the problem is here > So why can't md5sum check the Windows made MD5 files? However when I make a MD5 in Linux using the -b command I get the ASTERISKS and as far as I can tell it looks EXACTLY like the Windows made MD5 and md5sum will successfully check it (and the same file even works in Windows). Again to be clear: The Windows made MD5 has the ASTERISKS but md5sum in Linux gives me errors when I try to check it (I get no such errors checking the same Windows made MD5 in Windows). I went back into MS Windows and from there I can successfully use the Linux made MD5 (the one made with the -b option) and it works. What the hell?Īnd if that isn't confusing enough. That makes sense but what doesn't make sense is that the Windows made MD5 (which looks EXACTLY like the Linux made MD5 with the -b option) gives me an error when trying to verify with md5sum. Now as you can imagine I can use md5sum to verify the Linux made MD5 and it works regardless of how the MD5 was made (be it with the -b option or without). In other words if I create a MD5 in Linux with the md5sum -b option then it looks EXACTLY like the MD5 made in Windows. However the MD5 using the -b option looks like my "Example A" in the above post. The MD5 without the -b option looks like my "Example B" in the above post. However I was reading about the -b binary option so I tried this: Well here is how I've been making my Linux MD5 files: I pointed out the difference in formatting between my MS Windows made MD5 files and the MD5 files that I create under Linux (again using Ubuntu 12.04 Beta 1 right now). #MD5 CHECKSUM WINDOWS 10 FULL#Is there a way around this formatting difference? Right now the only solution I see is to manually edit the MD5 file to remove all the of the ASTERISKS (since most of my MD5 files are Windows created and yet I'm now trying to convert myself full time to Linux via Ubuntu which means I need to check these Windows created MD5 files in Linux).īeen playing with this more since I posted the above and now I'm even more confused LOLĪs I said in the post above I can't seem to use the Linux 'md5sum' terminal command to check the MD5 files made in MS Windows without getting an error. When I try to check a MD5 made in Linux using Windows I also get an error (again due to the difference in formatting). So as I said when I try to use md5sum in Linux to check a MD5 made in Windows I'm given an error (wrong formatting). Instead there is a space where the ASTERISK would be. ![]() The Linux created MD5 file doesn't have the ASTERISKS. 253343b4d39e9e8b337a7db300d5e7dd *filename01.mkvĬd103030ad0dd35ecf0af1d6cc327417 *filename02.jpgĢ53343b4d39e9e8b337a7db300d5e7dd filename01.mkvĬd103030ad0dd35ecf0af1d6cc327417 filename02.jpgAs you can see the two are almost exactly the same other than the ASTERISK in front of the file names (in the Windows created MD5 file). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |