Result for 363A21D5CA9E9C7277F781747CB8491FFF6046C3

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize20360
MD54A9C95F6541059E331BAC0E3AD9A0DB3
SHA-1363A21D5CA9E9C7277F781747CB8491FFF6046C3
SHA-2560359AFC7DF295BE8743F145B0C6C0FA328A4DC970DCCEEDBDC340B929D400CFA
SSDEEP384:TNor6ONJWYCisQc7CXlgIn5GaWRKj0W6wN7Tgst:C66JWYhsQc7CXqaWRK5RT
TLSHT10292F927B7D08BBAE4C47238589F87E1E22394F09705A20F6346D76D3D41BC90F8E699
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
MD5AF849DD732EB1FC5CED06BF3980B5FB5
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
PackageRelease4.16
PackageVersion2.0.0
SHA-1797B6B91CC451712A0F9F1CEB7834D22EBA1DBAD
SHA-2561096AF2927821ED5C9EE369F08D12B40362F57D0D3A4FA4BCDB6FB7F979252D8