Result for EA138E5364118E9D1123EDAA0CD77C54BFD322A3

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize33008
MD590D1E03BD6917FAF8CEA49365BCEE605
SHA-1EA138E5364118E9D1123EDAA0CD77C54BFD322A3
SHA-256CE516E45C955F12AED2D2D7A07B9BC19673CE72A5CACF56E11C5BF1BB1BDFEED
SSDEEP384:sACLrOgCiv/tMFUzzWIwr0TXL30/UlkjRYERRRR9RRRRqd:sdr3hv/CF+zS8L30clUQ
TLSHT160E2D78BFFA78B76C1D099348467CD246A73C9B0DA51A2175185B23D0C823DC9F5BF29
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
MD5ECBA28A41ABB8222C79FF055E8A47AB9
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
PackageRelease23.1
PackageVersion3.0.0
SHA-111DE615F2CF4110F5D5B759FDDA561D747D05142
SHA-256144B4937CCAF546BEA97A9E6969DB781FC80B9F64B53A0D9B3A9175701B10828