Result for D77C3807902BDB78440E139C5027AEA4A089A000

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize22940
MD5CA563D4F414281D6BEDBF7E215847AF2
SHA-1D77C3807902BDB78440E139C5027AEA4A089A000
SHA-25614C6A4FFCDA83211588420EE066ED36FCCE1A47C757583497C4DFEE6123EFFF0
SSDEEP384:jdAEf9xH0m7SnwZsa2fADAbDZZZZOZZZZlc0mDjg+lo:pD0mWQsJfADAb0c0mDER
TLSHT1CFA272C8F7D7CAB3D1826876A677DB0163E1C9C8CB8F57871198DAF81C8239A8D45B44
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
MD575E666B2B7D14AA5CA53AF71FB9DB652
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
PackageRelease31.1
PackageVersion2.5.0
SHA-113AC7C324AD496D76D7736073B2BE2413928E8CC
SHA-25699CAB4CCCB99E247BA393156A7364F9C6B8DC568B69A5D1763F8C52C239C0F07