Result for 4B884E1D4376304E1D1EC6A92ED6E1C765B46478

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize19576
MD5E937BE2BDBE87043409752FA634FF7BD
SHA-14B884E1D4376304E1D1EC6A92ED6E1C765B46478
SHA-2560A8F33C72CD9201D9F672340BC7028E2D087A30991F6883DDF2ADB83B8FCBEC5
SSDEEP384:fzvvOfCivtqm+cJHkMyM9U9JIU0NaFkA/eFzErw:LvvAhvtqm+gHfyM9U9qIT/eFzy
TLSHT1F5922B54FFC5CDB5E4E31978412387A562618E80CA4BFE4731682BBD28E23FC6A97750
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
MD5F5A74D2C30FC0A759A6803A1785B7BAA
PackageArchi586
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.63
PackageVersion2.5.0
SHA-13F9CAF68E8F40A29D590F89250685B2AEAB02E2C
SHA-256EC4BF16E19A79222FBE75FFC018EB22D969766B58A88F38DFB3E89DA1C6C282B