Result for 7A41ADBAB652E296C1B7E1EF64641FE0C0F3D660

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize16008
MD535E629DEFA5E7F96DC3FA769FB7A9D62
SHA-17A41ADBAB652E296C1B7E1EF64641FE0C0F3D660
SHA-2569C0F0BC181331E9CF1321E90269BB2458A5FC975FA99304C76A07C8A53A03BDA
SSDEEP384:Oir6ONJWeCisgEGdr312Tjzpn0T1miTDwl2zf:d66JWehsgEc3wXlgEiol
TLSHT17472C417FAD18BBBD4C16674C06B92727A3354709312D32B5281A2783DD23AC4F5FB6A
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
MD55142B7C7FFCE309087154994C64B92FD
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.2
PackageVersion2.0.0
SHA-16BD4CB27825E7DBD52CDE0145A2996086AABC32F
SHA-256C167D36C4690A01B37E1CA77757620976B8D1E00CC33230F3E56E3EEAE669276