Automic VaultAutomic Vault

brew

xmlsectool mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install xmlsectool

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Check schema validity and signature of an XML document

Befehle und Aliase

  • xmlsectool

Verlauf

Projektgeschichte und Nutzung

xmlsectool is a Shibboleth Java command-line tool for downloading XML, checking well-formedness and schema validity, verifying XML signatures, and creating enveloped XML signatures. Its main cultural home is SAML metadata operations rather than generic XML editing.

Projektgeschichte

The tool grew inside the Shibboleth ecosystem as a deployer utility for XML security work. Its documentation is organized by major supported series, with V3 now archived and V4 identified as the current supported line.

Version 2.0.0 was announced in June 2016 as a new stable release based on the Shibboleth v3 Identity Provider software stack. That release was intended as a drop-in replacement for most 1.2.0 users, while moving the tool to Java 7 or later, making SHA-256 the default signing digest, and blacklisting SHA-1 by default.

Version 4.0.0 was released on 2025-04-16. The V4 documentation states that V4 is the only supported release line, requires Java 17, removes options deprecated in V3, and adds a --version option.

Adoptionsgeschichte

xmlsectool's adoption follows Shibboleth and SAML federation operations: operators need to validate and sign metadata, verify downloaded metadata, and sometimes use token-backed signing credentials. Its presence in the Shibboleth announcement channel and deployer documentation shows it is maintained as operational security tooling, not just an example program.

Wie es verwendet wird

Typical use cases include validating SAML metadata schemas, verifying XML signatures before trusting metadata, signing SAML 2.0 metadata with explicit reference ID handling, selecting digest and signature algorithms, and using PKCS#11-backed credentials through Java security providers.

Warum Paket-Nerds sich dafür interessieren

xmlsectool is the kind of security package that package nerds care about because it turns a hard-to-compose Java XML security stack into one auditable command. The package boundary is useful: a CLI can be pinned, upgraded, scripted, and documented independently of an identity provider deployment.

Zeitleiste

  • 2016-06-28: Shibboleth announced xmlsectool 2.0.0 and the end of 1.x support.
  • 2025-04-16: xmlsectool 4.0.0 was released as the current stable release.
  • 2025-04-16: Security maintenance for xmlsectool 3.0.0 and earlier ceased, making V4 the only supported release.

Related projects

  • Related projects and technologies include Shibboleth Identity Provider, Shibboleth Service Provider, SAML 2.0 metadata, XML Signature, Apache Santuario-style XML security libraries, Java security providers, and PKCS#11 hardware tokens.

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 1 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhä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
xmlsectoolcliglobales 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-08
Manager-Version4.0.0
Manager aktualisiert2026-06-22
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://wiki.shibboleth.net/confluence/display/XSTJ3/xmlsectool+V3+Home

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:xmlsectool
Version4.0.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/xmlsectool
Homepagehttps://wiki.shibboleth.net/confluence/display/XSTJ3/xmlsectool+V3+Home
Repositoryhttps://git.shibboleth.net/git/xmlsectool
Upstream-Dokumentationhttps://shibboleth.atlassian.net/wiki/spaces/XSTJ4/overview
LizenzApache-2.0
Quellarchivhttps://shibboleth.net/downloads/tools/xmlsectool/4.0.0/xmlsectool-4.0.0-bin.zip
Zuletzt aktualisiert2026-06-22T14:06:42-07:00
Pulseupdated
Abhängigkeitenopenjdk
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namexmlsectool
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • 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