Skip to content

v0.11.30.0 Release

Latest
Latest
Compare
Choose a tag to compare
@bitbound bitbound released this 04 Jan 20:57
v0.11.30.0
b91cfef

Updates

Agent installation now requires the Agent Installer role. As an admin, you will need to give yourself this role to continue installing agents.

Note: You may need to hard refresh and/or log out and back in afterward to access the Deploy page. Access to the backend APIs is updated immediately, though, regardless of how the front-end UI behaves. It's a quirk in the Identity Framework implementation for Blazor that I didn't take the time to figure out.

image

On the Deploy page, you will now generate links that expire either after a total number of uses, or at a certain point in time. The generated links will include an access key and should be treated as a secret.

For now, these are held in a simple memory cache and don't survive reboots.

image

Installation

See the readme for instructions on running in Docker.

Changes:

  • b91cfef Update verbiage.
  • 9b68da7 Update default.yml for Azure Pipelines
  • 913cb57 Update readme.
  • 681ff79 Update README.md
  • 90ea87a Rename ScreenCapturer.
  • 1409856 Add AgentInstaller role. Add AgentInstallerKeyManager tests.
  • 9c0e9dd WIP on installer keys.
  • ccc323d Add installer key to command line args.
  • 3326817 Change single use installer keys to usage-based with a supplied count.
  • 21d6a61 Merge branch 'agent-installer-keys' of ssh.dev.azure.com:v3/translucency/ControlR/ControlR into agent-installer-keys
See More
  • 3c5cc1d WIP on installer keys.
  • 7c0a083 Add UseHttpLogging option in compose file.
  • 047f06b Change default installer key expiration to 1 hour.
  • 301787e WIP on agent installer keys.
  • 08e3c50 Refactor device update in agent hub.
  • b9b9153 WIP on new agent installer flow.
  • bf9461d Ignore query filters for server stats.

This list of changes was auto generated.

Assets 4
Loading