Result for 3811653E5FEED499B86FD41519DB862E18959294

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize19740
MD5C120B1DA6583F473A665CF8EA5EDCF1D
SHA-13811653E5FEED499B86FD41519DB862E18959294
SHA-2566ECF3B0E953DD23614ECEC520C9AB4F1E8F66046FBE3F1A70B277F17F6ECD237
SSDEEP384:f6q4rOBCivnqma4iAMiP9Xm+z4XsnmlZelRt:idUhvnqmahbiP9Xmg48nm36
TLSHT1B9921912F7C5CEB0E4E3253800238F22D230DE95AA4BBE4BB61C577E3D413A955A3769
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
MD5263B04B6606F3DCB02D31E8DD46D4B8A
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.1
PackageVersion2.5.0
SHA-11EBC5E92FE77A6960DF0F67F41803A41D27AC0BD
SHA-25659A0B6C886DD70BC8ABCC1ACE56055FCE684F488E913917561AF5A85E606E407