Result for 8C0C36FF7E4E67A8985A831E1FB9D8D673AA1EFD

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize19540
MD557DE7F85C65804BC0AA84AC47D550FFD
SHA-18C0C36FF7E4E67A8985A831E1FB9D8D673AA1EFD
SHA-256704583347F8006EBD0985E01C0B5A5A01B5ECA3AAB263EEED7787C64E830DF52
SSDEEP192:qMFzCs/MMqkZHmqwp7FHhHnwnnA17/dk6rBYmlhXhm6gJ:qaWsFqg6FBnwneJVrbld
TLSHT1FA9260C4FB86CBF3D0862D7561379B1333A289C8D78F67864418ABF86D46B59D911F02
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
MD52582AE104863A42A0D8B98830FBA1771
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
PackageRelease33.1
PackageVersion3.0.0
SHA-117629D33B267BB8DDF8651ADA4823C561AAEF2B8
SHA-2565DC1ECB5070CE1CA231606DF8231B403D8344A6729409B85A93EBFB11FB02CAF