Result for 755B53D17F595362BCF0EEE2851A47417A90D27C

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize25248
MD5D74819373DCBFF70F9F94CB2B03760DD
SHA-1755B53D17F595362BCF0EEE2851A47417A90D27C
SHA-256300B7B3641D2C92BD1132834710C560CD787FEA1B44DAD81021C45066A0EACFE
SSDEEP192:G82NqWjg25XoYcJCjYmMFuoP13A0RrSrEDikFsd1DSXfYhXwaXMcClJZkTmlI7rj:CtXVpMFdcvKcOUBrAC+r0JUh3b21
TLSHT1A2B2C78FBF958FB6C1C04A7044A307726BB349B4E643B20F5510BBBA2C417989E57B79
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
MD588A166649295A00D262AD73B27D755F7
PackageArchx86_64
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
PackageRelease142.176
PackageVersion3.0.4
SHA-1068DD02701C48E998F063711C86C3FC3340177F8
SHA-256AE525CEB5FE83655E197819077A222387329846603831C5BDEEC6F517305414E