consul

Commit Graph

Author	SHA1	Message	Date
Matt Keeler	01f82717b4	Vendor the vault api	2018-06-25 12:26:10 -07:00
Kyle Havlovitz	bd42da760b	vendor: pull in latest version of go-discover	2018-05-10 15:40:16 -07:00
Pierre Souchay	9dc7194321	Bump version of miekg/dns to 1.0.4 See https://github.com/hashicorp/consul/issues/3977 While trying to improve furthermore #3948 (This pull request is still valid since we are not using Compression to compute the result anyway). I saw a strange behaviour of dns library. Basically, msg.Len() and len(msg.Pack()) disagree on Message len. Thus, calculation of DNS response is false consul relies on msg.Len() instead of the result of Pack() This is linked to miekg/dns#453 and a fix has been provided with miekg/dns#454 Would it be possible to upgrade miekg/dns to a more recent function ? Consul might for instance upgrade to a post 1.0 release such as https://github.com/miekg/dns/releases/tag/v1.0.4	2018-03-28 10:23:57 -05:00

Author

SHA1

Message

Date

Matt Keeler

01f82717b4

Vendor the vault api

2018-06-25 12:26:10 -07:00

Kyle Havlovitz

bd42da760b

vendor: pull in latest version of go-discover

2018-05-10 15:40:16 -07:00

Pierre Souchay

9dc7194321

Bump version of miekg/dns to 1.0.4

See https://github.com/hashicorp/consul/issues/3977

While trying to improve furthermore #3948 (This pull request is still valid since we are not using Compression to compute the result anyway).

I saw a strange behaviour of dns library.
Basically, msg.Len() and len(msg.Pack()) disagree on Message len.

Thus, calculation of DNS response is false consul relies on msg.Len() instead of the result of Pack()

This is linked to miekg/dns#453 and a fix has been provided with miekg/dns#454

Would it be possible to upgrade miekg/dns to a more recent function ?

Consul might for instance upgrade to a post 1.0 release such as https://github.com/miekg/dns/releases/tag/v1.0.4

2018-03-28 10:23:57 -05:00

3 Commits (9406ca1c959e591299351dfaf26fbf0c26dd71c0)