|Anonymous | Login | Signup for a new account||2017-09-20 06:31 WEST|
|Main | My View | View Issues | Change Log | Roadmap | Docs | My Account|
|Viewing Issue Simple Details|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0000061||[MyDNS-NG] Global||minor||always||2010-10-10 02:44||2010-10-12 01:16|
|Summary||0000061: mydnscheck complaints about invalid characters opendkim|
There are actually two parts to this.
This is really a feature request, not really a bug.
First, requesting that the default character limit for the data field in the rr table should be changed from 128 to a 255 character limit. Opendkim's signatures are longer then 128 character and are therefore chopped off by the field limit.
Second, mydnscheck complains about invalid characters when using opendkim signatures in txt fields. A simple solution to this would be for mydnscheck to check all records but txt records for validity.
|Tags||No tags attached.|
|Seems like line 177 of src/mydns/db.c could be changed from VARBINARY(%u) to CHAR(255) or VARCHAR(255). I'm not sure about pgsql at line 142.|
Ok, well lets scratch the part about changing data to 255 characters, since this is already handled by extended-data-support.
Looks like this ticket can be closed...all that was needed was enabling extended-data-support and re-adding the entries.
Now mydnscheck know longer complains about invalid entries.
|2010-10-10 02:44||stkcode||New Issue|
|2010-10-10 05:00||stkcode||Issue Monitored: stkcode|
|2010-10-10 05:03||stkcode||Note Added: 0000161|
|2010-10-12 01:16||stkcode||Note Added: 0000164|
|Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group|