Result for CA2C7CBC8CDAB1E5B0B3A4A96DB0E48E19223C26

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize19436
MD5623B17C651C1E573EEEFBA0E99F75E3D
SHA-1CA2C7CBC8CDAB1E5B0B3A4A96DB0E48E19223C26
SHA-25691793CE39708593FFA893AFC94F82D2DDD4AE450E0E687597FEC6CD085637B43
SSDEEP384:f/knS2OXCivXqm2+IXxoMUJCU7Za7G5k/HSj7E5aU+8r+xlRpZS1i:EnS2OhvXqm2+IBjU0CaC2SHE5aU+86x+
TLSHT1D0920A64FEDACE72E5D32D3801738B5162204FC1CE47ED87712C6ABD18922ED5687761
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
MD53FC8B560CA8FE117F21857502AC8D1BD
PackageArchi686
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
PackageRelease20.1
PackageVersion2.4.0
SHA-114897EFDB15D320FBF2C07FA3BC90043CAD4FA2E
SHA-2560CF823061CCFF6832A632F58F452E718FC3FEAD0DFFBDCFD5FAA78A7FC65B197