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

Option to provide AXFR secret (TSIG) #981

Open
Af0x opened this issue Oct 11, 2021 · 9 comments
Open

Option to provide AXFR secret (TSIG) #981

Af0x opened this issue Oct 11, 2021 · 9 comments

Comments

@Af0x
Copy link

Af0x commented Oct 11, 2021

Hello,

to secure the AXFR transfer I want to request an option to add a TSIG secret in the DNS options.

Best regards,

Af0x

@d00p
Copy link
Member

d00p commented Oct 11, 2021

That would also require to include DNSSEC if i see this correctly

@Af0x
Copy link
Author

Af0x commented Oct 11, 2021

I think those are two different things.
Example guide for bind: https://www.cyberciti.biz/faq/unix-linux-bind-named-configuring-tsig/
Bind manual: https://bind.isc.org/doc/arm/9.11/Bv9ARM.ch04.html#tsig

Summary:

  • create a key file on the master and the slave to define the key and instruct to sign all transactions
  • include that file in the .conf file
  • use the key in the allow-transfer statement of the zone

@d00p
Copy link
Member

d00p commented Oct 11, 2021

According to that guide, if such key is already setup, we'd only need the key "name" for the generated zones.

@Af0x
Copy link
Author

Af0x commented Oct 11, 2021

If you mean included with setup, yes. The impact in the conf file is quite minimal. But you need to create that keyfile with the key itself and instructions to use the key "name" for the AXFR slave IP address. What I´m not sure about is if you can use the same key for multiple slaves or if you have to set one key per slave.

@Af0x
Copy link
Author

Af0x commented Oct 11, 2021

addition: you are probably right. you just need to define the key and add it to the allow-transfer section of the zone. No need to add the slave in the keyfile - if I read the bind docs correctly:

Once a key has been added to named.conf and the server has been restarted or reconfigured, the server can recognize the key. If the server receives a message signed by the key, it is able to verify the signature. If the signature is valid, the response is signed using the same key.

@d00p
Copy link
Member

d00p commented Oct 11, 2021

That's what I meant, everything else needs to be done on master AND Slave hence not much sense for froxlor to do that only for the master. Maybe we can provide a small tutorial in our wiki for the creation and integration so People are not totally lost, what do you think?

@Af0x
Copy link
Author

Af0x commented Oct 11, 2021

If that feature is present, of course. The slave has to be configured manually anyway. Only thing froxlor needs to do is to include the key/ make it possible to use that key in the AXFR field.

@Af0x
Copy link
Author

Af0x commented Oct 12, 2021

Just to clarify: there has to be some work within froxlor to make use of that key, correct?

@d00p
Copy link
Member

d00p commented Oct 12, 2021

Depends. When froxlor should also do the key-mgmt and creation and named config then yes. If it's just the key-entry for every zone, then it's not a big deal

@d00p d00p mentioned this issue Oct 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants