Skip to content

Commit

Permalink
README: keys group is not required anymore for a long time
Browse files Browse the repository at this point in the history
  • Loading branch information
Mic92 committed Oct 3, 2023
1 parent f5ddf92 commit 9de50ec
Showing 1 changed file with 0 additions and 23 deletions.
23 changes: 0 additions & 23 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -503,25 +503,6 @@ Consider the following nixos configuration example:
}
```

To access secrets each non-root process/service needs to be part of the keys group.
For systemd services this can be achieved as following:

```nix
{
systemd.services.some-service = {
serviceConfig.SupplementaryGroups = [ config.users.groups.keys.name ];
};
}
```

For login or system users this can be done like this:

```nix
{
users.users.example-user.extraGroups = [ config.users.groups.keys.name ];
}
```

<details>
<summary>This example configures secrets for buildkite, a CI agent;
the service needs a token and a SSH private key to function.</summary>
Expand All @@ -544,10 +525,6 @@ the service needs a token and a SSH private key to function.</summary>
};
systemd.services.buildkite-agent-builder = {
serviceConfig.SupplementaryGroups = [ config.users.groups.keys.name ];
};
sops.secrets.buildkite-token.owner = config.users.buildkite-agent-builder.name;
sops.secrets.buildkite-ssh-key.owner = config.users.buildkite-agent-builder.name;
}
Expand Down

0 comments on commit 9de50ec

Please sign in to comment.