Result for A2D4FCEFAF32490D4891EC0FAD6C2C384A2086F2

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize19912
MD5E8B14D19A9EC3A789EE109648D38B74C
SHA-1A2D4FCEFAF32490D4891EC0FAD6C2C384A2086F2
SHA-256414F252D46E091D09CF8E1B3CC274A8151AB047EDF81B6F1AD3534AE077F9484
SSDEEP384:uDzO4CivXAcsAQnDp0JD2Mswm4olJpYVJx:ufthvXAcspW494Jx
TLSHT14192C55BEBC9DFB5C8C19974846347316673AAF08A10A21B0250FBBD2E617DC1F1B768
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
MD50D74139E40B462412BA308791D9C07D6
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-10BC6DD50707C60B8487700F38B27E56CA1EC3899
SHA-2568EACA72E659B29D47E8853DB8A1AE6B665779DF043E921CE354349F47FC62260