Latest Blog Posts for Plaintext

• Software Security's Futures Plural
  on Dec 7, 2010 in article
  An update on BeeWise.
• Untwisted: Bit-sliced TEA time
  on Dec 6, 2010 in article
  Or an introduction to bitslicing a block cipher, for those who will not confuse the algorithm with their tea bread.
• secYOUre tweeted on Mon Dec 06 00:04:40 +0000 2010
  on Dec 5, 2010 in tweet
  I'll be speaking at MiniMetricon 5.5 (coloc with RSA) in SF on 14th Feb about BeeWise.com. If you are attending, please stop by and say Hi!
• BeeWise - Security Event Futures
  on Nov 18, 2010 in article
  A first testbed for a security event-futures exchange.
• Backward Insecurity: Network Externalities Strike Back
  on Nov 16, 2010 in article
  Or why we will observe downgrade attacks, again.
• Ali Baba, Waldo and the Dining Cryptographers
  on Nov 10, 2010 in article
  Teach your children the story of Ali Baba: how he managed to convince the NSA that he knew where Waldo was without disclosing his location, how later he joined him for a dinner with other fellow cryptographers, how they discovered their banquet was a...
• Stuxnet: a Glimpse into the Future of Malware and its Interplay with Information Warfare
  on Nov 2, 2010 in article
  When national security and economic security becomes inseparable.
• Call for Participation, Mini-Metricon 5.5
  on Nov 1, 2010 in article
  If you are interested in security metrics, as I really do, please consider to submit a discussion topic by November 12 and join our meeting at Mini-Metricon 5.5.
• A blog plain with security stakeholders
  on Oct 13, 2010 in article
  Or on the reasons for a blog at the intersection of software security, economics and market.
• Back Cover
  on Oct 10, 2010 in text
  Plaintext hosts the the security musings, thoughts and items of interest that escape from the head of Alfonso De Gregorio and reach by chance the keyboard. If you stumble upon any of them asking the way back to home, feel free to try to help using th...

{pvComments::user_name}

{pvComments::date}

Delete 

{pvComments::comment}

Post a Comment