brew

openssh mit Homebrew, apk, chocolatey, dnf, MacPorts, Nix, pacman, zypper, apt, scoop, winget installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für openssh in AI-Agent-Workflows.

Installationsbefehl Sicherheitshinweise

Agent-Sicherheit

Antwort zur Agent-Sicherheit

openssh provides remote login, key, and transfer tools with broad host access.

Credential-Zugriff

Reads SSH keys, agent sockets, known hosts, config, and forwarded credentials.

Änderungen an Remote-Zustand

Can execute commands and transfer files on remote hosts.

Publish-/Artefakt-Risiko

Can deploy files, change servers, and expose forwarded credentials.

Empfohlene Kontrolle

Gate remote command execution, scp/sftp writes, key generation, and agent forwarding.

Hinweise für Agent-Nutzung

Allow local key inspection; require approval before connecting to or mutating remote hosts.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install openssh

local Homebrew formula metadata

MacPortsverifiziert · 94%

sudo port install openssh

MacPorts ports tree · net/openssh/Portfile · Quelle: api.github.com

Linux

Alpine Linux apkverifiziert · 92%

sudo apk add openssh

Alpine Linux edge package indexes · openssh · Quelle: dl-cdn.alpinelinux.org

Fedora dnfverifiziert · 92%

sudo dnf install openssh

Fedora Rawhide package metadata · openssh · Quelle: dl.fedoraproject.org

Nixverifiziert · 92%

nix profile install nixpkgs#openssh

nixpkgs package indexes · openssh · Quelle: raw.githubusercontent.com

Arch Linux pacmanverifiziert · 92%

sudo pacman -S openssh

Arch Linux sync databases · openssh · Quelle: geo.mirror.pkgbuild.com

openSUSE zypperverifiziert · 92%

sudo zypper install openssh

openSUSE Tumbleweed package metadata · openssh · Quelle: download.opensuse.org

Debian aptverifiziert · 92%

sudo apt install openssh-client

Debian stable package indexes · openssh-client · Quelle: deb.debian.org

Windows

Chocolateyverifiziert · 92%

choco install openssh

Chocolatey community package catalog · openssh · Quelle: community.chocolatey.org

Scoopverifiziert · 92%

scoop install main/openssh

Scoop official bucket manifest trees · bucket/openssh.json · Quelle: api.github.com

Windows Package Managerverifiziert · 92%

winget install --id Syncplify.Server -e

Windows Package Manager source index · Syncplify.Server · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

OpenBSD freely-licensed SSH connectivity tools

Projektlinks

Befehle und Aliase

scp
sftp
slogin
ssh
ssh-add
ssh-agent
ssh-keygen
ssh-keyscan
sshd

Verlauf

Projektgeschichte und Nutzung

OpenSSH is the OpenBSD project's freely licensed implementation of the SSH protocol suite: remote login, remote command execution, file transfer, key management, agent forwarding, and server-side SSH access. The package includes `ssh`, `sshd`, `scp`, `sftp`, `ssh-keygen`, `ssh-agent`, `ssh-add`, and related tools.

Projektgeschichte

OpenSSH began in 1999 when OpenBSD developers forked Bjorn Gronvall's OSSH, itself derived from Tatu Ylonen's last sufficiently free ssh 1.2.12 release. The OpenSSH project history describes the goal as freeing SSH from license restrictions, cleaning up the code, and maintaining it under the OpenBSD security-audit culture.

The initial import landed on September 26, 1999, shortly before OpenBSD 2.6. The early team removed portability clutter, replaced problematic cryptographic and GPL components, repaired bugs, restored features, and added support for SSH 1.5 and later SSH 2. The OpenBSD manual credits Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos, Theo de Raadt, and Dug Song with creating OpenSSH from the original free ssh base.

OpenSSH's project goal was explicit: because telnet and rlogin are insecure, operating systems should ship SSH support. SSH 2 support became usable around May 4, 2000, solving the integrity and patent-era problems of SSH 1 and giving OpenSSH the protocol base that would become standard for secure administration.

