Result for 0AE482166E9942489FD024D584B1D5A61120F782

Query result

Key Value
FileName./usr/bin/x11vnc
FileSize1661856
MD58E2AC131E3D77CFBC73B97E1F6C2330B
SHA-10AE482166E9942489FD024D584B1D5A61120F782
SHA-2568E2042102337684194AFEF30D163D7F15E118867D2B53F2F244AABEA1EBEADC5
SSDEEP49152:IIx5SEU1vHe9iJGsLOPoDz8dFcelVZWta96O:IIphDsLgoD
TLSHT175758E02B35525BCC561C070965F92A26B75F0AB5334B97F348C92383F56B3853BEAE2
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD573627A75F6A948F67470AEC1DBA227CC
PackageArchx86_64
PackageDescriptionx11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows. For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop. The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamex11vnc
PackageReleasebp154.1.48
PackageVersion0.9.16
SHA-1969D15BD49204A6EF06357694C40E6EF761B10AC
SHA-25690C87CCC7F105C2652065FFFEE5939B4C0BF740A902745F4EAF23D2270572150