Result for 591555F95E6211A544D2494DCB7A3854B6A2BC0C

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize10816
MD5E27ECAEC5FDC6ACEDBBEA88641866808
SHA-1591555F95E6211A544D2494DCB7A3854B6A2BC0C
SHA-256A1253F00F27A7802B2FA103284A400CED70931D6F8038B4F89C00605DF0A6357
SSDEEP192:f4XRr6ORpJnUCCisQrTHtMepjWeeoE9+dKhfx:f4Br6OjJUCCisQr5MepjWe1E9+0
TLSHT1A522F947FA81CD72D4F21A304023DF364221C948EA51DF03E64899BD7CDBFA9B66AB51
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
MD53D4DE189F6A95C1C83F457B5C6A4BB0A
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-12E3F43719FF552B21AF65106F63733D9DDC9C0E3
SHA-256F55224C07B7DC2D326B96903B7D595CADA8ED218B11C39659492226388B8D9FE