Result for 17577C5F394F415D48ADE74FD6AF31B16B062542

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize19572
MD546D9E4EAC427A2A076641F5F456ECB35
SHA-117577C5F394F415D48ADE74FD6AF31B16B062542
SHA-256337456BDE9C6B9F3AC4751BB5FAEF4BFE7F470F882B42297EC1FD47F41E521E9
SSDEEP384:f9Do0lOm6uS2AMQPKfmeK47CcEqKaz/dPZ1vsIxm:VMTm6R2bUKf7H7CGVz/hZB
TLSHT16E92E799FBD6CD32F0A308748523926513F19E84CB57EE4730A86FEA28513A8A5C7710
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
MD59AE473A134F3717A3C51C65835574D7C
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
PackageRelease125.41
PackageVersion2.5.1
SHA-10F7C7349C2FBB1EEAA3EC2DCEC21E892FCC2F844
SHA-25671BA30AF5C8D86BCF94CCC148F6FBB57F9A5194A44022F2C33830F3CA128D8B9