Result for 80F6154B545FD04B5B34C1044825426BB1FD85A6

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize32240
MD534377DD8990F404A919C69A01AE5EA4C
SHA-180F6154B545FD04B5B34C1044825426BB1FD85A6
SHA-256B22BB7979A55ADACAA6BF7E79DF8CE1089D06DD56FD9934603C0B1F8151422D2
SSDEEP384:c8MbvNkcMFoEYkj+EbiNh1RGcmc58KGK+Y:c8b9Fo4+Eb8GcFSKGK
TLSHT106E2945DF7EA8EB2F4C359798C37473306F15D48DA2B928B6140AFFA288078CD649716
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
MD5A316739BFB5A3B302A0299385C8BBCE6
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
PackageRelease31
PackageVersion2.5.0
SHA-11488D9E1C96C08067751D0869C624EC3A63F76EF
SHA-25638B2F87247A457D17077E06BE2B692755A9C50CF26588B46841B2445DFA1B60B