Filippo Valsorda

Hi! First of all, thank you for your work packaging age, and for reporting things upstream. What that test does (under a layer of abstraction in testscript) is make a...

What kind of input sanitization do you need to do? checkInitialized exists only to catch API misuses where zero-valued Points are used as inputs.

See the plugin package as exposed in https://pkg.go.dev/filippo.io/age/[email protected].

You certainly can't change the policy to a laxer one, otherwise an attacker would just do that, and bypass the point of e.g. always having to touch the key to...

The latest BoringCrypto validation, both according [to the docs](https://github.com/google/boringssl/blob/master/crypto/fipsmodule/FIPS.md#validations) and to a CMVP search is [certificate #4407](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4407). Its [security policy](https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp4407.pdf) specifies 853ca1ea1168dff08011e5d42d94609cc0ca2e27 as the version, which is `fips-20210429`. The Approved...

Discussed this offline with @agl. My understanding is that on the Go side we have three imperfect options: 1. wait for `fips-20220613`, then enable TLS 1.3, missing the [NIST SP...

I understand that `fips-20220613` will be the one we'll hopefully get a certificate for the soonest.

> @FiloSottile sorry, could you help to elaborate on why we didn't go with the currently validated `fips-20210429` for enabling TLS1.3? Thank you! See https://github.com/golang/go/issues/62372#issuecomment-1821413387 and https://github.com/golang/go/issues/62372#issuecomment-1827476258. The `fips-20210429` Security...

@sAnjAy060897 see https://github.com/golang/go/issues/65321 linked above.

> If the `age` specification were to explicitly mention grease, that would be a helpful place to point to (so at least the concept/name has a reference explaining its motivation)....