News for hackers. Stuff that matters.
Re:Introducing the Tink cryptographic software library by tptacek on Thursday August 30, 2018 @05:08PM (#17880789)
Tink competes with Nacl/libsodium.

Tink is really great and more people should look at it. It's (I think?) the successor to Keyczar, which was one of the first misuse-resistant crypto libraries.

Some ways in which Tink differs from Nacl:

* Its interfaces are in some ways better; for instance, it doesn't punt nonces to the developer (a source of security issues with Nacl software).

* It has a coherent design based on security objectives, so that extensions to it make sense. For instance, instead of exposing random block cipher modes in a low-level interface, Tink maintains a notion of AEAD, streaming AEAD, and deterministic AEAD, and then has interfaces to add primitives that fulfill those objectives.

* Tink is natively (rather than through bindings) portable to Java, C++, and ObjC.

* Tink has a team of cryptographers maintaining it; that team includes Daniel Bleichenbacher, which is crazy and awesome.

Nacl is great, but more people should look at Tink.

Re:Introducing the Tink cryptographic software library by loeg on Thursday August 30, 2018 @09:24PM (#17882242)
Notably (and unlike NaCl/libsodium), Tink is not portable to plain C.
Re:Introducing the Tink cryptographic software library by dietr1ch on Friday August 31, 2018 @03:04AM (#17883516)
I hope that stops being a cons someday.
Re:Introducing the Tink cryptographic software library by pvg on Thursday August 30, 2018 @05:42PM (#17881046)
Another difference seems to be KMS support.