Slashdot Mirror
Reiser4 Filesystem Released
trixie_czech writes "It's finally arrived. Go to namesys for reasons to use reiser4 as a filesystem and benchmarks. Go here to download. Enjoy!" The Namesys homepage in its current stage reminds me of a cross between The Secret Guide to Computers and the GNU Manifesto -- which is to say, there is a lot to read here, not just a bullet-pointed feature list.
It was a day like any other and my 240GB RAID5 ReiserFS mp3 partition was just minding its own business... a split second power outage later and my precious data was vomited into tens of thousands of nightmarish numeric lost+found files. What I did manage to recover through painstaking use of mp3info, grep, prayer, etc. seemed fine, except for the insidious corrupted block of data that would invariably be within each and every one of my mp3 files. I nearly cried. At least I had an excuse to re-rip all of my CDs in Ogg format now.
The moral of the story: ext3 with data journaling (mount option data=journal), and a UPS are wonderful things. I can power cycle my box all day long with no ill effects (to my files anyway).
You better believe I am staying far far away from Reiser4!
So, show me a collision in SHA1. I dare you.
Need a Python, C++, Unix, Linux develop
I don't trust any hashing algorithm in which there are demonstrated collisions. You shouldn't either. Stop recommending anybody use MD5 when there's a perfectly good replacement available that practically everybody who has MD5 also has.
I wouldn't be surprised to discover that the fact that you can generate collisions in the algorithm means that its distribution for random input is far from flat, and it's probably a bad idea to use it for anything.
Need a Python, C++, Unix, Linux develop
I wouldn't recommend crc32 for large volumes of data. Mostly because if you have any errors, they'll likely be more than single bit errors, and for a large enough amount of data will swamp crc32's ability to detect them.
I don't trust a hash algorithm that has collisions for anything, not even verification. Part of this is because I have a strong bent towards viewing things from a cryptographic standpoint, but another reason is this... If the algorithm is sitting around, there for people to use, it will be abused because people will not be aware that it is broken for certain purposes. It's better to get rid of it altogether.
For example, MD5 is now completely unsuitable for use as a verification mechanism for downloads. Removal of the tool from distributions makes it harder for people to abuse it for this use, and more likely that they'll use SHA-1, which does not have any proven attacks yet.
Need a Python, C++, Unix, Linux develop
@Aardpig, your sig is racist & inflammatory... Slashdot: where racism against Indians is OK... are you purporting that slashdot and it's readers are racists? and no offense, whatever your race is, that is fine with me, afterall we are all sprung from the same stock, sharers in the same hopes, and partakers of the same nature, but, i do find your signature rather racist, and inflammatory... peace to you and everyone
@Aardpig,
i hope that your remarks are not racially motivated,
as your signature seems to indicate, however, MD5 is a bad choice of hash algorithm for the purpose that
you indicate.
hth