Result for A1791FE74C26F1C07E64B33B86050E6EFBE3168D

Query result

Key Value
FileNamex11vnc.spec
FileSize14933
MD51126F8A19720C7D1A3D5EA1E0F4CA155
SHA-1A1791FE74C26F1C07E64B33B86050E6EFBE3168D
SHA-256A55C93EA9AE8DECB5002AFA0A8730D12559F8EDE7C07DD04CF037D214B814CD6
SSDEEP384:j4sBjwWhJ1SYCbdiXPUcoJlBg+6PO0fBH6vXlWy:jfNwKJnCBi6y+8fgX
TLSHT17B621AF363853271A38206E2577E2261E33E84FE33440115B9EC815D6B5D5BAA3BB2F1
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
MD56F5E0C433C02AFBB7057A958F6B70B48
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
PackageRelease2.9
PackageVersion0.9.16
SHA-11FA3BCA886449E85B2CB2D4AE8CF858E70BFA69F
SHA-256796B3D9A1F23F859F1A7025CFA2C51D955EBB1FF1C5BF7D25AB3767D8782C2AD