[__opendkim_key] Overall improvements in key management #22

evilham · 2022-03-25T10:04:31Z

evilham commented

2022-03-25 10:04:31 +00:00

While developing this, I noticed that the type was handling inconsistently the
expectation that a cdist object with the same __object_id gets modified.
Instead more and more lines were added to, e.g. SigningTable and KeyTable.

In order to solve this, some backwards compatibility breaking is necessary.

This is probably not too terrible since:

the --selector parameter was mandatory, therefore the fallback for the key
location is triggered.
OpenDKIM uses the first match in SigningTable and KeyTable
__line and __block respectively append if they do not match

Closes #19 and #20

While developing this, I noticed that the type was handling inconsistently the expectation that a cdist object with the same __object_id gets *modified*. Instead more and more lines were added to, e.g. SigningTable and KeyTable. In order to solve this, some backwards compatibility breaking is necessary. This is probably not too terrible since: - the `--selector` parameter was mandatory, therefore the fallback for the key location is triggered. - OpenDKIM uses the first match in `SigningTable` and `KeyTable` - __line and __block respectively append if they do not match Closes #19 and #20

evilham added 3 commits 2022-03-25 10:04:32 +00:00

9473f34910 [__opendkim] FreeBSD: Fix service name inconsistency

This was going to be taken care of in __start_on_boot, but the solution to that
ended up not being generic enough; so this is what we get >,<.

While at it, add various variable value checks where it made sense.

91e8020837 [__opendkim] Deprecate --userid

The parameter could produce inconsistencies permissions-wise.

Users of the type that need this functionality can still use:
--custom-config 'UserId $USERID'

Closes #17

60c6ee54a1

[__opendkim_key] Overall improvements in key management

While developing this, I noticed that the type was handling inconsistently the
expectation that a cdist object with the same __object_id gets *modified*.
Instead more and more lines were added to, e.g. SigningTable and KeyTable.

In order to solve this, some backwards compatibility breaking is necessary.

This is probably not too terrible since:

- the `--selector` parameter was mandatory, therefore the fallback for the key
location is triggered.
- OpenDKIM uses the first match in `SigningTable` and `KeyTable`
- __line and __block respectively append if they do not match

Closes #19 and #20.

evilham added 1 commit 2022-03-25 10:09:39 +00:00

c47d4dbaf2

[__opendkim_genkey] Improve error text for unsupported OS

It was not listing FreeBSD, which is currently supported.

evilham force-pushed opendkim-improvements from c47d4dbaf2 to 7ca0bcf8d9

2023-04-21 13:01:39 +00:00

Compare

fnux referenced this pull request

2024-03-26 15:45:16 +00:00

[__opendkim*] add debian support #28

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.

git checkout -b opendkim-improvements master

git pull origin opendkim-improvements

Step 2:

Merge the changes and update on Gitea.

git checkout master

git merge --no-ff opendkim-improvements

git push origin master

Sign in to join this conversation.

No reviewers

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ungleich-public/cdist-contrib#22