Result for 7600F9DF3F60519A54371D0D996C3469406A55BE

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize20520
MD56A3A13F00D1E5298724FC3167BE4E129
SHA-17600F9DF3F60519A54371D0D996C3469406A55BE
SHA-256E95C55C0516C6D3339A7B9762D141220EBFB769E24FF049B4B7EF7E5488CFBD5
SSDEEP192:Gk+KywKWJWKOon6gjkVTtfcHGjTNTR+fiRvFxHNKw2SKiRTtCoUJAzLiNqeDq6v:WKxVOIiPfDTNl+fiRtb2Ji99PiNqo
TLSHT1F792E89FFBC54BF2E0868530887B06311AF399B8CE26635B5550FAFA245174C8F47B58
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
MD5874F65F5091BAAB1CB11685E308D1731
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
PackageRelease31.el5
PackageVersion2.5.0
SHA-100DDBFABF0DDBA08D89E3818762BE17E2D6BA0EF
SHA-256D8B8759195FFA4E2F895A0849A5E4C442AE51354263E92B50CA44D1AC6BD7DE1