Result for 07591D790E522099C909AEEBD4B8E22EA94C74CC

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize28760
MD55E7D0977F9584F6CA83E6588ABD39E83
SHA-107591D790E522099C909AEEBD4B8E22EA94C74CC
SHA-2566E9A854DD2A8A4C0ABE1024CB8E6D11C97861546220C139BB44BA8B6195341DB
SSDEEP384:7LoNZSIiac77zJ+rFi1/aOCONukoirvJw:7LJac39AFECVvD
TLSHT167D2D95FFFD687B2D1C2893448274B226BF348B4DA27D21B6181BBB91C803589E97F15
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
MD58640619563D4CE6F5357226F1638D4C6
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
PackageRelease31.63
PackageVersion2.5.0
SHA-1356C13869C8A689115C9DFAABA5B693C696FC9D8
SHA-25643CFC8106A7CEEDFB4F867306B5C0183F20FCFFFB8CA1207610A473F59666015