BSD Ports

sysutils/rubygem-openbolt 5.6.0 DragonFly

Execute commands remotely over SSH and WinRM

System
DragonFly
Repository
DPorts
Maintainer
[email protected] (as in FreeBSD)
License
APACHE20
Categories
rubygems, sysutils
Package size
214.7 KiB, 1076.9 KiB installed

Description

OpenBolt is an open source orchestration tool that automates the manual work it takes to maintain your infrastructure. Use OpenBolt to automate tasks that you perform on an as-needed basis or as part of a greater orchestration workflow. For example, you can use OpenBolt to patch and update systems, troubleshoot servers, deploy applications, or stop and restart services. OpenBolt can be installed on your local workstation and connects directly to remote targets with SSH or WinRM, so you are not required to install any agent software.

OpenBolt is a community implementation of Puppet Bolt.

In the other systems

The newest version among them is 5.6.0, as upstream numbers it.

SystemPortVersionVulnerabilitiesStatusMaintainerLast update
DragonFlysysutils/rubygem-openbolt5.6.0 newestnone known-[email protected]-
FreeBSDsysutils/rubygem-openbolt5.6.0_1 newestnone known-[email protected]2026-10-04
HardenedBSDsysutils/rubygem-openbolt5.6.0_1 newestno data-[email protected]-
GhostBSDsysutils/rubygem-openbolt5.6.0_1 newestno data-[email protected]-

Version history 1

  1. 5.6.0

Upstream's version as each commit to the port's Makefile set it, or as this site first saw it in the system's packages; the tree's own revisions are not versions here.

Install

Binary package:

pkg install rubygem-openbolt

From DPorts:

cd /usr/dports/sysutils/rubygem-openbolt && make install clean

Dependency graph

Ports that need it on the left, what it needs to run on the right; at most 8 of each. "Dependencies" below lists them all.

Dependencies

Run dependencies 26

No port depends on this one.

Configuration

No options to configure.

Service scripts
none

Message after installing

This port depends on security/rubygem-net-ssh which has stricter defaults that
OpenSSH: when using strict host key checking, security/rubygem-net-ssh will
refuse the connexion if both the remote host name and IP address are not on the
same line of a known_host file.

security/rubygem-net-ssh added support for disabling strict host key checking
in version 5.2.0, however this setting is still enabled by default because
upstream OpenSSH has it enabled by default.  However, FreeBSD ships with a
modified version of OpenSSH where strict host key checking is disabled by
default.  As a result:
  - When adding an entry for a new host, only the host name is added in the
    known_host file;
  - The absence of CheckHostIP in the SSH configuration means the feature is
    disabled while such absence is generally the indication of the feature
    being enabled.

As a consequence, host key verification may need additional work:
  - When using security/rubygem-net-ssh < 5.2.0, either:
      - Disable host key checking totally (--no-host-key-check parameter of the
        bolt command);
      - Update your remote host entries in the known_hosts file to use the
	format:
        <host-name>,<IP address> <key-type> <key>
  - When using security/rubygem-net-ssh >= 5.2.0
      - Add "CheckHostIP no" to your SSH client configuration file
        (/etc/ssh/ssh_config or ~/.ssh/config).

Some future version of security/rubygem-net-ssh should drop strict host key
checking entirely, for more details, see:
https://github.com/net-ssh/net-ssh/pull/663