If you use the right library --- Nacl or Keyczar, or call out to PGP --- you don't need to be an expert to build cryptography into your application.

In all the stories you read about some generalist developer blowing their users' feet off with bad crypto, what you're reading about is someone reinventing these libraries with vanity crypto.

Edited, original from https://code.google.com/p/keyczar/wiki/CppTutorial

  keyczar::Keyczar* crypter = keyczar::Crypter::Read(location);
  if (!crypter)
    return;

  crypter->set_compression(keyczar::Keyczar::ZLIB);

  std::string input = "Hey Alice, here is Eves message: [quote]"+superescape(evemessage)+"[/quote] Your Bob";
  std::string ciphertext;
  bool result = crypter->Encrypt(input, &ciphertext);

Ooops because, http://arstechnica.com/security/2012/09/many-ways-to-break-s...

Sure. I think that speaks to my point; the compression side channel was novel enough that trained cryptographers missed it in Keyczar.

(Just don't use compression with your encryption and avoid the issue entirely).

Well, even if they removed it, our hypothetical library user could do it by themselves if not told not to.