Result for 9D497D61D26754527CF28255CCAFE86D21678A80

Query result

Key Value
FileNamex11vnc.spec
FileSize14933
MD54316AD33FAB7E3753C3571D12AC53D6C
SHA-19D497D61D26754527CF28255CCAFE86D21678A80
SHA-256636F5EF8F1414329AB834411E770698AD5898AA07103EE9EEBA8911147186333
SSDEEP384:j4CBjwWhJ1SYCbdiXPUcoJlBg+6PO0fBH6vXlWy:jxNwKJnCBi6y+8fgX
TLSHT15C621AF363853271A38206E2577E2261E33E84FE33440115B9EC815D6B5D5BAA3BB2F1
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
MD595F05D4869096DF8F491DDB554428936
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.7
PackageVersion0.9.16
SHA-1D09EE0DA220949530E72D59CF474B84B36417A5F
SHA-256CB79BE4A35C0E4702C12D41045DB5B139E35C56E53A60986A1C022124F332A6F