Result for 56A9BD5DF33896F736672E07A0841B7F97C7C19A

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize31496
MD56E70695F612870CA7853EBF9174E23BD
SHA-156A9BD5DF33896F736672E07A0841B7F97C7C19A
SHA-256BA51078D6CF91C681E94F4654D192C812ECBDF3D5EAB9E468AFAA54497A6DDD4
SSDEEP384:jkfOVCivqxMFY03n1bUh1ROowlvOzKeCm8yK7z:jk6hvq2FXnVwOoevIKep8yKv
TLSHT12CE2C85AFBE88F76DCD19D7C88274A3352314E84D609D20B92506BBE2C417DCAB0E796
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
MD5ACD236C881DE8547CE78720CB284D844
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
PackageRelease76
PackageVersion2.5.5
SHA-1074E9A5045C7FB387642AB2C415D94526B03D7C2
SHA-256AD757F21F85C33208F7B1BE4AA0639F5912AB7C34448232DA8E83E73DBB654A7