Why aren't these buffers allocated dynamically and grown on demand? --- bind-9.7.2b1/lib/dns/tkey.c~ 2010-07-10 00:46:27.000000000 +0100 +++ bind-9.7.2b1/lib/dns/tkey.c 2010-08-20 18:05:23.248022587 +0100 @@ -863,7 +863,7 @@ buildquery(dns_message_t *msg, dns_name_ dns_rdataset_makequestion(question, dns_rdataclass_any, dns_rdatatype_tkey); - RETERR(isc_buffer_allocate(msg->mctx, &dynbuf, 4096)); + RETERR(isc_buffer_allocate(msg->mctx, &dynbuf, 8192)); RETERR(dns_message_gettemprdata(msg, &rdata)); RETERR(dns_rdata_fromstruct(rdata, dns_rdataclass_any, @@ -1001,7 +1001,7 @@ dns_tkey_buildgssquery(dns_message_t *ms isc_result_t result; isc_stdtime_t now; isc_buffer_t token; - unsigned char array[4096]; + unsigned char array[8192]; UNUSED(intoken); Even after fixing this it still doesn't work: [dwmw2@i7 ~]$ nsupdate -vg dns.txt ; TSIG error with server: tsig verify failure update failed: REFUSED
Can you run nsupdate with -dD -L99 parameters, please ("nsupdate -dDvg -L99 dns.txt", for example), and attach output here? Can you attach errors from the log on the server side, please? Thank you in advance.
Created attachment 442452 [details] typescript I can't easily get server-side logs, but Samba *can* change the DNS for this host. Am I doing something stupid -- should I be using host-specific Kerberos credentials instead of my own personal TGT?
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
(In reply to David Woodhouse from comment #2) > Am I doing something stupid -- should I be using host-specific > Kerberos credentials instead of my own personal TGT? For the record: yes. and yes. Works in Fedora 19 when I use the correct credentials.