Result for D503988B8FD93620AA607D025463B6062FA7F826

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize13680
MD5F63CD50B6F73898DA9EEEEA0D131A5ED
SHA-1D503988B8FD93620AA607D025463B6062FA7F826
SHA-256265D78B82D3A9D4C17BA8E76769B8C0B3BA37C4EB769D703E90E974C74257D91
SSDEEP192:G2plBr6OjpJnUCCisyfVHuSRa4oQYbRG5BVxBhqwq:JBr6ONJUCCisyfQSRpoQr5BVA
TLSHT16B52C747FA80CB7ED4998370849B8A35A333957CA750971B0A00E7B83D927AC0F57A99
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
MD5D287D4AC1F6295DB8801E9652DAF3F02
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-17FEC56F55D9F6C11452ABA29D41C4A2A68483AA4
SHA-256FEDA88C3215B770A89988DD6AD2831367FB932BE24E7572994E2C822B55E2020