Result for 5C72F490BBC4FE83E3AE9B74790E752086821809

Query result

Key Value
FileNamex11vnc.spec
FileSize14933
MD582F24764CA8C376A6729A2DBD08B31D0
SHA-15C72F490BBC4FE83E3AE9B74790E752086821809
SHA-2564A9701E820BC3EB09BD0B57BA19B752A3724DF02DE66D3089EC0FD63F76717CA
SSDEEP384:j4LBjwWhJ1SYCbdiXPUcoJlBg+6PO0fBH6vXlWy:jQNwKJnCBi6y+8fgX
TLSHT119621AF363853271A38206E2577E2261E33E84FE33440115B9EC815D6B5D5BAA3BB2F1
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
MD54A47069BDF342B5D988103C3AE35F617
PackageArchaarch64_ilp32
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
PackageRelease2.2
PackageVersion0.9.16
SHA-1C0EB26C435BB03765DC92656E5A4F21F1F067C65
SHA-256943BCE6EA555D0C2B9A2065625335A920F45711FBFE69BD68435AFF10251542C