Install bsh
For a permission whose scripts call bsh, install the helper on every that can run that permission. For a broker inside a container, include the installation in the container image or deployment process so it survives replacement.
Before you begin
Run bsh on Linux or macOS on x86-64 or ARM64. It manages Windows targets remotely through WinRM or directory services. These pages describe version 0.2.0, which adds external references for non-secret values and the Bridge public URL fallback.
Choose a package for a supported Linux distribution or an archive for Linux or macOS.
Install a package
Configure the package repository
Follow the signed repository setup instructions for your distribution at Britive Downloads.
Install the package
sudo apt update
sudo apt install britive-script-helperThe package name is britive-script-helper. It installs /usr/bin/bsh. A package named bsh in your distribution’s own repository may be BeanShell, a different program.
Install from an archive
Download the release files
Open Britive Downloads and select the britive-script-helper release and platform. Download the archive, SHA256SUMS, and SHA256SUMS.asc from the same release.
Platform names are linux_amd64, linux_arm64, darwin_amd64, and darwin_arm64.
Verify the manifest signature
Import the public key using the site’s signing-key instructions. Then verify the checksum manifest:
gpg --verify SHA256SUMS.asc SHA256SUMSContinue only if verification succeeds with the expected signing key.
Verify the archive checksum
On Linux, run:
sha256sum --check --ignore-missing SHA256SUMSConfirm that the downloaded archive reports OK.
On macOS, replace the placeholders and compare the resulting checksum with the archive’s entry in the signed manifest:
shasum -a 256 'britive-script-helper_<version>_<platform>.tar.gz'Install the executable
Replace both placeholders before you extract the verified archive:
tar -xzf 'britive-script-helper_<version>_<platform>.tar.gz'
sudo install -m 0755 bsh /usr/local/bin/bshVerify
Run these commands as the same operating-system user and in the same container or host environment as the permission scripts:
command -v bsh
bsh version
bsh probecommand -v must identify the installed executable. bsh version reports the installed version. bsh probe lists the protocols and methods in that installation without provisioning access.
If bsh is not on the permission script’s PATH, use the executable’s absolute path in the script.
Continue with Configure an SSH permission. If the executable cannot run, see Troubleshoot bsh.