Result for BA9A358EC7CA343050E371685C1E33455D9322D6

Query result

Key Value
FileNamex11vnc.spec
FileSize14939
MD56D63709FCE617D8C90EEDE63890C76BE
SHA-1BA9A358EC7CA343050E371685C1E33455D9322D6
SHA-256BA086377CFD55A15AEFD6C9B82C7B030D8EEA54AB132BAE85956CD0D2A752FB6
SSDEEP384:j4IBjwWhJ1SYCbdiXPUcoJlBg+6PO0fBH6vXlWy:jHNwKJnCBi6y+8fgX
TLSHT131621AF363853271A38206E2577E2261E33E84FE33440115B9EC815D6B5D5BAA3BB2F1
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
MD55AD19DD78DC6CB2B0FB5BAB891EB49C4
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
PackageReleaselp153.3.3
PackageVersion0.9.16
SHA-1D5ACDAB5A81587F7E648489CB5E56A39E69FA673
SHA-25632C83298CB4D2EF48A3C6FF0024DF29D8635D91EEE944ED1A0F601ED57DF971B