Result for 9921F8009E723BE75A265ED6114AC5740489CC6C

Query result

Key Value
FileNamex11vnc.spec
FileSize14939
MD58235652B1BA9C7380C33D4754700D2B2
SHA-19921F8009E723BE75A265ED6114AC5740489CC6C
SHA-25663EAAC1A2DB67D50FE16EB8FD81673E50DE4F47BA115E3DB924613DFA0F6EB07
SSDEEP384:j4FBjwWhJ1SYCbdiXPUcoJlBg+6PO0fBH6vXlWy:jCNwKJnCBi6y+8fgX
TLSHT1E1621AF363853271A38206E2577E2261E33E84FE33440115B9EC815D6B5D5BAA3BB2F1
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
MD5132647055C18F6CA977D832852CE1F6E
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
PackageReleaselp152.3.3
PackageVersion0.9.16
SHA-13CF4271433463AB356E04CF1F9512B574CA0605C
SHA-256CA745869EF2A7A75432EF07627B1847CE8EA314A7C53967E1BF5C2AF2F93A8AE