You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building hono locally using the profile run-tests may currently fail, if 127.0.0.1.nip.iocould not be resolved.
That may be caused by DNS rebinding protection, especially, if executed in a home-network behind an internet router.
To support also builds without disable that protection, the test may be skipped, if 127.0.0.1.nip.io could not be resolved.
The text was updated successfully, but these errors were encountered:
Using Ubuntu Resolve - 8.8.8.8 works as well, but removes the DNS rebinding protection.
I use an Ubuntu-derived distro with systemd-resolved resolver and the snippet below added to /etc/systemd/resolved.conf has permanently solved the issue:
[Resolve]
DNS=8.8.8.8
Domains=~nip.io
Needed to restart the service afterwards sudo service systemd-resolved restart
So all queries to nip.io are resolved by Google DNS, which apparently doesn't have the DNS rebind protection.
…upported
The integration tests verifying SNI based client authentication are now
run only if DNS rebinding for the nip.io domain works in the local
environment.
Fixeseclipse-hono#3183
Signed-off-by: Kai Hudalla <kai.hudalla@bosch.io>
…upported
The integration tests verifying SNI based client authentication are now
run only if DNS rebinding for the nip.io domain works in the local
environment.
Fixeseclipse-hono#3183
Signed-off-by: Kai Hudalla <kai.hudalla@bosch.io>
The integration tests verifying SNI based client authentication are now
run only if DNS rebinding for the nip.io domain works in the local
environment.
Fixes#3183
Signed-off-by: Kai Hudalla <kai.hudalla@bosch.io>
Building hono locally using the profile run-tests may currently fail, if
127.0.0.1.nip.io
could not be resolved.That may be caused by DNS rebinding protection, especially, if executed in a home-network behind an internet router.
To support also builds without disable that protection, the test may be skipped, if
127.0.0.1.nip.io
could not be resolved.The text was updated successfully, but these errors were encountered: