Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC2136 GSS-TSIG verify checksum fails #5123

Open
kluoto opened this issue Feb 24, 2025 · 0 comments
Open

RFC2136 GSS-TSIG verify checksum fails #5123

kluoto opened this issue Feb 24, 2025 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@kluoto
Copy link

kluoto commented Feb 24, 2025

I configured RFC2136 provider with the gss-tsig authentication. I am able to authenticate against Windows AD and register records to Windows DNS, but the verification of the servers response message fails.

From the logs I see message:

2025-02-24T09:00:15Z" level=warning msg="warn in dns.Client.Exchange: checksum mismatch. Computed: xxxxxxxxxxxxxxxxxxxxxxxx, Contained in token: yyyyyyyyyyyyyyyyyyyyyyyy"

This message is from: https://github.com/jcmturner/gokrb5/blob/855dbc707a37a21467aef6c0245fcf3328dc39ed/v8/gssapi/MICToken.go#L119

Version used:

GSS-TSIG algorithm used is aes256-cts-hmac-sha1
External-DNS: v0.15.1
DNS Provider: rfc2136

I did try to use the code from master branch, but that version exits on the verify error and external-dns goes to restart loop. As that implementation seems to not ignore the checksum validation as it does in version v0.15.1. With the master, I also had problems with the Kerberos realm being overwritten with the zone in upper case, which is not correct in my case as the zone is different from the Kerberos realm.

@kluoto kluoto added the kind/bug Categorizes issue or PR as related to a bug. label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant