Description

Emissary Outbound: Deploy your Protected Services that live “behind enemy lines”.

Punch a hole outward with Emissary Outbound to create a Protected Service where you don’t control the network / can’t allow ingress from the internet.

Emissary Outbound creates a tunnel between a service it can access and Drawbridge, effectively making Emissary a mini-Drawbridge.

Your machines can now securely proxy out connections to local services to Drawbridge as a Protected Service.

How to use

Emissary Outbound is now a feature of the Emissary-Daemon client. It is enabled via passing two fields in the command line when launching Emissary:
--outbound is the host and port for the service you want to allow access to via Drawbridge
--service-name MUST be 15 characters in length with no special characters due to a bug. This will be fixed in the non-preview version.

Note: With this update, you will not see this Protected Service in the Drawbridge Dashboard yet, but you will in any connecting Emissary clients.

Example for a Minecraft server (note you'll need to change the address and port if using a different computer or port):
./Emissary_program --outbound localhost:25565 --service-name MinecraftServer

Now, when a regular Emissary client connections to your Outbound-Protected service, the connection flow will look like this:
Emissary <-> Drawbridge <-> Emissary Outbound <-> Outbound-Protected service (e.g Minecraft server)

Assets 8

30 Mar 04:55

imdawon

v0.4.0-alpha

a76964c

Retries and Connection Clarity (v0.4.0-alpha) Latest

Latest

This update adds:

Retries in case of connection failures.
Clearer language in the terminal output for Protected Service address. localhost wasn't there before, making it confusing as to where the Protected Service was actually accessible from.

Note: ALL Emissary client updates should be served via Emissary Bundles and not directly downloaded from GitHub

Assets 8

26 Mar 04:17

imdawon

v0.3.2-alpha

f1c5205

Hotfix for Emissary Bundles (v0.3.2-alpha)

Fix: previous version of Emissary (0.3.1-alpha) did not read from the bundle/drawbridge.txt file.

This is the first official Emissary version to support the Emissary Bundle! Now you can use Emissary without needing to manually configure it in the console application! A Drawbridge admin, using at least Drawbridge v0.5.0-alpha, can generate Emissary bundles.

Happy hosting!

Assets 8

25 Mar 19:43

imdawon

v0.3.1-alpha

db94968

Additional Support for Emissary Bundles (v0.3.1-alpha)

We no longer nest the Emissary binary in the release folder as this was causing a headache with supporting Emissary Bundles in Drawbridge. No functional changes have been made other than the structure of our release .zips.

Happy hosting!

Assets 8

24 Mar 06:03

imdawon

0.3.0-alpha

0514339

Support Emissary Bundles (v0.3.0-alpha)

Note: We now use .asc instead of .sig files to make verification easier. It is way easier for me to automate stuff using the .asc format.

Emissary Bundles are the hot new thing. I don't like configuring Emissary. You don't like configuring Emissary. We fixed it with the Emissary Bundle.

A Drawbridge admin can click a button to generate an Emissary bundle for a specific machine. It contains the encryption key(s), certificate, and Drawbridge address info alongside the latest Emissary client, so your fleet of machines can connect with no requirement to move files around.

I know, right?

Enjoy! A Drawbridge release to support this will be released soon.

Other notes:
GitHub doesn't count releases as "Releases" if you check the "Set as a pre-release button" during the creation of a new release.

So this release won't be published like that, so Drawbridge can grab the latest release via the GitHub API.

Assets 8