# std/crypto: add AES-OCB · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/a5a3ad4f956bae1ca0e5a49de2e9ac7145170039)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: a5a3ad4f956bae1ca0e5a49de2e9ac7145170039

Requested commit: a5a3ad4f956bae1ca0e5a49de2e9ac7145170039

Commit: a5a3ad4f956bae1ca0e5a49de2e9ac7145170039

Tree: 713106289091e9eea404dbf3267b1967d5998b06

Author: Frank Denis

Committer: Andrew Kelley

## Message

```
std/crypto: add AES-OCB

OCB has been around for a long time.

It's simpler, faster and more secure than AES-GCM.

RFC 7253 was published in 2014. OCB also won the CAESAR competition
along with AEGIS.

It's been implemented in OpenSSL and other libraries for years.

So, why isn't everybody using it instead of GCM? And why don't we
have it in Zig already?

The sad reason for this was patents. GCM was invented only to work
around these patents, and for all this time, OCB was that nice
thing that everybody knew existed but that couldn't be freely used.

That just changed. The OCB patents are now abandoned, and OCB's
author just announced that OCB was officially public domain.

```

## Parents

- [58b14d01aeb919989d1750a8894350a07fd4e844](https://git.cafe/gitcafe/zig/commit/58b14d01aeb919989d1750a8894350a07fd4e844?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/a5a3ad4f956bae1ca0e5a49de2e9ac7145170039?format=markdown)
