macOS
brew install qcalocal Homebrew formula metadata
sudo port install qcaMacPorts ports tree · devel/qca/Portfile · Quelle: api.github.com
brew / Rang 4692
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für qca in AI-Agent-Workflows.
Installation
brew install qcalocal Homebrew formula metadata
sudo port install qcaMacPorts ports tree · devel/qca/Portfile · Quelle: api.github.com
sudo apk add qcaAlpine Linux edge package indexes · qca · Quelle: dl-cdn.alpinelinux.org
sudo dnf install qca-qt5Fedora Rawhide package metadata · qca-qt5 · Quelle: dl.fedoraproject.org
sudo pacman -S qca-qt5Arch Linux sync databases · qca-qt5 · Quelle: geo.mirror.pkgbuild.com
Überblick
Qt Cryptographic Architecture (QCA)
Verlauf
QCA is KDE's cross-platform cryptographic abstraction for Qt applications, exposing a consistent API while loading cryptographic implementations through providers.
QCA, the Qt Cryptographic Architecture, dates to the early Qt 3 and Qt 4 era; official source headers carry Justin Karneges copyright beginning in 2003 and Brad Hards contributions beginning in 2004.
Inspired by the Java Cryptography Architecture, QCA introduced a cross-platform Qt-style API separated from concrete implementations through dynamically selected providers.
QCA's adoption has centered on Qt and KDE applications that need TLS, certificates, SASL, OpenPGP, CMS, smart-card, hashing, and encryption facilities while preserving Qt types and conventions.
The input records packages in Homebrew, Alpine Linux, Fedora, Arch Linux, and MacPorts. Distribution naming commonly reflects the supported Qt generation because QCA is primarily consumed as a runtime or development library.
Applications include QtCrypto, initialize QCA for provider-backed operations, link against the QCA library, and test required algorithms with QCA::isSupported(). Provider plugins normally reside in Qt's plugins/crypto directory.
QCA lets package maintainers separate a stable Qt-facing API from replaceable cryptographic provider plugins. That architecture permits backend changes without recompiling every client application, while making provider availability an important runtime packaging concern.
Sicherheitslage
Für qca wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
mozcerts-qt6 | cli | globales Executable | |
qcatool-qt6 | cli | globales Executable |
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.
Installationsmetadaten
| Paketschlüssel | brew:qca |
|---|---|
| Version | 2.3.12 |
| Paketmanager | Homebrew |
| Paketmanager-Seite | https://formulae.brew.sh/formula/qca |
| Homepage | https://userbase.kde.org/QCA |
| Upstream-Dokumentation | https://userbase.kde.org/QCA |
| Lizenz | LGPL-2.1-or-later |
| Quellarchiv | https://download.kde.org/stable/qca/2.3.12/qca-2.3.12.tar.xz |
| Zuletzt aktualisiert | 2026-10-08T15:34:20-04:00 |
| Pulse | updated |
| Abhängigkeiten | botan, ca-certificates, gnupg, libgcrypt, nspr, nss, openssl@4, pkcs11-helper, qt5compat, qtbase |
| Build-Abhängigkeiten | cmake, pkgconf |
| Von macOS bereitgestellte Bibliotheken | cyrus-sasl |
| Bottle | verfügbar (auf arm64_golden_gate, arm64_linux, arm64_sequoia, arm64_tahoe, x86_64_linux) |
| Homebrew post-install | nicht definiert |
| Dienst | keiner deklariert |
Registry-Fakten
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | qca |
| Version Scheme | 0 |
| Revision | 1 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
Source-Datenbank-Treffer
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
libqca-qt5 2.3.10-r0
Qt cryptographic architecture
sudo apk add libqca-qt5libqca-qt6 2.3.10-r0
Qt cryptographic architecture
sudo apk add libqca-qt6qca 2.3.10-r0
Qt cryptographic architecture
sudo apk add qcaqca-dev 2.3.10-r0
Qt cryptographic architecture (development files)
sudo apk add qca-devqca-doc 2.3.10-r0
Qt cryptographic architecture (documentation)
sudo apk add qca-docqca-qt6-dev 2.3.10-r0
Qt cryptographic architecture
sudo apk add qca-qt6-devqca-qt5 2.3.12-1.fc46
Qt5 Cryptographic Architecture
sudo dnf install qca-qt5qca-qt5-cyrus-sasl 2.3.12-1.fc46
Cyrus-SASL plugin for the Qt5 Cryptographic Architecture
sudo dnf install qca-qt5-cyrus-saslqca-qt5-devel 2.3.12-1.fc46
Qt5 Cryptographic Architecture development files
sudo dnf install qca-qt5-develqca-qt5-gcrypt 2.3.12-1.fc46
Gcrypt plugin for the Qt5 Cryptographic Architecture
sudo dnf install qca-qt5-gcryptqca-qt5-gnupg 2.3.12-1.fc46
Gnupg plugin for the Qt Cryptographic Architecture
sudo dnf install qca-qt5-gnupgqca-qt5-logger 2.3.12-1.fc46
Logger plugin for the Qt5 Cryptographic Architecture
sudo dnf install qca-qt5-loggerqca-qt5-nss 2.3.12-1.fc46
Nss plugin for the Qt5 Cryptographic Architecture
sudo dnf install qca-qt5-nssqca-qt5-ossl 2.3.12-1.fc46
Openssl plugin for the Qt5 Cryptographic Architecture
sudo dnf install qca-qt5-osslqca-qt5-pkcs11 2.3.12-1.fc46
Pkcs11 plugin for the Qt5 Cryptographic Architecture
sudo dnf install qca-qt5-pkcs11qca-qt5-softstore 2.3.12-1.fc46
Pkcs11 plugin for the Qt5 Cryptographic Architecture
sudo dnf install qca-qt5-softstoreQuellspur
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
View the package source record on GitHub.