consul/proto
freddygv 1031ffc3c7 Re-validate existing secrets at state store
Previously establishment and pending secrets were only checked at the
RPC layer. However, given that these are Check-and-Set transactions we
should ensure that the given secrets are still valid when persisting a
secret exchange or promotion.

Otherwise it would be possible for concurrent requests to overwrite each
other.
2022-08-08 09:06:07 -06:00
..
pbacl proto: add package prefixes for all proto files where it is safe (#13735) 2022-07-13 11:03:27 -05:00
pbautoconf proto: add package prefixes for all proto files where it is safe (#13735) 2022-07-13 11:03:27 -05:00
pbcommon proto: add package prefixes for all proto files where it is safe (#13735) 2022-07-13 11:03:27 -05:00
pbconfig proto: add package prefixes for all proto files where it is safe (#13735) 2022-07-13 11:03:27 -05:00
pbconfigentry proto: add package prefixes for all proto files where it is safe (#13735) 2022-07-13 11:03:27 -05:00
pbconnect proto: add package prefixes for all proto files where it is safe (#13735) 2022-07-13 11:03:27 -05:00
pbpeering Re-validate existing secrets at state store 2022-08-08 09:06:07 -06:00
pbpeerstream Implement/Utilize secrets for Peering Replication Stream (#13977) 2022-08-01 10:33:18 -04:00
pbservice peerstream: require a resource subscription to receive updates of that type (#13767) 2022-07-15 15:03:40 -05:00
pbstatus proto: add package prefixes for all proto files where it is safe (#13735) 2022-07-13 11:03:27 -05:00
pbsubscribe proxycfg-glue: server-local implementation of `ServiceList` 2022-07-14 18:22:12 +01:00
prototest peerstream: require a resource subscription to receive updates of that type (#13767) 2022-07-15 15:03:40 -05:00
buf.gen.yaml Migrate from `protoc` to `buf` (#12841) 2022-05-23 10:37:52 -04:00
buf.yaml Migrate from `protoc` to `buf` (#12841) 2022-05-23 10:37:52 -04:00