Result for 12555348B5A0062E2B052B3BF6BD1A6725FA02E1

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize29472
MD5059437E38BF3F53D971CCAFD1A7F1EE0
SHA-112555348B5A0062E2B052B3BF6BD1A6725FA02E1
SHA-256F433B215C8377BBBF40B23AE86A9230D58C357CC887DEEF4698857DE99D9BE4D
SSDEEP192:GYx6bi0CTArqgA8Zji/WMF8WFjMxqKUTfNwLMlDSX4UDyeG4BKc4RU9ma87W7e2A:V6bJqgvMFJAOArz11VDbk1AGQYuc
TLSHT1EBD2E68BBF978BF2C0808970446B49326FB345B4E667F25B6450B7B91841348EF67F26
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
MD5C9CBBDB68CFCFEA193BCE65557F0FD27
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
PackageRelease7.1
PackageVersion3.0.0
SHA-112BC51AB81BF95C66ABFF52AEF1C10A1335B8542
SHA-2566BEAAB560E012D26BE14D5BF0E7B6FC0DBD871C909D7E371286F398B456EB5C8