Result for D47AF12989F3019B44D5A4294B6C3463B2536BC4

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize10816
MD5383AD5C916846D267EE6FE64E7E35C4E
SHA-1D47AF12989F3019B44D5A4294B6C3463B2536BC4
SHA-256EC6A9F44BC85CC20D71A6A05DFA85741F45072DF397D0937B3E9270A67D03203
SSDEEP192:f4Xtr6ORpJnUCCisQrTHtMepjWeeoE9+dKh2x:f4dr6OjJUCCisQr5MepjWe1E9+0
TLSHT1D522094BFA81CD72D4F20A304123DF364221C948EA51DF03E648997D7CDBFA9B66AB51
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
MD5D50797D8E40276BC28ACE3C210F29207
PackageArchi386
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.el5
PackageVersion2.0.0
SHA-18D7BE056DCBF75DE6CFA25527FF4D6A17C28D13E
SHA-256FE4ACA95696D1239CD1C953E61F2D2766E105C8433A638BA59D6F60086A1A109