• On MP3.com: Free music videos

(continued from previous page)


"Blue Hat" summit meant to reveal ways of the other side

(continued from previous page)

adding that he doesn't plan to change his practice of giving companies 30 days before going public with issues. "I still have no desire to play e-mail tag with the (security response team) for a year for every bug that I find."

But Moore did gain a better understanding of why it takes Microsoft so long to create patches and said his impression of the people who create the products have changed. "I still may not agree with their security policies and how they handle bug reports, but at least I know they actually believe what they are saying," he said.

"Things are different when a group of programmers watches their actual code exploited. It kind of hits people in the gut."
--Matt Thomlinson
Director of security
engineering, Microsoft

Others agreed. "They are taking this subject seriously. It was really cool to see," said Kaminsky, a security researcher who does work for telecommunications company Avaya. "At some point, there was a shift at Microsoft."

That shift began in earnest with a well-publicized memo written by Gates on the concept of "trustworthy computing" in 2002. Security had long been a concern at Microsoft, but the issue became imperative after several high-profile attacks exposed the degree of its vulnerabilities.

"The security faults we are seeing could end up bringing an end to the era of personal computing," Kaminsky said. "The ability to customize our computers is under attack from those who are customizing it against our will."

It was this kind of impassioned rhetoric that won respect even among some of the more wary Microsoft participants.

Noel Anderson, a wireless networking engineer on Microsoft's Windows team, became suspicious as soon as he walked into the hacking demo--and saw the giant wireless antenna at the front of the auditorium.

Anderson decided that he should leave his laptop turned off, an instinct that saved him the embarrassment of falling into the hackers' trap, even though the hackers focused on a demo laptop. But under different circumstances, he thought to himself, "I might have even fallen for that."

As a result, Anderson and his team walked away with some concrete ideas on how to make sure future versions of Windows are more resilient to wireless attacks. He also left the room with a new respect for the hackers behind the demonstration.

"It's not just a bunch of disaffected teenagers sitting in their mom's basement," he said. "These are professionals that are thinking about these issues."

The hackers, for their part, seemed equally impressed with the technical knowledge of the senior executives they encountered.

At one point, researcher Matt Conover was talking about a fairly obscure type of problem called a "heap overflow." When he asked the crowd, made up mostly of vice presidents, whether they knew about this type of issue, 18 of 20 hands went up.

"I doubt that there is another large company on this planet that has that level of technical competency in management roles," Moore said.

Yet regardless of the mutual admiration, some tense moments were inevitable during the confrontation.

Microsoft developers, for instance, were visibly uncomfortable when Moore demonstrated Metasploit--a tool that system administrators can use to test the reliability of their systems to intrusion. But Metasploit also includes a fair number of exploits, as well as tools that can be used to develop new types of attacks.

"You had these developers saying, 'Why are you giving the world these tools that make it so easy to do exploitation?'" Kaminsky said. They calmed down, he said, once the researchers were able to state their case.

"We do regression testing in the real world of software development," Kaminsky said. "If we say, 'This thing isn't going to break,' then we need to test that. What these tools give is the ability to do this kind of testing, to be able to say not just, 'We did the best we could,' but 'We tried stuff and nothing worked.'"

Nevertheless, he understands why not all Microsoft developers were satisfied with the explanation.

"I'm also sure Ford wasn't too happy with (Ralph) Nader's reports in the late '60s," he said. "What do you mean you are telling people our cars can blow up?"

"The ability to customize our computers is under attack from those who are customizing it against our will."
--Dan Kaminsky
Security researcher

By the end of the two days, those on both sides felt they had just scratched the surface and were more than willing to meet again.

And executives such as Toulouse and Anderson said they came to a better understanding of what makes hackers tick.

"We have conversations where we say an attacker might do this or an attacker might do that. Now there is a face to some of those guys," Anderson said. "They were just as much geeks as we were."

The next time a Blue Hat event is held, as promised by Microsoft, Kaminsky said he would jump at the chance to return--assuming Microsoft lets him back.

"I'll be there next time, no matter what," he said. "I have some really interesting and devious plans coming up." End box

Previous page
Page 1 | 2
advertisement