| Key | Value |
|---|---|
| CRC32 | F30E63DD |
| FileName | ./usr/share/doc/packages/x11vnc/examples/dtVncPopup |
| FileSize | 3014 |
| MD5 | 9C3749C9A2CAF136500B1DECD875D63A |
| OpSystemCode | {'MfgCode': '1006', 'OpSystemCode': '362', 'OpSystemName': 'TBD', 'OpSystemVersion': 'none'} |
| ProductCode | {'ApplicationType': 'Operating System', 'Language': 'English', 'MfgCode': '2194', 'OpSystemCode': '51', 'ProductCode': '15799', 'ProductName': 'Red Hat Enterprise Linux Source Disc 1 of 1', 'ProductVersion': '5'} |
| RDS:package_id | 15799 |
| SHA-1 | 1FFF8F0855B58ABCB9E3B69C861FF174FA575135 |
| SHA-256 | A6E455F01B1477B547B4B68C6B5A632DA806DCFF24DB200611AC4FC60FB13434 |
| SSDEEP | 48:G50z6Gn10SnM8tbSdLQSslckhJ/Za5LDNwa6foTGeZ8qiMGiZbDKU2VRqP1A:1X1pn9WtsOkhC5VwaeyGiZ3GRSK |
| SpecialCode | |
| TLSH | T1C55196C573A967310F1345122D4E73E5A721114A3BAD3F12B6EDC15813A93B4D3E52CB |
| db | nsrl_legacy |
| insert-timestamp | 1648550239.2681513 |
| source | RDS_2022.03.1_legacy.db |
| hashlookup:parent-total | 20 |
| hashlookup:trust | 100 |
The searched file hash is included in 20 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| MD5 | 1DC3F6CBA537608B45FFA2C8357C0031 |
| PackageArch | i586 |
| PackageDescription | x11vnc 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. |
| PackageName | x11vnc |
| PackageRelease | 3.47 |
| PackageVersion | 0.9.16 |
| SHA-1 | 0C428C15537603209FF5B83BFAE7F1EE11DD9355 |
| SHA-256 | DFC0CCD5C7ED2099C0934C644FA5E9765C8950E2171A35C3DDDC08A1F2F464D4 |
| Key | Value |
|---|---|
| MD5 | B37C62298F204F9D9472D7DBE63FB176 |
| PackageArch | x86_64 |
| PackageDescription | x11vnc 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. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | x11vnc |
| PackageRelease | bp153.1.13 |
| PackageVersion | 0.9.16 |
| SHA-1 | 18217A11BC2E5B382135A455A72FC8C572FF3EC8 |
| SHA-256 | 194075ED4B52E30C92141C92B853AD289258C9D907F56A82D327888F8AF560A3 |
| Key | Value |
|---|---|
| MD5 | A077A38C5D8432CD1D31FFF1C241D089 |
| PackageArch | s390x |
| PackageDescription | x11vnc 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. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | x11vnc |
| PackageRelease | bp156.3.8 |
| PackageVersion | 0.9.16 |
| SHA-1 | 342ABC33E45CAE7714C724C9EB7F3EC97201D116 |
| SHA-256 | F528ED111BC37E9D41EE64119571B822C97120C58A5DBDB52EFCA3A600F09D65 |
| Key | Value |
|---|---|
| MD5 | 8401224B84F8BBE9AAF416F47468F268 |
| PackageArch | i586 |
| PackageDescription | x11vnc 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. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | x11vnc |
| PackageRelease | 2.9 |
| PackageVersion | 0.9.16 |
| SHA-1 | 3D06FC4C3228AE2D4C1B0E265AC9471DBF38C722 |
| SHA-256 | E5B7FBB47A1431D2C1A6F90F655E76855B5523E999206A205A53AF652CD830CA |
| Key | Value |
|---|---|
| MD5 | F6F0C5EFE04DB5539CA1529B2985EB0A |
| PackageArch | x86_64 |
| PackageDescription | x11vnc 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. |
| PackageName | x11vnc |
| PackageRelease | lp152.3.3 |
| PackageVersion | 0.9.16 |
| SHA-1 | 484A4E1D2B2E4F70204C2B4CADB833018AFF01FE |
| SHA-256 | BC04CC950130BAABAD409688DCFA9537D20EA96B8823B99852DE0D203AFF4EAB |
| Key | Value |
|---|---|
| MD5 | 865E5A1D89FE232E59476A41FB3D8E23 |
| PackageArch | x86_64 |
| PackageDescription | x11vnc 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. |
| PackageName | x11vnc |
| PackageRelease | lp153.3.3 |
| PackageVersion | 0.9.16 |
| SHA-1 | 4864EF6685CFEB0225131B32DA404C023509CF8F |
| SHA-256 | 28871E91A7CA22D39EC77F1C3C04BC2D74830100FB754640EF15BDFE3B825C7C |
| Key | Value |
|---|---|
| MD5 | 24D94D6179AB611900005DD7D113D5FF |
| PackageArch | x86_64 |
| PackageDescription | x11vnc 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. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | x11vnc |
| PackageRelease | 2.9 |
| PackageVersion | 0.9.16 |
| SHA-1 | 4F3BA8F6EE0EBB4DD7A5F0EE598814145ADE76CD |
| SHA-256 | A0C70373467CFE5F2708D2CE98158285DA7ACD7D0F9136875DFD3D998880468E |
| Key | Value |
|---|---|
| MD5 | 8407A99CE11ADF8698D9AC764B762C33 |
| PackageArch | x86_64 |
| PackageDescription | x11vnc 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. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | x11vnc |
| PackageRelease | lp151.2.20 |
| PackageVersion | 0.9.13 |
| SHA-1 | 673917C3CB568DE7EFB2C5AB436C37D873EF3BE9 |
| SHA-256 | 53B28B7A0C4DAB108C05B606497052F52DADEECDD1BEB412C2015E0FE9C9BBC7 |
| Key | Value |
|---|---|
| MD5 | 7F4E704D8AD9EA7299912C4A60611BD0 |
| PackageArch | x86_64 |
| PackageDescription | x11vnc 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. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | x11vnc |
| PackageRelease | lp152.3.31 |
| PackageVersion | 0.9.13 |
| SHA-1 | 8662CCCE86896204BE7DFAD53D0357AB0A79E502 |
| SHA-256 | 5B19D7043A7F309FF94DF6BCA9557E4F7F32619414EE6247D89F0582C0516161 |
| Key | Value |
|---|---|
| MD5 | CA02FDDDCE17EF00C4A98D14F29F1CA9 |
| PackageArch | x86_64 |
| PackageDescription | x11vnc 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. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | x11vnc |
| PackageRelease | lp150.1.20 |
| PackageVersion | 0.9.13 |
| SHA-1 | 8CC6F10DEE3FA5D02B777906E6FF162B6ABDBD76 |
| SHA-256 | 8A5EF07EB3046FF5D35939F140B93F6DD3002FDE325BE269D1DCE6D29075468E |