Result for E5A73CF19BDDDDC28A8BD9C4EAA8420186FAA7CC

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize15144
MD5C7A6B9739017A37FB6B561820C1D9F4E
SHA-1E5A73CF19BDDDDC28A8BD9C4EAA8420186FAA7CC
SHA-2566299AEE6474D07923037DA06B6CA35D3D6F7F771E85AD8C10ED0C6D5E645FA93
SSDEEP384:fznr6OjJWeCisIrHDbzsXL/EGXsL2EmgY:br6gJWehsIrPYXL/EgsyEK
TLSHT12062D50AFB86CEF3E0E31A744417971B96229840DA1EEF53BE08966C7C96B999407643
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
MD5ECB901747CF03907ED6E6D975CA2C836
PackageArchi686
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-1555C027499D874C709B879B9F588264B84D713A9
SHA-2566F3493FCB19A5A0D2DFD48E61BE0B392C230636465FB3AB9DF88AFE48D5E3CDA