Result for FEFC1BBC6D96477D2115563646BFC28C4C45B629

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize10544
MD58DC2854643B494975F07A42F9B93295B
SHA-1FEFC1BBC6D96477D2115563646BFC28C4C45B629
SHA-256D2DDC278637E304E863C0E2C7B662A4B4901675A8AC36C7299DE9B700EE1BC35
SSDEEP192:fFEdCr6ORpJnUCCisQrVAcYRAV3lXmIdRA5/AAKEh05fC:fFEdCr6OjJUCCisQr6ccoF1dRd1EW0
TLSHT1DD22C50BFA82CD72D8926731805FDB3B92238884D912DF07BB48CA6C3DD679D350AB51
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
MD571BB74ACAA933B37AD3F72D13E1E3805
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.el6
PackageVersion2.0.0
SHA-1BFE057CC3144F6573A516B1266DC0B10D6BBCF8C
SHA-256CBABC70FC113EA3580E398505ADF5E452443C92993CD6E98BF09E9D8A3B97215