NASCAR.com - Gordon rallies to win third Daytona 500 - Feb 20, 2005
Gordon rallies to win third Daytona 500
Stewart dominates, but late fade sends him to seventh
February 20, 2005
08:18 PM EST (01:18 GMT)
DAYTONA BEACH, Fla. (AP) -- Jeff Gordon grabbed the lead from Dale Earnhardt Jr., then held off Kurt Busch and Earnhardt in extra laps to win his third Daytona 500 on Sunday.
One of the wildest finishes in the 47-year history of NASCAR's biggest race saw four lead changes in the last nine laps. Earnhardt, the defending champion, came from as far back as 30th to grab a late lead, only to watch four-time series champion Gordon pass him seconds before a caution flag waved with three laps to go.
The race went three laps beyond the scheduled 200-lap distance, with Gordon hanging on over two final laps of green-flag racing to beat Busch by two car-lengths.
"Oh, my goodness, what an amazing day," a jubilant Gordon said. "Three, baby!"
He is the fifth driver to win three or more Daytona 500s, joining Richard Petty (7), Cale Yarborough (4) and Bobby Allison and Dale Jarrett (3).

| | Michael Waltrip high-fives members of his crew after edging Dale Earnhardt Jr. to win the first race of the Gatorade Duel. Credit: CIA Stock Photo
NASCAR.com - NASCAR threatens to bench Johnson, Harvick - Feb 17, 2005 NASCAR threatens to bench Johnson, Harvick Multi-car wreck in second race sends top drivers to back By Marty Smith, NASCAR.COM February 17, 2005 08:57 PM EST (01:57 GMT)
DAYTONA BEACH, Fla. -- The year-long on-track feud between Jimmie Johnson and Kevin Harvick officially came to a head Thursday, and NASCAR made it clear that they've officially had enough.
No penalties were levied for the multicar accident that took out Johnson, Harvick, Mark Martin, Joe Nemechek and Rusty Wallace, and also involved Scott Riggs and Dave Blaney.
But the drivers, crew chiefs and team owners were summoned to the NASCAR transporter for a stern talking-to from president Mike Helton.
NASCAR spokesman Jim Hunter said that if Johnson and Harvick don't resolve their differences immediately, they could be spectators for an upcoming event.
"If they get into it again, there could be some severe penalties -- like missing a race," Hunter said. 
Jimmie Johnson (48) spins after contact with Kevin Harvick (29) during the second 150-miler on Thursday. Credit: AP
Trend Micro has a pretty good graphic showing the behavior of the latest MyDoom variant included in their description of the virus. 

