Skip to content

Releases: openziti/ziti-tunnel-sdk-c

v2.0.0-alpha1

12 Jun 16:09
3f6b15c
Compare
Choose a tag to compare
v2.0.0-alpha1 Pre-release
Pre-release

What's Changed

Full Changelog: v0.22.32...v2.0.0-alpha1

v1.0.0

12 Jun 15:30
1416e2a
Compare
Choose a tag to compare

Changes

initialize logger after command line parsing; use fprintf before then @scareything (#850)

avoids unwanted logger initialization messages for subcommands like version.

More flexible versions @ekoby (#849)

v0.22.32

07 Jun 10:32
afe442f
Compare
Choose a tag to compare

Changes

get ziti-sdk-c 1.0.4 @scareything (#848)

This sdk update includes fixes to prevent new requests from piling up when the controller is unavailable.

initialize ziti logger before command line parsing @scareything (#846)

This change activates the logger early in the process startup, so messages that are logged during command line parsing are visible.
Also don't let the log level from value from the config file replace the level that was specified on the command line.

Assume http proxy if type is not specified @scareything (#847)

This matches the behavior of golang's proxy url processing, and enables HTTP_PROXY to be set with the same format that the ER recognizes.

v0.22.31

05 Jun 14:30
ee8c959
Compare
Choose a tag to compare

Changes

Support using http proxy for outbound connections @scareything (#845)

Outbound connections to controllers, routers and hosted servers can be made through a proxy server.

The proxy for controller and router connections is specified with the -x command line option or the HTTP_PROXY environment variable. The value is a URL of the form type://[user[:pass]@]hostname:port. At this time "http" is the only supported type, and Basic authentication is assumed if credentials are provided.

ziti-edge-tunnel run -I /opt/openziti/etc/identities -x http://user:pass@proxyhost:port

Proxies for hosted server connections can be configured by populating the "proxy" field in the host.v1 service configuration.

{
    "address": "127.0.0.1",
    "listenOptions": {
        "identity": "$tunneler_id.name"
    },
    "port": 22,
    "protocol": "tcp",
    "proxy": {
        "address": "localhost:3128",
        "type": "http"
    }
}

Wait for systemd tun device unit to be active before configuring dns @scareything (#837)

A race condition could lead to systemd resetting the resolver configuration that was applied by ziti-edge-tunnel

v0.22.30

29 Apr 20:31
94b479f
Compare
Choose a tag to compare
v0.22.30 Pre-release
Pre-release

Changes

wait for systemd tun device unit to be active before configuring dns @scareything (#837)

v0.22.29

26 Apr 15:32
90b416d
Compare
Choose a tag to compare

Changes

get ziti-sdk-c 0.36.11 / tlsuv 0.28.5 @scareything (#836)

check dns response buffer as it is filled, and set truncate flag accordingly @scareything (#831)

Use mingw to build windows-x64 binaries @scareything (#826)

v0.22.28

12 Apr 17:29
9110284
Compare
Choose a tag to compare

Changes

get ziti-sdk-c 0.36.10 @scareything (#832)

check dns response buffer as it is filled, and set truncate flag accordingly @scareything (#831)

Use mingw to build windows-x64 binaries @scareything (#826)

v0.22.27

02 Apr 14:33
964e6ab
Compare
Choose a tag to compare
v0.22.27 Pre-release
Pre-release

Changes

Use mingw to build windows-x64 binaries @scareything (#826)

v0.22.26

27 Mar 16:56
f3adeff
Compare
Choose a tag to compare

Changes

Handle proxy dns responses correctly @scareything (#827)

There were two issues that prevented proxied dns queries from working:

  1. The ziti connection that dns queries are sent over is not established (by design) when the first request is sent with ziti_write. The intent is to rely on ziti_write queueing the message until the connection is established, but there was a problem in ziti-sdk-c that caused crypto hash checks to fail for messages that were sent before the connection was ready. This was fixed with ziti-sdk-c 0.36.9.
  2. The write callback associated with sending the dns query to the hosting tunneler was incorrectly treating the "length" parameter as "status", so even when a message was sent successfully, the tsdk responded to the original DNS client with SRVFAIL.

Declare data pointer as const @scareything (#825)

This fixes a build error when using Xcode 15.3

v0.22.25

06 Mar 19:39
fda6af5
Compare
Choose a tag to compare

Changes

Avoid invalid memory access when services with hostname intercept addresses become unavailable. @scareything (#822)

Avoid segvs when processing add command @scareything (#821)