Operations

11/25/2016
08:00 AM
John Klossner
John Klossner
Cartoon Contest
80%
20%

Name That Toon: Naughty or Nice

Submit your caption in the comments, and our panel of experts will reward the winner with a $25 Amazon gift card. If you don't want to enter a caption, help us pick a winner by voting on the submissions. Click thumbs up for those you find funny. As always, editorial comments are encouraged and welcomed.

Click here for contest rules. For advice on how to beat the competition, check out How To Win A Cartoon Caption Contest. The contest closes Jan 2.

John Klossner has been drawing technology cartoons for more than 15 years. His work regularly appears in Computerworld and Federal Computer Week. His illustrations and cartoons have also been published in The New Yorker, Barron's, and The Wall Street Journal. Web site: ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Page 1 / 11   >   >>
EnzoP200
50%
50%
EnzoP200,
User Rank: Apprentice
1/16/2017 | 11:43:33 AM
Cartoon Caption
There's an intruder on our network. Uses the name [email protected] Klau5.
XanderC027
0%
100%
XanderC027,
User Rank: Apprentice
1/10/2017 | 12:26:44 PM
"The new guy..."
"The new guy calls me 'Blitzen' and just sits there watching reindeer porn all day..."
SeanP20101
100%
0%
SeanP20101,
User Rank: Apprentice
1/9/2017 | 6:59:57 PM
Malware Christmas!
Have you met the new SOC Engineer.  Driving me nuts.  He keeps saying, "Whoa Oh Ho, Maaaaaalware Missed Us.  Malware Missed Us, everybody!"
Bill in MD
100%
0%
Bill in MD,
User Rank: Apprentice
1/6/2017 | 10:59:48 AM
Caption
I don't think Bob takes his Red Team job seriously.
reggicat
100%
0%
reggicat,
User Rank: Apprentice
1/6/2017 | 10:20:16 AM
Naughty or Nice
His stats are completely unacceptable. He keeps verifying everything twice.
LK2012
50%
50%
LK2012,
User Rank: Apprentice
1/6/2017 | 10:03:46 AM
Elf Monitoring
With this new insider threat tool I can keep tabs on what the elves are doing in the off-season!!
Joe Stanganelli
0%
100%
Joe Stanganelli,
User Rank: Ninja
1/5/2017 | 6:23:47 PM
lu
"No, I think he's just a UNIX programmer."
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
1/5/2017 | 6:22:11 PM
bt
"He's busy adding nodes beneath the tree."
KerryL293
50%
50%
KerryL293,
User Rank: Apprentice
1/5/2017 | 3:01:55 PM
Caption
He says he'll work 364 nights a year and we get to pay him in milk and cookies!
WilliamR980
100%
0%
WilliamR980,
User Rank: Apprentice
1/5/2017 | 9:51:22 AM
Caption Contest
"New QA engineer.  Checking everything twice."
Page 1 / 11   >   >>
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11354
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-ieee1905.c by making a certain correction to string handling.
CVE-2018-11355
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
CVE-2018-11356
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
CVE-2018-11357
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
CVE-2018-11358
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented certain cleanup.