Result for 2D5F386C975A9A2F0BE83676CC19C499ADCB74AD

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize15448
MD576AA741B962693EC90E15F44BDF0BFE4
SHA-12D5F386C975A9A2F0BE83676CC19C499ADCB74AD
SHA-256BEB09289DD26A46AF480B9A45667698CAD05492AF83A039FA37C5FF2FBE745BE
SSDEEP192:olvnpc0iIOQVPCivlZFWoqX3JHpnyMKM7wD52l6VDpV7eWp14Ldg0O+akQeW:opFiIOqCivlZFY5HpyMKzUYVVV7JiH
TLSHT15E62A5C8F6E987F3D9C11E3D12170B02A3A18AC4976F7B83479C66782D53ABC9D49E50
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
MD5714027257C2FFE1A9F5D6B2A7D253D98
PackageArcharmv7hl
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-114812D89918CB4220567B95C9E57A8E72492321B
SHA-256F8895B34434246DD5D615C9A030D450011CCDADF3DF13D1051500759D2F5B3FD