Result for 88D842C524EE398E18F190B6EE12AEBBB7D64FDE

Query result

Key Value
FileNamex11vnc.spec
FileSize14864
MD5DA6F6D7909A225D4D5044C245064B4A1
SHA-188D842C524EE398E18F190B6EE12AEBBB7D64FDE
SHA-2561113618A1776C037D3C1CD576F7E69142D63E82BC4DEEE71943D39E6CD7743F1
SSDEEP384:j4nBjwWhJ1jrCbriXPUcoJlBg+6PO0fBH6vXlWy:jENwKJVCXi6y+8fgX
TLSHT1E86219F363853271A38206E2577E2261E33E84FE33441115B9EC815D6B5D5BAA3BB2F1
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
MD55B783D0DED424F207AD1D0E328E0C3AE
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.
PackageNamex11vnc
PackageRelease3.3
PackageVersion0.9.16
SHA-1046D1AB7FD6D4E9C49530F7D2FE9777AC473F9F5
SHA-256C173C6C1B433A5517955F2344184A91280FE27729807F8D6513CCAD0E12F5324