[Opendnssec-develop] Testing for RC3, found a new zone to test with

[Matthijs Mekking]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I parse "\2" as an escape character followed by a 2. I need to take that
2 literally. So I need to put a '2' in the buffer. The escape character
was not useful, as it is equal to the character string "2".

Now take "\002". This is what I believe is a octal value. This is not
equal to "\2".

To be honest, RFC 1035 does say:

\X              where X is any character other than a digit (0-9), is
                used to quote that character so that its special meaning
                does not apply.  For example, "\." can be used to place
                a dot character in a label.

So, how to handle \X where X is a digit?

1. \X -> 'X'
2. \X -> '\' 'X'


Matthijs

Alexd at nominet.org.uk wrote:
> Hi -
> 
>> Also, I got an error that the NAPTR record was not the same as in the
>> output zone, but I think is a false report from the auditor:
>>
>> Input:
>>
>> all.rr.binary.org. IN NAPTR 100 10 "" ""
>>  "/urn:cid:.+@([^\.]+\.)(.*)$/\2/i" .
>>
>> Output (.finalized):
>>
>> all.rr.binary.org. IN NAPTR 100 10 "" ""
>>  "/urn:cid:.+@([^.]+.)(.*)$/2/i" .
>>
> 
> Should output not actually be :
> 
> all.rr.binary.org. IN NAPTR 100 10 "" ""
> "/urn:cid:.+@([^.]+.)(.*)$/\002/i" .
> 
> or
> 
> all.rr.binary.org. IN NAPTR 100 10 "" "" "/urn:cid:.+@([^.]+.)(.*)$/\2/i" .
> 
> ?
> 
> Thanks,
> 
> 
> Alex.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBAgAGBQJLYCM0AAoJEA8yVCPsQCW55bEIAI/r9FcsyK+pTXV98bkp6N3I
4jnQIGLYGBGMDa2XSzbWgwbmFv4K+LKW2epCSx1KNBRWQrhjCAo2A10cw4maQa3l
1m27q6sfuZZ5tTg5xuKmaTW+RZJYFNtWsHvWr9tdqgA+CLZ1uYdf8OlYPiCSsFkZ
efcix48IfWtrLRCM/LZLhh3oLqiKeIFSOftuNTfFtgU5HVH9JAdNcQwGeFiSTubz
s8qw/NhJWWyertWZjHEV1MhYkH3jRmhCc/Y2nyNx/fXUp4Fa6s+1p0g5YtJoonTa
n2aw5Lmkrn2TQwsm8sVMNtg7Jkp4sv1YGXwNI2ZbvkBjdv2dw1pyXCMpus119DE=
=n+Ja
-----END PGP SIGNATURE-----