Automic VaultAutomic Vault

brew

gmssl mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install gmssl

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Toolkit for Chinese national cryptographic standards

Befehle und Aliase

  • gmssl

Verlauf

Projektgeschichte und Nutzung

GmSSL is an open-source cryptographic toolkit developed by Peking University for Chinese commercial cryptography standards. It provides a gmssl command-line tool, a C library, protocol support, and language bindings around SM2, SM3, SM4, SM9, TLCP, TLS, and related algorithms.

Projektgeschichte

The public GitHub repository was created in 2014. The README describes GmSSL as a domestic commercial cryptography open-source library independently developed by Peking University, covering national cryptographic algorithms, standards, secure communication protocols, mainstream operating systems and processors, cryptographic keys, and cryptographic cards.

The 3.x series was a major rewrite. The README states that GmSSL 3 reduced memory needs and binary size, removed the OpenSSL-compatible API from the core, adopted CMake, targeted embedded environments, and added a separate OpenSSL compatibility layer for applications such as Nginx.

GmSSL releases show a 3.0.0 release in 2022, 3.1.x releases in 2023, and 3.2.0 in 2026. The README's changelog for 3.1.1 onward includes TLS 1.3 work, TLCP support, post-quantum algorithms, command-line options for cryptographic operations, performance improvements, and removal of broken algorithms such as RC4 and MD5.

Adoptionsgeschichte

GmSSL's adoption is tied to compliance and interoperability needs around Chinese national cryptographic standards. Its README emphasizes SM algorithms, TLCP, RFC 8998 TLS 1.3 cipher suites, hardware interfaces such as SDF and SKF, and language bindings for Java, PHP, Go, Python, Rust, and Node.js.

Homebrew packaging gives macOS and Unix-like developers a convenient way to test the gmssl CLI and library without building the full CMake project manually. The GitHub repository's large star and fork counts also indicate broader interest than a single-vendor compliance sample.

Wie es verwendet wird

Practitioners build GmSSL with CMake, install the gmssl command-line tool and libgmssl, and use it to exercise SM-family algorithms, certificate workflows, digital envelopes, TLS/TLCP protocol support, and benchmark tests.

Application developers use the C library or language bindings when they need Chinese commercial cryptography support in services, embedded systems, mobile platforms, or compatibility layers for existing OpenSSL-oriented software.

Warum Paket-Nerds sich dafür interessieren

GmSSL is package-significant because cryptographic standards support is hard to vendor casually. A package-managed build gives users a repeatable toolkit for SM2, SM3, SM4, SM9, TLCP, and TLS experiments without treating a security-sensitive C library as a one-off source checkout.

It also shows a common packaging tension in crypto: users want a familiar OpenSSL-like CLI surface, but the project deliberately changed APIs in GmSSL 3 and moved OpenSSL compatibility into a separate layer.

Zeitleiste

  • 2014: Public GitHub repository created.
  • 2018: GMBrowser v0.1 release published in the repository release stream.
  • 2022: GmSSL 3.0.0 released.
  • 2023: GmSSL 3.1.x releases published.
  • 2026: GmSSL 3.2.0 released.

Related projects

  • OpenSSL is related through the compatibility-layer discussion in the README.
  • GmSSL-Java, GmSSL-PHP, GmSSL-Go, GmSSL-Python, gmssl-rs, and GmSSL-Nodejs provide language bindings around the core library.
  • SoftSDF is a related software SDF module for development and testing.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • 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.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
gmsslcliglobales 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-25
Manager-Version3.2.0
Manager aktualisiert2026-06-21
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv3.2.0

https://github.com/guanzhi/GmSSL

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:gmssl
Version3.2.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/gmssl
Homepagehttps://github.com/guanzhi/GmSSL
Repositoryhttps://github.com/guanzhi/GmSSL
Upstream-Dokumentationhttps://github.com/guanzhi/GmSSL#readme
LizenzApache-2.0
Quellarchivhttps://github.com/guanzhi/GmSSL/archive/refs/tags/v3.2.0.tar.gz
Zuletzt aktualisiert2026-06-21T07:05:30Z
Pulseupdated
Build-Abhängigkeitencmake
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namegmssl
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment