Result for 3066B7A458804FCF3F9FDA583703C8987B8C4B66

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize10544
MD5BD3E40B8A07BCE4878E5622D2ABBB111
SHA-13066B7A458804FCF3F9FDA583703C8987B8C4B66
SHA-2568D20A2EDEDA03DE3A4CB4965211E5972FE8678E8B9B5A99DDE66A11399535CC3
SSDEEP192:fmEdCr6ORpJnUCCisQrVAcYRAV3lXmIdRA5/AAKEh0s6fC:fmEdCr6OjJUCCisQr6ccoF1dRd1EWsz
TLSHT1BA22C40BFB82CD72D8922731805FDB3B92228884D912DF07BB48DA6C3DD679D350AB51
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
MD595EE9B152DBAC09AA682DB595B5C437B
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
PackageRelease4.el6
PackageVersion2.0.0
SHA-1A997E3CA9A95AABA591F5EB42D59A3C616F431C7
SHA-2567FEAA7FC303926530C53A92120CDD2475691D7A0D4B083BC0FB7748A9C433465