Since this was dated September 17, make that four days ago, not two.
Check the date on the xsec.org page referred to, daxctle2.c. milw0rm 2358 was a re-publication of this, also posted up on 09/13/2006. Republication happened at other exploit advisory sites as well, such as the SecuriTeam(TM) site, where, for some strange reason, the exploit was published twice, redundantly.
The formal vulnerability advisories SA21910 and FrSIRT/ADV-2006-3593, from Secunia and FrSIRT respectively, posted on 09/14/2006, confirmed and extended this, since both groups developed internal versions of daxctle2.c which were reliably effective in compromising fully patched instances of IE6.0 on WXPSP2.
However, both these advisories made it clear that the root cause flaw was in the ActiveX component that was so successfully and famously attacked by HD Moore in July.
Friday's MS advisory, Microsoft Security Advisory (925444), both clarified matters and proposed two workarounds that might be of more use than shutting down ActiveX or fervent prayer, namely:
Disable just the DirectAnimation Path ActiveX Control in the Registry, or
Modify the ACL of the actual file Daxctle.ocx to be more restrictive.
Assuming, of course, that one considers it wise to use MSIE at all, given a choice. But PHBs from coast to coast have left many millions of cube inmates with exactly that: no choice.
IANAL. But I am a CISSP on a forensics track, and just got finished with a class on forensics and the law.
After noting that I wouldn't cry for more than 10 or 15 milliseconds if the earth opened up and swallowed the entire RIAA right down to the last crooked exec and bloodsucking lawyer.. it is fairly normal for the court to impose sanctions from the bench in cases where deliberate destruction of evidence has been shown to the judge's satisfaction.
The cases I read summaries of, where deliberate evidence tampering was demonstrated to the satifsfaction of the court, didn't go the bench warrnt route. They went the bench sanctions route. And what happened to the defendant (not the plaintiff, BTW, read the article) isn't at all unusual in the light of what I learned. Though RIAA cases were not specifically studied during the course of this work.
The testimony of the defense forensics expert probably clinched matters. There was no real way he was going to lie under oath. You get a name for that and you're done in forensics, period, end of sentence.
Here are the name of the 19 Democrats who voted "Yes" on the Alito debate cloture Roll Call vote. These were the Democrats who voted in favor of ending the Alito confirmation debate. The failure to filibuster guaranteed Samual Alito's confirmation. Thus, these 19 are as responsible as any member of the Bush Administration for what Alito does, and what he fails to do, during the rest of his life term on the Supreme Court bench.
The date was January 30, 2006. The day it became clear to anyone with eyes to see and a mind open to comprehension that the United States is now, at best, a one-party state.
Akaka, Hawaii
Baucus, Mont.
Bingaman, N.M.
Byrd, W.Va.
Cantwell, Wash.
Carper, Del.
Conrad, N.D.
Dorgan, N.D.
Inouye, Hawaii
Johnson, S.D.
Kohl, Wis.
Landrieu, La.
Lieberman, Conn.
Lincoln, Ark.
Nelson, Fla.
Nelson, Neb.
Pryor, Ark.
Rockefeller, W.Va.
Salazar, Colo.
Maria Cantwell's name is in boldface because I made the mistake of voting for that bitch, half a dozen years ago.
Ye Gods, even wretched Hillary Clinton, who stands for nothing beyond her own personal aggrandizement, voted "No".
I did my first install on a Sun box in 1988. Not Solaris. SunOS. Piece of cake. But it took FOREVER to spool the OS distro off that QUIC-24 tape drive.
And of course, BSD is alive. Furthermore, as I hinted earlier, it's dead easy to install on SPARCs.
It really is too bad that Martin Krafft fails to explain how to install the SPARC port of Debian. The last time I tried this, I had dug through the relevant portion of his book, and had it open next to me.
His description went wide of the mark quite quickly, and became totally useless shortly thereafter.
The install failed, of course. The OS went in, but the system went into spin-lock upon bootup attempt. That was about the third staight install failure for Debian 3.0r1 SPARC (each one burning 10 to 15 hours of my time), and it was the one which finally snapped my patience.
The SPARC32 gear of a dozen years ago was put together quite well, even if it isn't nearly as speedy as recent Intel kit. Even after the processors have been changed out for faster aftermarket Ross Hypersparcs.
Too bad that no Linux distro has supported it for half a decade. Yeah, catcalls, mudgobs, and rotting veggies also go out to RedRat, SuSE, and Mandrake.
And it's really too bad that Debian wastes our bloody time by pretending to support SPARC hardware.
I'm waiting for the first "BSD is dead" troll to show up. I can really use the bellylaugh. Because installing OpenBSD/SPARC32 on one of those old systems is a complete slam-dunk. Stock processors or Hypersparcs, single-proc or dual.
The way the current H5N1 vaccine candidate is produced works around the "kills chicken eggs" problem.
BTW, this is not an issue with other "ordinary" influenzas. The H5N1 issue stems from its quite extraordinary lethality.
H5N1 vaccine starts with a "designer virus" containing enough elements of the H5N1 genome to provoke resistance when they are expressed as surface glycoproteins. But the "designer virus" has a much lower lethality and the chicken eggs mature to produce usable virus yields.
It should be mentioned in passing that the current H5N1 candidate is seriously flawed for a number of reasons. The most important of these is that it was designed using the strain prevalent in Vietnam in late 2004. The strain spreading like crazy across Eastern Europe right now, and moving into (oh, joy) the Middle East has a number of specific genetic and antigenic differences from the Vietnamese one. It is quite possible for the current candidate to fail quite badly to induce immunity to this new strain, should it be the one to finally go airborne H2H.
If you want more reading matter than you can handle on this subject, and reputable to boot, may I suggest two sites you folks should have been reading on a daily basis for the last six months:
The author of the Recombinomics site is a virologist who is one of the world's foremost experts on genetic recombination. I draw your attention to something that has gotten short shrift on Slashdot, which omission may shorten the lives of a few readers here - recombination and/or reassortment, NOT mutation, is how H5N1 is likely to achieve airborne human-human infectiousness.
The Flu Wiki has an editorial board which is very, very physician and virologist heavy. There is simply NFW that it will wander into the Wilderness Of Disrepute that Wikipedia now stands lost in.
Slashdot Mirror
Check the date on the xsec.org page referred to, daxctle2.c. milw0rm 2358 was a re-publication of this, also posted up on 09/13/2006. Republication happened at other exploit advisory sites as well, such as the SecuriTeam(TM) site, where, for some strange reason, the exploit was published twice, redundantly.
The formal vulnerability advisories SA21910 and FrSIRT/ADV-2006-3593, from Secunia and FrSIRT respectively, posted on 09/14/2006, confirmed and extended this, since both groups developed internal versions of daxctle2.c which were reliably effective in compromising fully patched instances of IE6.0 on WXPSP2.
However, both these advisories made it clear that the root cause flaw was in the ActiveX component that was so successfully and famously attacked by HD Moore in July.
Friday's MS advisory, Microsoft Security Advisory (925444), both clarified matters and proposed two workarounds that might be of more use than shutting down ActiveX or fervent prayer, namely:
- Disable just the DirectAnimation Path ActiveX Control in the Registry, or
- Modify the ACL of the actual file Daxctle.ocx to be more restrictive.
Assuming, of course, that one considers it wise to use MSIE at all, given a choice. But PHBs from coast to coast have left many millions of cube inmates with exactly that: no choice.IANAL. But I am a CISSP on a forensics track, and just got finished with a class on forensics and the law.
.. it is fairly normal for the court to impose sanctions from the bench in cases where deliberate destruction of evidence has been shown to the judge's satisfaction.
After noting that I wouldn't cry for more than 10 or 15 milliseconds if the earth opened up and swallowed the entire RIAA right down to the last crooked exec and bloodsucking lawyer
The cases I read summaries of, where deliberate evidence tampering was demonstrated to the satifsfaction of the court, didn't go the bench warrnt route. They went the bench sanctions route. And what happened to the defendant (not the plaintiff, BTW, read the article) isn't at all unusual in the light of what I learned. Though RIAA cases were not specifically studied during the course of this work.
The testimony of the defense forensics expert probably clinched matters. There was no real way he was going to lie under oath. You get a name for that and you're done in forensics, period, end of sentence.
The date was January 30, 2006. The day it became clear to anyone with eyes to see and a mind open to comprehension that the United States is now, at best, a one-party state.
Maria Cantwell's name is in boldface because I made the mistake of voting for that bitch, half a dozen years ago.
Ye Gods, even wretched Hillary Clinton, who stands for nothing beyond her own personal aggrandizement, voted "No".
google: stolen customer data
:D
ROTFLMAO!!!
How many of us want to work for the next Card Systems Solutions? All in favor, raise your hands.
Ah. Like a forest after the clearcutters have come and gone. Thought so.
Yeah, it's the kernel that bites. Getting the distro on is pretty easy. Booting, on the other hand .... I draw a merciful veil.
I did my first install on a Sun box in 1988. Not Solaris. SunOS. Piece of cake. But it took FOREVER to spool the OS distro off that QUIC-24 tape drive.
And of course, BSD is alive. Furthermore, as I hinted earlier, it's dead easy to install on SPARCs.
It really is too bad that Martin Krafft fails to explain how to install the SPARC port of Debian. The last time I tried this, I had dug through the relevant portion of his book, and had it open next to me.
His description went wide of the mark quite quickly, and became totally useless shortly thereafter.
The install failed, of course. The OS went in, but the system went into spin-lock upon bootup attempt. That was about the third staight install failure for Debian 3.0r1 SPARC (each one burning 10 to 15 hours of my time), and it was the one which finally snapped my patience.
The SPARC32 gear of a dozen years ago was put together quite well, even if it isn't nearly as speedy as recent Intel kit. Even after the processors have been changed out for faster aftermarket Ross Hypersparcs.
Too bad that no Linux distro has supported it for half a decade. Yeah, catcalls, mudgobs, and rotting veggies also go out to RedRat, SuSE, and Mandrake.
And it's really too bad that Debian wastes our bloody time by pretending to support SPARC hardware.
I'm waiting for the first "BSD is dead" troll to show up. I can really use the bellylaugh. Because installing OpenBSD/SPARC32 on one of those old systems is a complete slam-dunk. Stock processors or Hypersparcs, single-proc or dual.
The way the current H5N1 vaccine candidate is produced works around the "kills chicken eggs" problem.
BTW, this is not an issue with other "ordinary" influenzas. The H5N1 issue stems from its quite extraordinary lethality.
H5N1 vaccine starts with a "designer virus" containing enough elements of the H5N1 genome to provoke resistance when they are expressed as surface glycoproteins. But the "designer virus" has a much lower lethality and the chicken eggs mature to produce usable virus yields.
This trick was used a few years ago by NAIAD to produce a vaccine candidate for Ebola. Here is a short article on the design of the Ebola vaccine candidate, and the announcement of the beginning of human trials.
It should be mentioned in passing that the current H5N1 candidate is seriously flawed for a number of reasons. The most important of these is that it was designed using the strain prevalent in Vietnam in late 2004. The strain spreading like crazy across Eastern Europe right now, and moving into (oh, joy) the Middle East has a number of specific genetic and antigenic differences from the Vietnamese one. It is quite possible for the current candidate to fail quite badly to induce immunity to this new strain, should it be the one to finally go airborne H2H.
If you want more reading matter than you can handle on this subject, and reputable to boot, may I suggest two sites you folks should have been reading on a daily basis for the last six months:
Recombinomics
The Flu Wiki
The author of the Recombinomics site is a virologist who is one of the world's foremost experts on genetic recombination. I draw your attention to something that has gotten short shrift on Slashdot, which omission may shorten the lives of a few readers here - recombination and/or reassortment, NOT mutation, is how H5N1 is likely to achieve airborne human-human infectiousness.
The Flu Wiki has an editorial board which is very, very physician and virologist heavy. There is simply NFW that it will wander into the Wilderness Of Disrepute that Wikipedia now stands lost in.
Do your homework if you want to live. Verb sap.