Result for 0B49E9A2AC71A20F547E34C598DA02909D4F640F

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize13152
MD50B52454C2BADD5FB597C907EDF60BA63
SHA-10B49E9A2AC71A20F547E34C598DA02909D4F640F
SHA-2568A4F27179A2BEF6C4F9C39474DBCAD2586F0C2E6399DC1012CF801480A312501
SSDEEP192:GfBr6OjpJnUCCisBc/7nfvlpza6iCDTNZNwfMv2pSc:Yr6ONJUCCisBcTnfO6K0M
TLSHT17342C54BFAC2DB7AC5905374C0A78A3166335AB49726872F9720F3743D9279C0F07A65
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
MD5F45A80494CC1EBE8F216AC20946453A7
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.el6
PackageVersion2.0.0
SHA-12C916773EB3BED40BA61A418BB641C99EF02B1EC
SHA-2560C4EC8F6022004D50C43A5CBCBADD40C8535089447394A2C868BD25D804FC720