sops/kms
Andy Freeland 89e75471cc Fix KMS encryption context for backwards compatibility with SOPS 1.x
In SOPS 1.x, KMS encryption context was stored as a JSON object, but
SOPS 2.0 stored it as a comma-separated list of key/value pairs:

```
$ jq '.sops.kms | .[].context' encrypted-python
{
  "a": "b",
  "c": "d"
}
> jq '.sops.kms | .[].context' encrypted-go
"a:b,c:d"
```

The two outputs are incompatible with each other and caused a stack
trace when reading files encrypted with SOPS 1.x.

This patch restores read and output compatibility with SOPS 1.x.

Fixes #190.
2017-03-22 09:59:51 -07:00
..
mocks
keysource.go Fix KMS encryption context for backwards compatibility with SOPS 1.x 2017-03-22 09:59:51 -07:00
keysource_test.go Fix KMS encryption context for backwards compatibility with SOPS 1.x 2017-03-22 09:59:51 -07:00