Hát a kérdés adott!!! Annyit tudok, hogy audio file-al van kapcsolatban.
Oldal 1 / 1
Mire jó az .sfv file?
#2
Elküldve: 2002. 12. 02. 00:02
idézet:
Ezt írta Geli:
Hát a kérdés adott!!! Annyit tudok, hogy audio file-al van kapcsolatban.[/quote]Amit én ismerek az a wincmd-ben is benne van, egy alap crc ellenőrzésen alapúló fájlsértetlenség ellemőrzési módszerhez kell (ezt jól megmondtam)
idézet:
; Generated by WIN-SFV32 v1.0
; (Compatible: Windows Commander 5.0)
[/quote]
#3
Elküldve: 2002. 12. 02. 00:18
idézet:
Ezt írta Sipi-:
[QB][/QB][/quote]
És ugye nem sok köze van az audio filehoz
Én úgy tudom, hogy mikor darabolsz file-t a windows(total) commanderrel, akkor csinál ilyen filet, és ebbe teszi bele az összeillesztéssel kapcsolatos dolgokat. Legalábbis, ami nem a .crc-ben van, az itt![]()
; Generated by WIN-SFV32 v1.0
; (Compatible: Total Commander 5.50)
x.001 E02CC0C0
x.002 29348740
x.003 A4F30974
x.004 B819F341
Pl eszerint az van benne, hogy hol kell folytatni az összeillesztést.
#4
Elküldve: 2002. 12. 02. 00:22
idézet:
Ezt írta Geli:
Hát a kérdés adott!!! Annyit tudok, hogy audio file-al van kapcsolatban.[/quote]
Amit tudsz, az látod nem igaz, mert bármilyen filehoz rendelhető.
Ha tudod mi az a CRC akkor a magyarázat egyszerű: ez majdnem ugyanaz, csak nem úgy hívják.
Ha nem tudod mi az a CRC akkor kicsit nehezebb a helyzet: az SFV file egy (vagy több) ellenőrzőösszeget tartalmaz, amiből ellenőrizhető egy (vagy több) file sértetlensége.
A [url="http://"http://www.geocities.com/SiliconValley/Mouse/4668/"]QuickSFV[/url] szerintem a legjobb/leggyorsabb program az ellenőrzésre, de a wincomm beépített sfv-ellenőrzője is megteszi ha nincs más.
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
#5
Elküldve: 2004. 05. 23. 09:51
és sfv vagy az md5 a jobb?
sfv mintha kissebb összegel dolgozna:
md5:
sfv mintha kissebb összegel dolgozna:
Idézet
01_100_folk_celsius_-_paff_a_buvos_sarkany-eoh.mp3 A5DE920F
md5:
Idézet
C7B82843E544DB3289BB16DD9B018598 01_100_folk_celsius_-_paff_a_buvos_sarkany-eoh.mp3
#6
Elküldve: 2004. 05. 23. 11:43
Idézet: charlie - Dátum: 2004. máj. 23, vasárnap - 10:51
és sfv vagy az md5 a jobb?
sfv mintha kissebb összegel dolgozna:
md5:
sfv mintha kissebb összegel dolgozna:
md5:
Idézet
I'm not sure if the probability for reaching a false positive file identification is really going to tell you much.. Even for crc-32 (sfv), the probability of failure is very, very small. For md5 it is obviously much, much smaller.
Neither algorithms are perfect - the simple fact of the matter is that there are only 2^32 crc-32 codes, and that means it can only accurately (uniquely) hash 2^32 different files. MD5 can accurately assign unique hashes to 2^128 files. Both of these statements are assuming these algorithms work ideally, which they do not (SHA-1 is now considered more secure than md5). Obviously your chances are substantially better with MD5 - but your success with either will be pretty good.
Depending on your use, you may eventually encounter two files with the same crc-32 code - it is very unlikely that you will do so with MD5. In fact, many websites use MD5 codes as unique identifiers for images/documents - if they were come across two files with the same md5, this system would fail, but it seems to hold up well.
One of the saving graces of algorithms like these, when used for file verification, is that some files have specific characteristics that define a 'valid' file, in addition to its md5/crc hash. So, while your chances of changing a byte and having a file result in the same md5 are very, very low, the chances of you being able to change a byte of a zip file, and have it both result in the same md5, and still be a valid zip (or rar, or exe) file are astronomically low. Unfortunately, most files do not have validity checks like this (mp3, mpg, jpg, etc - do not).
From a security standpoint, crc-32 isn't really considered, and thus I don't see much research information on it, but you won't have too much trouble digging up research on MD5..
Neither algorithms are perfect - the simple fact of the matter is that there are only 2^32 crc-32 codes, and that means it can only accurately (uniquely) hash 2^32 different files. MD5 can accurately assign unique hashes to 2^128 files. Both of these statements are assuming these algorithms work ideally, which they do not (SHA-1 is now considered more secure than md5). Obviously your chances are substantially better with MD5 - but your success with either will be pretty good.
Depending on your use, you may eventually encounter two files with the same crc-32 code - it is very unlikely that you will do so with MD5. In fact, many websites use MD5 codes as unique identifiers for images/documents - if they were come across two files with the same md5, this system would fail, but it seems to hold up well.
One of the saving graces of algorithms like these, when used for file verification, is that some files have specific characteristics that define a 'valid' file, in addition to its md5/crc hash. So, while your chances of changing a byte and having a file result in the same md5 are very, very low, the chances of you being able to change a byte of a zip file, and have it both result in the same md5, and still be a valid zip (or rar, or exe) file are astronomically low. Unfortunately, most files do not have validity checks like this (mp3, mpg, jpg, etc - do not).
From a security standpoint, crc-32 isn't really considered, and thus I don't see much research information on it, but you won't have too much trouble digging up research on MD5..
Téma megosztása:
Oldal 1 / 1