Result for C4944F8C7A4FE8D47BFA5F8AD73013F08CF3219D

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize19912
MD528716EE81B9A67EF8A7176ADA852558C
SHA-1C4944F8C7A4FE8D47BFA5F8AD73013F08CF3219D
SHA-2563C14ED433AF6962AF07715954654D1D94578CAA47CB69BED10319AB745AA4D79
SSDEEP384:DDzO4CivXAcsAQnDp0JD2Mswm4olJpYVJs:DfthvXAcspW494Js
TLSHT1F392C55BFBC9DFB5C8C19974846346316673AAF08A10A21B0250FBBD2E617DC1F1B768
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
MD5C8EB151608CD40C6297ACCB728E0AAC6
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.el6
PackageVersion2.5.0
SHA-106BF8A12C03FEC6A405F1183EAA4E0478E0AC1F5
SHA-256F74EF34030BF4716F02A24CEF516677D92F1CFF8A69E291313A76401A7FFA220