dont have FLAC installed on this system, but "verify" should be used to check that the FLAC fiiles are error free

guess I'm not understanding...FLAC is like SHN. if the fingerprint/md5 verifies then it is effectively the same as the master original the taper/seeder made. thats the whole point of the fingerprint/md5, to verify the files are error free and that are the same as the original seed

Quote from: Brian Skalinder on January 14, 2004, 06:09:26 PM
How does one validate the FLAC files against the fingerprint signatures?

Nice stab.  This is the question I was trying to ask.  The only way I know is to drop the FLACs in the frontend, create a fingerprint file and compare that manually to the fingerprint file provided(hopefully) by the taper.  If there isn't a program to do that, maybe I could create one.

Quote from: blu666z on January 14, 2004, 06:34:29 PM

Quote from: luvean on January 14, 2004, 06:05:52 PM
guess I'm not understanding...FLAC is like SHN. if the fingerprint/md5 verifies then it is effectively the same as the master original the taper/seeder made. thats the whole point of the fingerprint/md5, to verify the files are error free and that are the same as the original seed

That doesn't prove they are the originals.  ie.  I get a show in from you in FLAC.  I decode track 1, fuck around with it in SoundForge and then encode it back to FLAC.  Now if I run the test on it, it will test fine but it is not the original file you sent me.  Does that make sense?  To relate that to SHNs, just because the files match the MD5 they were sent with doesn't mean that MD5 is the original seeded by the taper.

-Kevin

if you alter a file in any way, then the fingerprint/md5 will NOT match the file you downloaded.
as for: "To relate that to SHNs, just because the files match the MD5 they were sent with doesn't mean that MD5 is the original seeded by the taper."
well, I guess thats where the fingerprint/md5 that is hosted on etree/archive, etc comes into play...you can match the the fingerprint/md5 with what is listed on those sites to see if it matches the "original"

Looks like I may have to write a little utility to do that.

-Kevin

Quote from: Joe w. on January 14, 2004, 10:47:01 PM
you have to do a side by side comparison of the fingerprint's numerical output.

Just go to the db (if it is in the db) and find the original fingerprint......and compare it to yours.

Right, but this still doesn't address the central question:

How does one validate the FLAC files against the fingerprint signatures   (not against their internal checksum, not validating one fingerprint file against another)?

"HOW does one verify FLAC files against the fingerprint file signatures (NOT the internal FLAC file checksums)?"

I guess I'm missing something obvious...arent those(signatures/checksums) the same thing, just under a different name? when you verify the file it compares it to the fingerprint signatures/checksum sent with the files.
to verify that this is the same fileset that the taper/seeder originally seeded you would just compare the same as with shn/md5 files, either visually compare the checksums or run the original md5 against the fileset you have. either way produces the same result