Result for 70A910B34AB033FC72FADA4E8434593253635484

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize19824
MD50212ADD6E85992BDAFF6D9483B7E4141
SHA-170A910B34AB033FC72FADA4E8434593253635484
SHA-25642F11AF8E397330D580FA0D7A59D3CFA6B071D00687A0D37D07D4C1C297CEDA0
SSDEEP384:bES0O4CivXFfPAQnHrQDFYwElMWjeDi3:bEthvXFfPpLQDi27Di3
TLSHT1A692D51BEFC49FB1C8C58A718497463166339AF4DA10A35B0640FAB92E62BDD4F0B758
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
MD54DFB7C32FA65281E38C2EBB44CA1E65F
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
PackageRelease21.el5
PackageVersion2.5.0
SHA-1146E0D4F62399566E76E16046840645D8806118A
SHA-256EB3E1F6CE628511D7CB2EAF7D919B7ED6E85F61A00822EBB60E9BD2168A763AD