search

Domain-Connect / spec

Domain Connect Specification
MIT License
73 stars 34 forks source link

Double part of string in Digitally Sign Requests #50

Closed ivan1986 closed 2 years ago

ivan1986 commented 4 years ago

Double part of string in Digitally Sign Requests NCDfnRHut5nG0S3U4cq4DuGrMDFVBwxH1duTsqDNgIOOfNTsFcWSVXoSSTqCCMGbj8Vt51umDhWQAj06lf5 The records would be of the form: end of 2 and start of 3

arnoldblinn commented 4 years ago

I'm not following what you are raising here....

ivan1986 commented 4 years ago

Domain Connect Spec Draft.adoc:721

part 2 ends to substring and part two start fro same substring - in result domain key this part will be doubled.

francoisp-houzz commented 4 years ago

@arnoldblinn I think the issue @ivan1986 is raising is with respect to the example of storing the public key in multiple TXT records to accommodate DNS server limitations.

The relevant part from the specification reads as follows:

p=2,a=RS256,t=x509,d=BEO8bsELQL8GjS4zsjdA53gRk2SDxuzcB4fK+NCDfnRHut5nG0S3U4cq4DuGrMDFVBwxH1duTsqDNgIOOfNTsFcWSVXoSSTqCCMGbj8Vt51umDhWQAj06lf5

p=3,a=RS256,t=x509,d=NCDfnRHut5nG0S3U4cq4DuGrMDFVBwxH1duTsqDNgIOOfNTsFcWSVXoSSTqCCMGbj8Vt51umDhWQAj06lf50qP2/jMNs2G+KTlk3dBHx3wtqYLvdcop1Tk5xBD64BPJ9

The end of p=2 and the beginning of p=3 both include NCDfnRHut5nG0S3U4cq4DuGrMDFVBwxH1duTsqDNgIOOfNTsFcWSVXoSSTqCCMGbj8Vt51umDhWQAj06lf5, while the original public key in the example only includes it once.

pawel-kow commented 2 years ago

Fixed in #66