Symantec and McAfee has released cleaning tools overnight for the latest fast spreading MyDoom variant. These cleaners also look to be designed to detect and remove the backdoor trojans that this virus installs on infected machines. However, depending on how long a machine is infected will determine how much damage is done and whether you will need to do a “wipe and redo”. Symantec’s Tool: http://securityresponse.symantec.com/avcenter/venc/data/w32.mydoom@mm.removal.tool.html McAfee’s Stinger Tool: http://vil.nai.com/vil/stinger/ 
Someone is paying attention, Trend Micro renamed their listing of the new MyDoom variant to match McAfee’s and it is now rated at Medium risk by them as well. WORM_MYDOOM.BB http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM%5FMYDOOM%2EBB
Listings for the new MyDoom variant are poping up on multiple vendors websites, with several of them already rating the virus at Medium to High risk. On top of it all the Virus Name Game is full force it seems.
Here is what I have seen so far:
W32/Mydoom.bb@MM (McAfee, Medium) http://vil.nai.com/vil/content/v_131856.htm
W32.Mydoom.AX@mm (Symantec, Level 3) http://www.sarc.com/avcenter/venc/data/w32.mydoom.ax@mm.html
Win32.Mydoom.AU (CA, High) http://www3.ca.com/securityadvisor/virusinfo/virus.aspx?id=41813
WORM_MYDOOM.M (Trend Micro, Low) http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM%5FMYDOOM%2EM
Hold on everyone, my virus sense is tingling...
All I can say is, its about time!!! USATODAY.com - DC Comics blazing a superhero trail back to big screen DC Comics blazing a superhero trail back to big screen By Scott Bowles, USA TODAY LOS ANGELES — For a decade, this has been a one-comic-book town. If you wanted to bring a superhero to the big screen, it was Marvel Comics or nothing. Based on Hellblazer: Keanu Reeves' character fights the powers of hell in Constantine, opening Friday. Warner Bros.
But now DC Comics is seeking a comeback after foundering with campy '90s Batman and '80s Superman sequels and last year's Catwoman flop.
This time, DC Comics is showcasing a hero with a lower profile. Based on the obscure comic book Hellblazer, which centers on a chain-smoking, cancer-ridden demon hunter, Constantine opens Friday armed with something the comic-book publisher hasn't seen in years: fan excitement.
The Internet is abuzz about DC's upcoming fare:
•Batman Begins, starring Christian Bale, opens June 17.
•Superman Returns, with X-Men director Bryan Singer at the helm, is due in June 2006.
•The Flash is expected to sprint to theaters next year with Blade's David Goyer writing and directing.
• Joss Whedon (Buffy the Vampire Slayer) is in talks to do Wonder Woman.
•The Bourne Supremacy's Paul Greengrass will direct the crime story The Watchmen.
•Matrix creators Andy and Larry Wachowski are producing V for Vendetta, due Nov. 5, about a crime fighter.
This is a little bit clearer on what is and is not vulnerable than the last doc I looked at. Go to the main link for information on removing this vulnerability. UPX parsing engine heap overflow vulnerability and Symantec Client Security UPX parsing engine heap overflow vulnerability and Symantec Client Security Situation: You have heard about the UPX parsing engine heap overflow vulnerability. You want to know whether your Symantec Client Security product is vulnerable and how to mitigate the vulnerability if it is.
Solution: Affected versions For a complete list of all Symantec products affected by the vulnerability, read the official Symantec statement on the Symantec Security Response Web site. The latest builds of all of the Symantec Client Security products are unaffected by the vulnerability.
Symantec Client Security 2.0 and Symantec AntiVirus Corporate Edition 9.0 Symantec Client Security 2.0 and Symantec AntiVirus Corporate Edition 9.0 are not affected by the vulnerability.
It was previously reported that the original shipping build of Symantec Client Security was vulnerable. While the shipping build did contain the vulnerable Dec2EXE.dll engine file and later builds did not, the vulnerable file is not called by Symantec AntiVirus, and is never loaded. Because the Dec2EXE.dll file is never loaded into memory, the build is not vulnerable.
Symantec Client Security 1.0 and Symantec AntiVirus Corporate Edition 8.0 The vulnerability of Symantec Client Security 1.0 and 1.1 depends on the version of Symantec AntiVirus Corporate Edition included. The vulnerability of each of the versions of Symantec AntiVirus Corporate Edition is as follows:
Build | Comment | Vulnerable? | 8.1.0.825a | Initial shipping build | No | 8.1.1.314a | MR1 | Yes | 8.1.1.319 | MR2 | Yes | 8.1.1.323 | MR3 | Yes | 8.1.1.329 | MR4 | Yes | 8.1.1.336 | MR5 | Yes | 8.1.1.366 | MR6 | No |
Build | Comment | Vulnerable? | 8.0.0.9374 | Initial shipping build | No | 8.0.0.9378 | N/A | No | 8.0.1.425 | MR1 | No | 8.0.1.429c | MR2 | No | 8.0.1.434 | MR3 | Yes | 8.0.1.437 | N/A | Yes | 8.0.1.446 | MR4 | Yes | 8.0.1.457 | MR5 | Yes | 8.0.1.460 | MR6 | Yes | 8.0.1.464 | MR7 | Yes | 8.0.1.471 | MR8 | Yes | 8.0.1.501 | MR9 | No |
Mitigation There are three ways to remove the UPX vulnerability in Symantec Client Security or Symantec AntiVirus: - Upgrade to a build that is not affected by the vulnerability
- Disable the vulnerable decomposer engine by using the nodec2exe.exe tool
- Disable the vulnerable decomposer engine manually by editing a configuration file
That lasted a long time
Sci Fi Wire -- The News Service of the Sci Fi Channel Straczynski Ends Trek Campaign
A day after calling for a letter-writing campaign by fans who wanted to see his version of Star Trek produced, Babylon 5 creator J. Michael Straczynski posted a follow-up message to the same newsgroup retracting his statement. "[B]elay everything I just said," Straczynski wrote. "In the 24 hours between the time I composed the prior note, and sent it, and it made its way through the moderation software, two things happened."
The two things that changed Straczynski's mind were a tip from a trusted source at Paramount, which owns the rights to the Star Trek franchise, that the studio is "giving the Trek TV world a rest" for a year or two, and an offer to run a series premiering in the fall of 2006, which Straczynski has accepted. In Straczynski's words, the Trek campaign is now "kind of moot."
The writer/producer apologized to fans and assured them that he hasn't abandoned the project completely. "We can reconvene a year or two down the road to see where this takes us," he said. "But in the interim ... my apologies for waking everybody up in the middle of the night."
More Posts Next page »
|
|