freddygv 65bcd3d84f 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
..
peering.gen.go	Add ACL enforcement to peering endpoints	2022-07-25 09:34:29 -06:00
peering.go	Use proto message for each secrets write op	2022-08-08 01:41:00 -06:00
peering.pb.binary.go	Use proto message for each secrets write op	2022-08-08 01:41:00 -06:00
peering.pb.go	Re-validate existing secrets at state store	2022-08-08 09:06:07 -06:00
peering.proto	Re-validate existing secrets at state store	2022-08-08 09:06:07 -06:00
peering.rpcglue.pb.go	Add ACL enforcement to peering endpoints	2022-07-25 09:34:29 -06:00
peering_grpc.pb.go	proto: add package prefixes for all proto files where it is safe (#13735)	2022-07-13 11:03:27 -05:00
peering_oss.go	peering: initial sync (#12842)	2022-04-21 17:34:40 -05:00