Result for 1FF51B6E1E986EA57863FCB7F8883B40720E48BA

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize19540
MD54A8AFFC0A65CEFACC9286E05383FD7F7
SHA-11FF51B6E1E986EA57863FCB7F8883B40720E48BA
SHA-256328DA9FCD800D7A63FFBC1FF2E507FFAF8EE0C72B4A991344FA9E5AD0F7AC527
SSDEEP192:qYFz0wkVqkZwGZwp+F7vrHnwnnA17/dk6rBYmlmlvriJ:q2sqjMFnnwneJVrblmB
TLSHT16E9260C4FB86CBE3D1C52D7961379B1337A289C8D78F6B860418ABF46C46B5AD911F01
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
MD5B0708FC6FC7F7AF2877FCFEB7916A872
PackageArcharmv7hl
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-12005EE26EBA1AB2B611A6953835B81E0C9C2E5E1
SHA-25651157FBBF36C998F20C5F271D74C5E84856C945C22F00A6C1EB322B9A08E99F5