OPNsense Forum
English Forums => Development and Code Review => Topic started by: cpw on August 10, 2021, 02:55:54 pm
-
Hi,
So, locally, I've fixed the rfc2136 plugin to use the much more flexible auth mechanism in nsupdate (nsupdate -y <keytype>:<server>:<keystring>) man page for nsupdate here: https://linux.die.net/man/8/nsupdate
I would like to submit this back to the community but I have no idea how I would go about doing so. I think that it'd be a good idea to add a field to the UI to capture the key type string, and then construct the -y cmdline value from the three fields (I currently have everything smashed into the keystring field for testing and validation - it works!).
How would I go about helping here? I don't know my way around the UI aspects of opnsense at all (obviously, I've figured out how to generate the nsupdate command tho ;) )
Is this even a good idea? It seems the only way to expose non HMAC-MD5 keys to end users for usage in dns updates.