Result for AF2A862F53D8A7945ED0ADC3455D9CEF8D3F054C

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize19572
MD5483C230374664AA558ABCD93D440C589
SHA-1AF2A862F53D8A7945ED0ADC3455D9CEF8D3F054C
SHA-256F3C82CB1DC5562FB86AB89CF3FD9A8F0FC1BB6C6CBD957DDBF9F97C93F478E47
SSDEEP384:fHruOlCivtqm+cJHkMyM9U9JIU0NaFkA/eHAAkI:PruShvtqm+gHfyM9U9qIT/eH
TLSHT129922A94FFD5CD76E4E3193841638A9562618F80CA4BEE47316C2BBC28923FCA697750
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
MD5D51B24DDF2848C6AFB9DDF80732BA3A9
PackageArchi586
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
PackageRelease72.41
PackageVersion2.5.1
SHA-13C76A2A0622527E5277542F67011A35763784AFA
SHA-256B8EE1182D37A913361500361C3B4FDF8D18F7A81A9E9C0A48A6F12E281A8EC0A