Result for A20AD44C41474B72F89C0F8DDCD6E53FC29C85DA

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize13680
MD590D6BCCC72FEDC6BC8FD3B3D68E10084
SHA-1A20AD44C41474B72F89C0F8DDCD6E53FC29C85DA
SHA-25676401DE66F26E70DD4021C2B517DB3B546F06B7D604C90EDC20A3B205B7D76A2
SSDEEP192:G2Ie2r6OjpJnUCCisyfVHuSRa4oQYbRG5BVxBCqwq:R2r6ONJUCCisyfQSRpoQr5BV1
TLSHT13052C747FB80CB7ED4998370849B8A356333957CA750971B0A00E7B83D927AD0F57B99
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
MD59F60B74BA6F69239BC98BE9F51F02F9D
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
PackageRelease4.el5
PackageVersion2.0.0
SHA-1B212AC3693836B51674AB6A6258B3EBBB15766EE
SHA-25655E206A8E7360DFAEE98E7ECCAF5101E040465BE2875650D631D8CDEE9CFBCA9