Result for 120A4592561C9FA920336245A311C77DABFF0889

Query result

Key Value
FileNamex11vnc.spec
FileSize14934
MD583058FB04FCD2B6B2114F45F7B7737E8
SHA-1120A4592561C9FA920336245A311C77DABFF0889
SHA-256B3E565CB87D5C3E8F4FF6B054A7A16F77D49CE29CEA9F56B1696D8B31D860BF0
SSDEEP384:j4NBjwWhJ1SYCbdiXPUcoJlBg+6PO0fBH6vXlWy:jcNwKJnCBi6y+8fgX
TLSHT192621AF363853271A38206E2577E2261E33E84FE33440115B9EC815D6B5D5BAA3BB2F1
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
MD5FD0312E824010F7755705A794A4F94AE
PackageArchi586
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.47
PackageVersion0.9.16
SHA-1C60FFF00A4C91EDBC0F4FE7D2DD3005357422E14
SHA-25695B914159B1EB75AB6DAD473D4A0A628C49F19DFD580CCE6AD1753CCA3298A2E