Result for 141F321798523679BE6C2347F36712B82D0EFF6A

Query result

Key Value
FileName./usr/bin/x11vnc
FileSize1924192
MD54AF743C1D4D82967F78FDAF93B8BD68D
SHA-1141F321798523679BE6C2347F36712B82D0EFF6A
SHA-25646585B8BDD42521A391CFEE8322A2DA5089A410C2AF7CC2940CAC69278F8021E
SSDEEP49152:FDKOHFNdgJUgrtjyxWAEe+PVZby7muQ7Th04Tl6HWtaC6R:FDh8JUwve+PV/
TLSHT1A8959E02B35215BCC565C070975F92A26A74B0AA1331BD7F35CC96383F17A2953BEEE2
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
MD57F4E704D8AD9EA7299912C4A60611BD0
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.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamex11vnc
PackageReleaselp152.3.31
PackageVersion0.9.13
SHA-18662CCCE86896204BE7DFAD53D0357AB0A79E502
SHA-2565B19D7043A7F309FF94DF6BCA9557E4F7F32619414EE6247D89F0582C0516161