v3.1.2

What's Changed

• fix: update zlib download use github respository by @JoaoPedroLucatto in #147
• Docker Images Update by @RogerZhongAWS in #126
• Added a backward compatibility CLI option destination-client-type: Fix backward compatibility by @RogerZhongAWS in #150.
  • IMPORTANT: --destination-client-type V1 will be a required parameter when connecting from the AWS console to a destination localproxy or from a source localproxy to the AWS IoT Device Client or Greengrass Secure Tunneling Component. Localproxy V3 → Localproxy V2 connections will require --destination-client-type V2, and Localproxy V3 → Localproxy V3 connections will remain the same.

New Contributors

• @JoaoPedroLucatto made their first contribution in #147

Full Changelog: v3.1.1...v3.1.2

v3.1.1

• The release of Device Client 1.9 introduces a breaking change for users who target devices running Device Client on the destination end of the tunnel. This small patch fixes these interoperability issues.
• If you use Docker images, find the ECR images tagged with the commit SHA associated with this release (Example: public.ecr.aws/aws-iot-securetunneling-localproxy/ubuntu-bin:f63f8fd6c7be216e484b066a8330df415a8600cf)

V3.1.1 pre-release 1

The purpose of this release is to add additional logging for a possible failure mode when new connection ids are not being incremented as expected. Will then determine fixes for this issue in subsequent releases.

Docker Images Release

Docker Images are now live and available at https://gallery.ecr.aws/aws-iot-securetunneling-localproxy

For every linux-based OS, we provide two types of images:

1. Base images have all the dependencies (boost, protobuf, etc) preinstalled. To build the binary, simply clone the repo into a directory and follow the instructions in the README. When spinning up the container, it is recommended to bind mount your host machine's directory to the container so any build artifacts will be accessible from your host machine.

2. The bin images have been stripped of all dependencies and instead have a pre-compiled binary available at /root/bin. It is recommended to use these for quick trials and testing.

Keep in mind that these images are a tool and are not meant to replace your production environment. Direct SSH into the container is not supported at this time because the SSH daemon has either not been enabled or installed in these images.

The README has been updated with more details.

V3.0.2 local proxy

Fixed an issue with data packets becoming lost under certain timing scenarios. #106

V3.0.1 local proxy

V3.0.1 is a patch release updating zlib version to the latest in order to address the latest vulnerability CVE-2022-37434

V3 local proxy

V3 introduces a major enhancement that allows the localproxy to dynamically create, manage, and tear down multiple TCP connections per serviceID simultaneously.

Some new use cases that we now support:

• Loading complex web assets from a private web server. Browser implementations of HTTP may create up to 6 parallel connections to serve requests. Having the localproxy accept these connections simplifies the user experience by not requiring the use of a SOCKS proxy.
• By extension, loading web pages over multiple tabs should result in little performance impact (barring bandwidth and system resource limitations) and allows for continuous data transfer over any number of TCP connections.
• Opening many SSH sessions in parallel. For example, you may configure multiple port forwards using SSH -L

The attached binary has been compiled for x86-ubuntu20.04

V2 local proxy (stable)

Latest tag of the v2 local proxy before the release of v3.
This marks an important update that adds a few new features and fixes a crucial bug that inhibits file transfer over SFTP.

• HTTP proxy support #56
• File transfer bug fix #88
• Added client-token option #92
• Fixed failing tests #91
• Updated Dockerfile and docker build script
• Documentation updates

The attached binary has been compiled for x86-ubuntu.

V2 local proxy

This is to tag the first revision of V2 local proxy.

V1 local proxy

This is to tag the last revision of V1 local proxy.