
If you got my most recent newsletter, you saw our survey regarding virtual conferences. Times have changed, folks... no training budgets, no travel budgets and likely absolutely no conference budgets in 2009.
The upcoming BitSpitters will be shorter (maybe I could cheat and do 'part 1' and 'part 2' videos) and hit some of the more humorous topics, such as:
If you have ideas for future BitSpitters episodes, send them to me at lchappell@packet-level.com. Watch for the announcement regarding Binary Balloons as well... he he he...
Time to put my headset on and spew!
Laura
www.wiresharkU.com
Things were little too hot in many areas of the country as American Airlines grounded some 3,000 flights last week. I was lucky. I was on code share flight with Alaska Airline. Of course, my Alaska Airline flight didn't take off on time (out of the last 10 round-trip flights Alaska Airlines, my flights have been delayed 8 times - they are a pretty mellow bunch). But hey, I was just happy that the plane took off within a couple of hours of the scheduled departure time and I didn't have to put up with the nasty stench of burning wires on the flight.
On Friday evening, I received an e-mail from Dan Garton, American Airlines' Executive Vice President of Marketing. Dan referred to me as "one of our most valued customers" in his apologetic e-mail addressing the grounding of the DC 80 planes. Considering that I have now almost reached my 3,000,000 mile mark with American Airlines, it's a miracle that I didn't have an AA flight schedule for last week. It sure seemed strange to me that the e-mail apology was sent from American Airlines VP of marketing. Don't you think it would been better to send the e-mail from the CEO, Gerard Arpey? Hmmm...
"The work being done now centers on a need to change the way in which American complied with the Airworthiness Directive (AD) regarding such items as the spacing of the ties on the wiring bundles and the direction of the retention clips and lacing cords. We are highly confident that this is not a safety of flight issue because the wire bundle is secure. It is a matter of how the work was done, not whether aircraft were protected from the threat of wire exposure and chafing that could cause fire."
Perhaps this whole world of a wired technology is passé. Maybe it's time to take a look over at MIT and check out the "WiTricity" project (http://web.mit.edu/newsoffice/2007/wireless-0607.html). These folks have it right. Wireless electricity! Take a bit further and imagine having roaming wireless electricity. As you cruise through the airport, your laptop would connect to various wireless electricity taps in charge itself to 100%. Considering the number of times I've plugged my computer into a power strip and then forgot to turn on th power strip - this could be very handy technology! Another plus would be the removal of the dreaded "power cord to the podium" that I've tripped over numerous times... the comedic fall that I've taken so many times would be missing from my presentations, but it's the price we pay for keeping up with technology.
So, back to the Redmond trip. On June 9, the week of TechEd, I'll be able to explain why I've been spending time in Redmond. I'll be arriving at the TechEd conference on a red-eye flight from Redmond that gets me into Orlando around 6:30 a.m. on June 10th. Mark Penaroza, the Security Track Manager, was nice enough to book me in afternoon sessions that Tuesday. As long as American Airlines doesn't ground their fleet that week, I should get there in plenty of time to present. (Crossing my fingers and wires!)
Now back to working on the Wireshark University certification test... we're almost there!
Laura
and many more... all there for one reason - to support, enhance and share knowledge on Wireshark features, future and related technologies and products.
Wireshark University Instructors and ExecuTrain GroupEvery attendee got the latest version of the Laura's Lab Kit (v9) in their bags - if you didn't attend, download the ISO image (3.3GB) from www.novell.com/connectionmagazine/laurachappell.html when you have a lot of spare time.
Campus Center Hang-Out
The Campus Center was definitely the place to collaborate. At times you'd see a table of the impressive Wireshark core developers dotted with attendees who were soaking up the brilliance emitted from the creative minds surrounding them. Conversations would wander from war stories of beleaguered networks overloaded with BitTorrent traffic to newer functions added to Wireshark over the past several revs to "I have a dumber network user than you do" competitions.
Here's the scoop... the HackTool or Hacker Tools designation does indicate that there is a potentially unwanted program on your computer or on connected media. You do want to know about that, don't you? The Laura's Lab Kit always contains some programs that could potentially be nasty if used in the wroF-Secure's Description of "HackerTool"
Hacker Tool (generic description)
Hacker Tool is usually a standalone file. In many cases such tools are used by hackers to perform certain actions on a compromised computer, for example to crack passwords or to scan for vulnerable computers. It should be noted that such tools are sometimes used by system administrators.
Our corporate customers prefer hacker tools to be detected by F-Secure Anti-Virus. If a system administrator still wants to use a hacker tool, he can exclude the tool's file from scanning. For ordinary users running such tools should be prohibited.
Yup - the week will be busy and filled with exciting new projects and opportunities. Before I head into my lab and immerse myself in packets (especially those 'ICMP Communication Administratively Prohibited' packets), however, I will catch a few moments in the sun to ward off a florescent-light pallor...
Laura