Result for 8C21101F42CC23DFF589CC03D07900AC87504DA3

Query result

Key Value
FileNamex11vnc.spec
FileSize14939
MD58C4B44BB7CA2430F525E48417B037FCB
SHA-18C21101F42CC23DFF589CC03D07900AC87504DA3
SHA-256DEF246E01A6A0C3F9546378F145D2B0A10AA72A6A87AD342007196820650B8A2
SSDEEP384:j4oBjwWhJ1SYCbdiXPUcoJlBg+6PO0fBH6vXlWy:jnNwKJnCBi6y+8fgX
TLSHT17F621AF363853271A38206E2577E2261E33E84FE33440115B9EC815D6B5D5BAA3BB2F1
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
MD5B3251CCD549354E1CBCD5693D189E2DC
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
PackageReleaselp151.3.1
PackageVersion0.9.16
SHA-1E6F41A0A81F08E1BCAD6A4D53E10929E5ADB2478
SHA-256F38661ABB2962C8E2E20CB71ABCA70AFA10F359632ADEF28DCF3E58E39261C9D