SHA-1 Broken
Nanolith writes "From Bruce Schneier's weblog: 'SHA-1 has been broken. Not a reduced-round version. Not a simplified version. The real thing. The research team of Xiaoyun Wang, Yiqun Lisa Yin, and Hongbo Yu (mostly from Shandong University in China) have been quietly circulating a paper announcing their results...'" Note, though, that Schneier also writes "The paper isn't generally available yet. At this point I can't tell if the attack is real, but the paper looks good and this is a reputable research team."
BTW:
Disabled US vets 10 yrs after Viet Nam: 10%
12 yrs after Gulf War: 89%
Stop uranium inhalation poisoning!
What exactly is your source on this? According to an anti-military news source quoting the DoVA:
Of the 504,047 eligible for VA benefits, 149,094 (29%) are now considered disabled by the VA eleven years since the start of the Gulf War; and...
29% is a big number, but 29% != 89% last time I checked. Also, there are many other explanations other than uranium dust, like chemical weapons in theatre. But I don't think facts probably matter very much to you.
Wild yes, but the source is here and it's apparently not a lie.
Having said that, it is very hard to explain how the contamination of Basrah occured, because almost all the time during and after the 1991 battles when uranium was being released, the prevailing winds would have been blowing them away from the city. Some people have suggested some kind of food-chain contamination, relating to either goats or birds.
There is a collection of peer-reviewed medical research on the subject here.Ignore me. Way past bedtime.
Someone had to do it.
Presumably it's the same motivation they have for trying to ruin Slashdot.
(being pedantic) Actually, you mean UTF-16. Unicode is just a set of code points; it doesn't actually specify how many bits are used to encode them.
No comment.