News for hackers. Stuff that matters.
Re:Restic Cryptography by azinman2 on Thursday August 31, 2017 @12:47PM (#15141624)
Ok so the issue is patents and how hard it is to write from scratch. I’m looking at it from the user of crypto perspective. I assume it’s all on a range of hard to super hard to implement (not just to get it working, but deal with side channel attacks, etc).

If you don’t care about a built in MAC, would you recommend CTR? OCB?

Re:Restic Cryptography by loup-vaillant on Thursday August 31, 2017 @06:18PM (#15144436)
> I’m looking at it from the user of crypto perspective.

The user wants something that works reliably. If it's hard to implement, confidence decreases. You can compensate with external audits, but those are expensive.

> If you don’t care about a built in MAC, would you recommend CTR? OCB?

You almost always care about built in MAC. If you don't authenticate your data, you will most likely run into trouble. And if you really don't care, I'd rather sidestep the CTR vs OCB vs WTF entirely by using Chacha20 (fast without dedicated hardware, naturally immune to timing attacks, dead simple to implement).

(In the general case, I'd recommend Chacha20 + Poly1305 constructions.)

Re:Restic Cryptography by Johnny_Brahms on Friday September 01, 2017 @01:07AM (#15146241)
Use whatever vetted AEAD mode that is available to you. That probably means AES-GCM or Chacha20 + Poly1305).

If you don't have any very good reasons to use CTR (encrypting lots of data with the same key) you.probably shouldn't.