Nebula v1.6.0 Release Notes
Release Date: 2022-06-30 // over 2 years ago-
โ Added
๐ง Experimental: nebula clients can be configured to act as relays for other nebula clients. Primarily useful when stubborn NATs make a direct tunnel impossible. (#678)
๐ง Configuration option to report manually specified
ip:port
s to lighthouses. (#650)๐ Windows arm64 build. (#638)
๐
punchy
and mostlighthouse
config options now support hot reloading. (#649)
๐ Changed
๐ Build against go 1.18. (#656)
๐ Promoted
routines
config from experimental to supported feature. (#702)โก๏ธ Dependencies updated. (#664)
๐ Fixed
๐ Packets destined for the same host that sent it will be returned on MacOS. This matches the default behavior of other operating systems. (#501)
๐
unsafe_route
configuration will no longer crash on Windows. (#648)A few panics that were introduced in 1.5.x. (#657, #658, #675)
๐ Security
- You can set
listen.send_recv_error
to control the conditions in whichrecv_error
messages are sent. Sending these messages can expose the fact that Nebula is running on a host, but it speeds up re-handshaking. (#670)
โ Removed
- ๐
x509
config stanza support has been removed. (#685)
Previous changes from v1.5.2
-
โ Added
- ๐ง Warn when a non lighthouse node does not have lighthouse hosts configured. (#587)
๐ Changed
No longer fatals if expired CA certificates are present in
pki.ca
, as long as 1 valid CA is present. (#599)nebula-cert
will now enforce ipv4 addresses. (#604)๐ Warn on macOS if an unsafe route cannot be created due to a collision with an existing route. (#610)
๐ Warn if you set a route MTU on platforms where we don't support it. (#611)
๐ Fixed
Rare race condition when tearing down a tunnel due to
recv_error
and sending packets on another thread. (#590)๐ Bug in
routes
andunsafe_routes
handling that was introduced in 1.5.0. (#595)โ
-test
mode no longer results in a crash. (#602)
โ Removed
x509.ca
config alias forpki.ca
. (#604)
๐ Security
- โฌ๏ธ Upgraded
golang.org/x/crypto
to address an issue which allowed unauthenticated clients to cause a panic in SSH servers. (#603)