Result for 3B0028149BD571C6E73044A205D8A0342269C494

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize13152
MD5A40CB492E2823D516D334B8AE6677CE5
SHA-13B0028149BD571C6E73044A205D8A0342269C494
SHA-2569208E5B3E3D9B3D18027C3D2948002FB4389700641D2539EFD965B2B93DAFA80
SSDEEP192:Gfg6r6OjpJnUCCisBc/7nfvlpza6iCDTNZNwfMv2SSc:Wr6ONJUCCisBcTnfO6K0x
TLSHT16C42B44BFAC2DB7AC5905374C0A78A3166335AB49726872F9720F3743D92B9C0F07665
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
MD58EC6A9A3B7C5596C434BC25DE9FCB4F0
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-194A99B4983E421E2B06CF18695B892DE77B8C945
SHA-25606387AB5174BD32AF4F1B4A52F3A0E5150D9CAF019F1FD7FC37C51DB15E22B1A