DKIM parsing error

[Greg Linklater]

Hi,

I've been trying to configure chasquid to sign my outgoing messages and can't figure out why dkimsign from driusan/dkim seems to produce extra output when invoked by the post-data hook.

```

20210410 12:41:06.670742 . conn.go:791 Hook.Post-DATA 91.90.44.25:2082: stdout: \"/usr/bin/dkimsign\\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=<domain>; s=<selector>; h=From:Subject:To:Date; bh=R+00iPAWa...; b=arQSDL/D0alca2...0Y72rA==\\n\"
20210410 12:41:06.670911 _ conn.go:814 Hook.Post-DATA 91.90.44.25:2082: error: error parsing post-data output: \"/usr/bin/dkimsign\\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=<domain>; s=<selector>; h=From:Subject:To:Date; bh=R+00...; b=a...PixNmbA5c0Y72rA==\\n\"

```

The signature is being generated correctly; the problem is the content that isn't part of the header; i.e. /usr/bin/dkimsign\\n. When I tried dkimsign myself with the same invocation as in post-data it produced just the header output as expected.

Have you seen this before?

Kind Regards

Greg Linklater

[Alberto Bertogli]

Yes, this was a bug, I'm sorry about that :(

The bug was fixed in 2020-06:
https://blitiri.com.ar/git/r/chasquid/c/b6248f3089d7df93035bbbc0c11edf50709d5eb0/

The fix was included in the 1.5 release.


So upgrading chasquid to 1.5 or above (current release is 1.6) should
fix it.

What version of chasquid are you using? How did you install it? I'm
asking so I can follow up if this was a distribution package, for
example, and try to get it fixed downstream.

Thanks!
Alberto