Talk:Simple file verification

From Wikipedia, the free encyclopedia

  1. What if all files where transmitted correctly, but not the corresponding SFV file, therefore raising a false-positive transmission error?
  2. What if files got corrupted and so did the SFV file - in such a way that the corrupted checksum happens to be the correct checksum for the corrupted files, therefore passing the files as false-negative valid files?
  3. What if the files were edited maliciously and so was the SFV file to look as if the files were authentic?

So to speak, in its pure form, SFV does neither add to integrity nor authentity of files, at least not as much as this article currently promises. --Abdull 20:13, 26 April 2007 (UTC)

  1. No user is probably ever going to rely on just a single hashcheck. In fact, most users don't even know what a hash is, and their way of checking a file's integrity is to open it in the program it's made for. And if you have already found out you have your data intact, who cares about the .sfv? Create a new one if you need it.
  2. I'm not saying it's completely impossible, but what are the odds of that actually happening, really?
  3. If you are to use .sfv as a safety check, you are not going to verify the data with the hash in the .sfv that ships with the data, but with the one you got from the "source" (either from a person who was the original owner of the data - or if thats you - from what you wrote down somewhere secure).
The article doesn't promise SFV to be the ultimate integrity & security verification, it merely points out the main use of SFV as a basic integrity and (if used wisely (see point 3), as a bonus) simple security check. Or if at the time of your writing, the page was radically different, you should have provided a diff for that version, or something. -- 82.131.68.159 07:06, 1 June 2007 (UTC)

[edit] Question

Are SFV's also used to combine files downloaded in segments into the 'original' file? —Preceding unsigned comment added by 66.105.208.12 (talk) 07:09, 24 November 2007 (UTC)

[edit] Mac / Unix shell script to check

if you want to check an sfv against the contents of that directory, this shell script will work. (not for the the faint at heart with the command prompt, requires proper line endings -- hence dos2unix at the beginning).


#!/bin/sh
dos2unix *.sfv
cat *.sfv |
{
  read line;
  while [ "$line" != "" ];
    do read line;
    file=`echo $line | cut '-d ' -f1`;
    crc=`echo $line | rev | cut '-d ' -f1 | rev | cut  -f1 `;
    crccheck=`crc32 $file`;
    if [[ "$crccheck" == "$crc" ]];
    then echo "$file                       Good.";
    else echo "$file                       Bad!! ($crccheck instead of expected $crc)"; exit;
    fi;
  done;
}
While I realize that this can be useful to people, Wikipedia is not the place to simply dump scripts on, and Wikipedia talk pages should be used for discussing improvements to the article. -- intgr [talk] 12:49, 15 November 2007 (UTC)

[edit] Lots of missing info

So is SFV simply a de facto file format or is there a standard algorithm, etc.? If so, who invented it, etc. Ham Pastrami 12:05, 2 December 2007 (UTC)