Result for 4D23216ED7CD1C37AEEEE7F9709F5D85B1736FC4

Query result

Key Value
FileNamex11vnc.spec
FileSize14864
MD55B46B1CF39FF8FE5EA9F9A8C737781E7
SHA-14D23216ED7CD1C37AEEEE7F9709F5D85B1736FC4
SHA-256131CDB2B17F430887CFD9898B8F42A22EFE31CEC76DB7F9FCA3E600AC113430B
SSDEEP384:j4aBjwWhJ1jrCbriXPUcoJlBg+6PO0fBH6vXlWy:jZNwKJVCXi6y+8fgX
TLSHT1166219F363853271A38206E2577E2261E33E84FE33441115B9EC815D6B5D5BAA3BB2F1
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
MD5EF46039ABBB89B974A83D62FA8F8A918
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.2
PackageVersion0.9.16
SHA-1ADB826A968C6746F41106C27C28623FDB6352CB4
SHA-25684E5ACA97E9D18EC08E5F2B0519AB22CCAD6380C7759B616995697B886ABE497