Cedric Kienzler 7ebee3dc7b This fixes a bug with age encryption when specifying multiple age recipients ...

I encountered an issue when I tried so specify multiple age recipients
in the .sops.yaml config file of my repository.

I tried running `sops --age 'agePubKey1,agePubKey2' -e -i values.secret.yaml`
which produced an appropriate file with two entries in the `/sops/age/-`
part of the encrypted yaml file.

However, I then continued to set multiple recipients in my .sops.yaml
file to simplify handling:

```yaml
creation_rules:
  - encrypted_regex: '^(data|stringData|spec)$'
    age: 'agePubKey1,agePubKey2'
```

However, this resulted in encryption only being done for the first
specified agePubKey, not the second or third one.

After digging a bit trough the code, I think this should fix it.

I verified the fix locally on my machine and got it working. Also adding
some unit tests and extending the repository examples so they can be
decrypted using the age keys provided in `age/keys.txt`

Signed-off-by: Cedric Kienzler <github@cedric-kienzler.de>

2022-03-20 22:49:11 +01:00

..

test_resources

Fix golint errors

2017-09-12 09:59:23 -07:00

config_test.go

Match file path relative to config file's directory (2) (#853)

2021-04-12 13:29:06 +02:00

config.go

This fixes a bug with age encryption when specifying multiple age recipients

2022-03-20 22:49:11 +01:00