Result for AAE8653C5D706F24F9F8B06FE4C716C62354AC24

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize24648
MD5DD1BF1CB8E7347A826005CCF9060C3F4
SHA-1AAE8653C5D706F24F9F8B06FE4C716C62354AC24
SHA-2560026B1566F20BAC78673590F8BF243F9708926D5BE5F77829CBD8F111B7DB359
SSDEEP192:G+aLLMer5HqaLjVmc7M1asIE8oH+HP2uHupGfDmuzWZ06ipodD90J+xL5Sw:NAMer5HqaEc7mabfoQtHkoD9z76Io7b
TLSHT1CFB2B7EFFA899BB1C0C10930442B46632BB396FCD746F25F6020FB79A481648DE57B25
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
MD53CD36B7767259D8AD916C02F5DC729AA
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
PackageRelease143.1
PackageVersion3.0.6
SHA-110E6C3B8B3EFDEA2B455BA72A9602F0BA611D3D9
SHA-256D40D7964035C9FF2D647D86E588357D8B021D534C2ED5D4D6549944F15D13B39