Automic VaultAutomic Vault

brew

tiger-vnc mit Homebrew, scoop, winget installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install tiger-vnc

local Homebrew formula metadata

Windows

Scoopverifiziert · 92%
scoop install extras/vncviewer

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

Windows Package Managerverifiziert · 92%
winget install --id RealVNC.VNCViewer -e

Windows Package Manager source index · RealVNC.VNCViewer · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

High-performance, platform-neutral implementation of VNC

Befehle und Aliase

  • vncconfig
  • vncpasswd
  • vncsession
  • vncviewer
  • x0vncserver

Verlauf

Projektgeschichte und Nutzung

TigerVNC is a high-performance, multi-platform implementation of Virtual Network Computing. Its README explains VNC as a remote display system that lets a user view and interact with a desktop environment running on another computer over a network.

Projektgeschichte

The official README gives TigerVNC's origin story directly: it is based on the RealVNC 4 and X.org code bases, started as a next-generation development effort for TightVNC on Unix and Linux, and split from TightVNC in early 2009 so TightVNC could focus on Windows platforms.

TigerVNC's technical identity is also defined by performance. The README says it supports a variant of Tight encoding accelerated by the libjpeg-turbo JPEG codec, which explains why the project became a frequent package choice for users who wanted an open VNC client/server stack with better speed than older VNC implementations.

The project includes both common cross-platform pieces and platform-specific tools. The README lists vncviewer on all platforms, winvnc on Windows, and Unix/Linux programs such as Xvnc, vncpasswd, vncconfig, x0vncserver, w0vncserver, and a systemd vncserver service.

Adoptionsgeschichte

TigerVNC's adoption follows the continuing need for remote graphical access to Unix and Linux desktops, lab machines, servers, and cross-platform GUI sessions. The official repository is maintained under the TigerVNC organization and shows a long-running C++ project with substantial stars, forks, releases, and active development.

In package-manager culture, TigerVNC is the kind of tool installed when SSH is not enough: developers, administrators, and researchers can add a VNC viewer or server from a package manager and connect to remote graphical environments without adopting a proprietary remote-desktop stack.

The Homebrew formula exposes the viewer and related command-line utilities on macOS, while Linux distributions commonly package both client and server pieces. This split packaging pattern is natural for VNC because some users only need a viewer and others need to host sessions.

Wie es verwendet wird

The vncviewer manual documents the classic client workflow: run vncviewer with a host and display number or port, use a .tigervnc configuration file, authenticate with a password, and open a window showing the remote desktop.

On Unix/Linux, TigerVNC is also used to create virtual X desktop sessions with Xvnc, manage VNC passwords with vncpasswd, configure a running server with vncconfig, and expose an existing X display through x0vncserver.

For package users, the practical pattern is simple: install the package, set or store a VNC password, start or connect to a server, and keep the rest of the workflow in shell scripts, service units, or desktop launchers.

Warum Paket-Nerds sich dafür interessieren

TigerVNC is significant because it packages a historically important remote-desktop protocol into reproducible open-source builds. It sits at the intersection of X11, remote access, compression, authentication, systemd services, and desktop packaging.

Its package details matter more than average: client-only versus server components, password-file locations, XDG configuration paths, FLTK viewer behavior, and platform support all affect whether a user can connect to a remote GUI from a freshly provisioned machine.

Zeitleiste

  • 1999-2008: README copyright acknowledgements trace inherited VNC, X Window System, TightVNC, and RealVNC lineage.
  • Early 2009: README says TigerVNC split from TightVNC so TightVNC could focus on Windows platforms.
  • 2014: GitHub repository for TigerVNC/tigervnc created.
  • 2020s: Official tags and repository metadata show continued 1.x releases and active maintenance.

Related projects

  • The README names RealVNC 4, X.org, TightVNC, and libjpeg-turbo as central lineage or supporting technology.
  • TigerVNC belongs to the broader VNC ecosystem of viewers, servers, X11 virtual framebuffers, and remote-desktop tooling.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für tiger-vnc wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 7 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 2 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
$XDG_CONFIG_HOME/tigervnc/default.tigervnc~/.config/tigervnc/default.tigervnc

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
$XDG_CONFIG_HOME/tigervnc/passwd~/.config/tigervnc/passwd

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
vncconfigcliglobales Executable
vncpasswdcliglobales Executable
vncsessioncliglobales Executable
vncviewercliglobales Executable
x0vncservercliglobales 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-Version1.16.2
Manager aktualisiert2026-05-11
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.16.2

https://github.com/TigerVNC/tigervnc

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:tiger-vnc
Version1.16.2
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/tiger-vnc
Homepagehttps://tigervnc.org/
Repositoryhttps://github.com/TigerVNC/tigervnc
Upstream-Dokumentationhttps://github.com/TigerVNC/tigervnc/wiki
LizenzGPL-2.0-or-later
Quellarchivhttps://github.com/TigerVNC/tigervnc/archive/refs/tags/v1.16.2.tar.gz
Zuletzt aktualisiert2026-05-11T18:07:38Z
Pulseupdated
Abhängigkeitenfltk@1.3, gettext, gmp, gnutls, jpeg-turbo, nettle, pixman
Build-Abhängigkeitencmake, gettext
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 Nametiger-vnc
Version Scheme0
Revision1
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Scoop92%

extras/vncviewer

scoop install extras/vncviewer
  • installed executable or alias match
  • Abgeglichen nach: Vncviewer
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/vncviewer.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1
winget92%

RealVNC.VNCViewer

winget install --id RealVNC.VNCViewer -e
  • installed executable or alias match
  • Abgeglichen nach: Vncviewer
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: RealVNC.VNCViewer from https://cdn.winget.microsoft.com/cache/source.msix

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 configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment