Result for 17E14C9C60FF91FDDAE27B8ED913A4F4E40390DB

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize20104
MD511C126AFC4719299FB50A73F9E15CF03
SHA-117E14C9C60FF91FDDAE27B8ED913A4F4E40390DB
SHA-25668F86B28FFC6613F586A71E4071CF7AF7DAEE22B3423175CDE58674AA78A2443
SSDEEP384:f7jiqgMF7Faj2lMJJD76hFtjEIPFS8jFRxHv2:TjTnF7QjLvn6hPHPjFR9e
TLSHT1D792FA96FFC7CDB2E0930C744537476262E18E85EA4BEE47302897E92C507E89953F52
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
MD56C25630EA046DF9AB0A1FA26CBA6B5DC
PackageArchi686
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
PackageRelease33.642
PackageVersion3.0.0
SHA-1162544664BB2B0924E07F75FEE58A9FC20646EB9
SHA-25620CD3A3B1AD57811295664D32E2FA0A823139E63655B6E5D718DF3B184396FC8