Result for EAAC5E915F0AE165B8CD1D675512EE2225B60D71

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize19824
MD5A744E39A5EA45E58495E7F6E0F35FD6D
SHA-1EAAC5E915F0AE165B8CD1D675512EE2225B60D71
SHA-25674430D4488B0658C6D9831F36447C83333922626D7D98557B60F652B48A32B7B
SSDEEP384:2PAS6BCOICivZFfYAQnutfoeVIQkFMgzhAiz:LS6oJhvZFfYpQfoeCWyai
TLSHT17292D65BEFC98F71C8C59A7284A706312A3356F48A14A32B0650FBF92E517DC4F0B758
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
MD536A0E2A374F54F4859521CE81CFDC936
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.el5
PackageVersion2.5.12
SHA-10FE1F0A0DD19897A3F226B0DBA2AEFD49129EA48
SHA-2563D34F7B380B1DA115C8127FB3C326CE25A3CFAFFECC015AD392803EC5F2FB120