Result for DB6DF2A901AD5832EC7D0838DF671468A3B90977

Query result

Key Value
CRC32AC883C89
FileName./usr/share/doc/packages/x11vnc/examples/rx11vnc
FileSize3146
MD5052A5ADF4C020B624EAC03305C4934D4
OpSystemCode{'MfgCode': '1006', 'OpSystemCode': '362', 'OpSystemName': 'TBD', 'OpSystemVersion': 'none'}
ProductCode{'ApplicationType': 'software collection', 'Language': 'English', 'MfgCode': '369', 'OpSystemCode': '51', 'ProductCode': '15095', 'ProductName': 'LXFDVD158', 'ProductVersion': '2012'}
SHA-1DB6DF2A901AD5832EC7D0838DF671468A3B90977
SHA-256DEEBB7FD6B611E99F9ECB7D639783C3DC850AD0348EEE9543FE5E88148262260
SSDEEP96:4N43c+EmMQF554U5VeA90lMFj7Tqu9vz1C:4e3c+Z5uU5VWuFj79JxC
SpecialCode
TLSHT1E651B780F12963B02E7A0178144FC5CC3B6941D8DBFDEDA4785E3B5A632C9A7B1748DA
dbnsrl_modern_rds
insert-timestamp1647057864.4629977
sourceNSRL
tar:gnameroot
tar:unameroot
hashlookup:parent-total21
hashlookup:trust100

Network graph view

Parents (Total: 21)

The searched file hash is included in 21 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileNamehttp://archlinux.mirror.root.lu//pool//community//./x11vnc-1:0.9.16-4-x86_64.pkg.tar.zst
MD55471E71FC3C11C481A46B6ECD2946739
SHA-107AEF61799DA157CAF299A5C6372F8768911C841
SHA-25614F631FA2F622F25C74D558C67732C00DFB2B2A80DF92DA791CDF97D0B0D8221
SSDEEP12288:F1NOZZbJwBIXDBtuodsLQnOBlIjwBcv+2rroGYFrNCeybNRDjdKLbohOJ:FCJ9uoBYc22rronQ7DJAL
TLSHT140E42333BBD98A9B290F7307EF0610DA27FA7A50F48D524346F169C25F60489E4F96E0
Key Value
MD51DC3F6CBA537608B45FFA2C8357C0031
PackageArchi586
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
PackageRelease3.47
PackageVersion0.9.16
SHA-10C428C15537603209FF5B83BFAE7F1EE11DD9355
SHA-256DFC0CCD5C7ED2099C0934C644FA5E9765C8950E2171A35C3DDDC08A1F2F464D4
Key Value
MD5B37C62298F204F9D9472D7DBE63FB176
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
PackageReleasebp153.1.13
PackageVersion0.9.16
SHA-118217A11BC2E5B382135A455A72FC8C572FF3EC8
SHA-256194075ED4B52E30C92141C92B853AD289258C9D907F56A82D327888F8AF560A3
Key Value
MD5A077A38C5D8432CD1D31FFF1C241D089
PackageArchs390x
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
PackageReleasebp156.3.8
PackageVersion0.9.16
SHA-1342ABC33E45CAE7714C724C9EB7F3EC97201D116
SHA-256F528ED111BC37E9D41EE64119571B822C97120C58A5DBDB52EFCA3A600F09D65
Key Value
MD58401224B84F8BBE9AAF416F47468F268
PackageArchi586
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-13D06FC4C3228AE2D4C1B0E265AC9471DBF38C722
SHA-256E5B7FBB47A1431D2C1A6F90F655E76855B5523E999206A205A53AF652CD830CA
Key Value
MD5F6F0C5EFE04DB5539CA1529B2985EB0A
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-1484A4E1D2B2E4F70204C2B4CADB833018AFF01FE
SHA-256BC04CC950130BAABAD409688DCFA9537D20EA96B8823B99852DE0D203AFF4EAB
Key Value
MD5865E5A1D89FE232E59476A41FB3D8E23
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
PackageReleaselp153.3.3
PackageVersion0.9.16
SHA-14864EF6685CFEB0225131B32DA404C023509CF8F
SHA-25628871E91A7CA22D39EC77F1C3C04BC2D74830100FB754640EF15BDFE3B825C7C
Key Value
MD524D94D6179AB611900005DD7D113D5FF
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-14F3BA8F6EE0EBB4DD7A5F0EE598814145ADE76CD
SHA-256A0C70373467CFE5F2708D2CE98158285DA7ACD7D0F9136875DFD3D998880468E
Key Value
MD58407A99CE11ADF8698D9AC764B762C33
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
PackageReleaselp151.2.20
PackageVersion0.9.13
SHA-1673917C3CB568DE7EFB2C5AB436C37D873EF3BE9
SHA-25653B28B7A0C4DAB108C05B606497052F52DADEECDD1BEB412C2015E0FE9C9BBC7
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