App Finder for Tunnel
Release Date: November 27, 2019
This application is a utility which can be used for conveniently flagging the applications to use WorkspaceONE Tunnel on macOS. On macOS, WorkapceONE Tunnel supports per-app VPN feature where only the whitelisted applications can be Tunneled rather than tunneling the entire device traffic. In order to whitelist the application to use Tunnel, admin needs to enter the following details on the Workspace UEM Console under "VMware Tunnel" device traffic rule:
- Friendly name
- Package ID
- Designated requirement
- Path (this is used only for the pure non-bundle binaries like Curl and ssh)
This fling application supports the basic drag and drop interface which admin can launch and then drag and drop the application to be flagged to use per-app VPN (Firefox in the following case), once the applicatin is dropped, it's attributes are listed and then admin can paste those in the UEM console as shown below:
- MacOS 10.11+
- Workspace ONE admin
- Download the pkg of this Fling
- Install it on the macOS device
- When the admin wants to flag any application like say "Chrome" to use Tunnel, just open the "Tunnel App Finder" application
- Drag and drop the "Chrome.app" onto it
The "Tunnel App Finder" application will list all the details of the Chrome binary, such as bundle identifier, designated requirement and path, which a user can enter into the UEM Console to flag Chrome to use per-app VPN via VMware Tunnel application.
No similar flings found. Check these out instead...
Federated Machine Learning on Kubernetes
FATE is an opensource project hosted by Linux Foundation to provide a federated learning framework. FATE has been used to increase the performance of predictions in credit reporting, insurance and other financial areas, as well as surveillance and visual detection projects. It helps organizations to comply with strict privacy regulations and laws such as GRDP and CCPA.
DoD Security Technical Implementation Guide(STIG) ESXi VIB
This VIB has been developed to help customers rapidly implement the more challenging aspects of the vSphere STIG. These include the fact that installation is time consuming and must be done manually on the ESXi hosts. In certain cases, it may require complex scripting, or even development of an in-house VIB that would not be officially digitally signed by VMware (and therefore would not be deployed as a normal patch would).