Profile_bird

Hey there! tolzak is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving tolzak's tweets.

Already using Twitter
from your phone? Click here.

tolzak

  1. Sun VirtualBox Guest Additions Local Denial Of Service Vulnerability http://ow.ly/D6eA
  2. - A year later: A look back at McColo http://ow.ly/BUTI [Surgical strikes work, but are they like dropping a pebble in a gravel pit...]
  3. Microsoft defends Hotmail's cookie requirement • The Register http://ow.ly/BUCn [Are you kidding me...?]
  4. The Seven Deadly Sins of Security Policy - CSO Online - Security and Risk http://ow.ly/BGxg
  5. Unpatched SMB Bug Crashes Windows 7, Researcher Says http://ow.ly/BFf6 [MS knew about but didn't patch exploited DoS vulnerability in W7]
  6. Hackers will exploit Windows kernel bug, researchers say http://ow.ly/BF8Z [Kernel exploit that doesn't play in your sandbox]
  7. How to DDOS a federal wiretap http://ow.ly/BEOB [Something to consider when looking at wiretap evidence authentication]
  8. It's easy to launch an attack against RDP http://ow.ly/BoQt [Excellent ARP poisoning video included.]
  9. Security firm chokes sprawling spam botnet http://ow.ly/Borp [That's one for the good guys.]
  10. Schneier on Security: Laissez-Faire Access Control http://ow.ly/B4GZ [Couldn't disagree more. What happened to prevention?] (#infosecblogs)
  11. @bbaskin Re: Universal Sign: There is, but you'd probably get fired for using it in the office...
  12. RT @kvashee: Gartner in court over Magic Quadrant dispute http://bit.ly/49z1r5
  13. Gov't warns firms about online robberies http://ow.ly/zBHY
  14. (#infosecblogs) Building a Better Mousetrap: Two Factor Passphrases http://ow.ly/15ZuA6
  15. Building a Better Mousetrap: Two Factor Passphrases http://ow.ly/zgqe (#infosecblogs)
  16. @SecRunner RE: sushi. If you're ever in Toledo, OH, check out Kyoto Ka. Just got 5-star review (disclosure... My wife and I own it...)
  17. @sfoak Depends on expected outcomes. If you are confident you can quickly identify a physical breach, 30 days should be fine.
  18. @sfoak RE: video/breack http://tinyurl.com/ygx6oba
  19. @danphilpott Ill-considered policies is a big part of it. I agree. Military a little out of their element on this. #infosecblogs
  20. U.S. Cyber-warfare defense: The weak link http://ow.ly/xFEn (#infosecblogs)