Result for 7EC67A1316EEA168A134D9EFD1649124C6B596C3

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize24848
MD5DD0694A80BB7A04BCFE22D4CA36F7F37
SHA-17EC67A1316EEA168A134D9EFD1649124C6B596C3
SHA-2566F66CC853A4249C8BA4487BDA6C0B7CAA97FA4FF6B34EC9E4713C2E1815B45A2
SSDEEP384:B0xpO8CivxAcE6mfvNYzbMtkgtY5yzeiCFk4flAyob5H05tO:49hvxAcEztkgtGy5sqk
TLSHT176B2073BF6D08771D4D179389CAB4AA29633A1F48B04620FA366BB3D1E107CC8F4A754
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
MD54D06388D004EB6C9A43511AC35C2D2BC
PackageArchx86_64
PackageDescription OMG defined CORBA Naming Service to provide a basic service location mechanism for CORBA systems. CosNaming manages a hierarchy of name-to-object-reference mappings. Anything, but typically the server process hosting an object, may bind an object reference with a name in the Naming Service by providing the name and object reference. Interested parties (typically clients) can then use the Naming Service to resolve a name to an object reference. More recently, CORBA Naming Service was subsumed/extended by the CORBA Interoperable Naming Service, a.k.a. INS. INS inherits all the functionality from the original Naming Service specification in addition to addressing some its shortcomings. In particular, INS defines a standard way for clients and servers to locate the Naming Service itself. It also allows the ORB to be administratively configured for bootstrapping to services not set up with the orb at install time.
PackageNametao-cosnaming
PackageRelease83.1
PackageVersion2.5.12
SHA-13AF166AD0C43D48B64B567E928118D19FA9C5BBF
SHA-256D6223DE4C84A25E3E9929CB57F89CC4E1D7BF8371FB75BCB94F448353619525E