Adoptionsgeschichte

OpenSSH became infrastructure software because it replaced insecure remote-login and file-transfer tools with a default, scriptable, auditable SSH suite. The portable release made the OpenBSD code usable on Linux, macOS, Cygwin, Solaris, AIX, HP-UX, and other Unix-like systems by adding compatibility layers, PAM/auditing hooks, and platform-specific sandboxing.

Package managers generally split OpenSSH into client and server packages or ship it in the operating-system base. Homebrew's `openssh` formula exists for users who want a packaged OpenSSH newer or different from the system copy, with dependencies such as libfido2 and OpenSSL for modern authentication and crypto support.

Wie es verwendet wird

Operators use OpenSSH for daily host access, jump hosts, port forwarding, remote command execution, Git-over-SSH, rsync transport, and automated deployments. Developers touch the package through keys, `~/.ssh/config`, known-host verification, `ssh-agent`, `scp`/`sftp`, and server configuration in `sshd_config`.

OpenSSH also functions as a security policy surface. Choices such as allowed key algorithms, FIDO/U2F support, host key rotation, agent forwarding, chrooting, and subsystem configuration are all exposed through a familiar command and config ecosystem.

Warum Paket-Nerds sich dafür interessieren

OpenSSH is one of the canonical examples of a package becoming part of the operating-system substrate. It is both an upstream security project and a downstream packaging problem: vendors patch it, split client/server binaries, coordinate crypto-library choices, and backport fixes because remote access breakage can lock administrators out of machines.

For package nerds, OpenSSH is also a portability case study. The upstream OpenBSD version stays small and tightly audited, while portable OpenSSH carries the compatibility code that lets one security-sensitive codebase work across many Unix variants.

Zeitleiste

1999: OpenBSD developers fork OSSH and import the code on September 26.
December 1, 1999: OpenBSD 2.6 ships with OpenSSH.
May 4, 2000: SSH 2 support is implemented sufficiently to be usable.
2017: OpenSSH 7.6 removes SSH 1 protocol support.
2026: Homebrew packages OpenSSH 10.3p1 in the `openssh` formula.

Related projects

OpenSSH descends from Tatu Ylonen's original SSH and Bjorn Gronvall's OSSH. It interacts with crypto libraries such as LibreSSL, OpenSSL, AWS-LC, and BoringSSL, and it overlaps operationally with file-transfer tools, bastion-host systems, VPNs, and configuration-management systems.

Quellen

Sicherheitslage

Risikostufe: blue

broad file, network, media, or database tool signal.

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

broad file, network, media, or database tool signal

Signale

text:ftp,ssh

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
Installiert mit 3 Laufzeitabhängigkeiten.
Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: ~/.ssh/config

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix: ~/.ssh/id_*~/.ssh/config

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit
`scp`	cli	globales Executable
`sftp`	cli	globales Executable
`slogin`	cli	globales Executable
`ssh`	cli	globales Executable
`ssh-add`	cli	globales Executable
`ssh-agent`	cli	globales Executable
`ssh-keygen`	cli	globales Executable
`ssh-keyscan`	cli	globales Executable
`sshd`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-10

Manager-Version10.4p1

Manager aktualisiert2026-07-06

lokale DatenOK

Upstreamnot checked

neueste erkannte Versionnicht erkannt

Paketschlüssel	brew:openssh
Version	10.4p1
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/openssh
Homepage	https://www.openssh.com/
Repository	https://anongit.mindrot.org/openssh.git
Upstream-Dokumentation	https://www.openssh.com/manual.html
Lizenz	SSH-OpenSSH
Quellarchiv	https://cdn.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-10.4p1.tar.gz
Zuletzt aktualisiert	2026-07-06T18:10:51Z
Pulse	updated
Abhängigkeiten	ldns, libfido2, openssl@3
Build-Abhängigkeiten	pkgconf
Von macOS bereitgestellte Bibliotheken	krb5, libedit, libxcrypt
Bottle	verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	openssh
Version Scheme	0
Revision	0
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	stable