Result for 93F894D114DCE5F023F6E4F94AD3D355539B389A

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize25384
MD5E1B88DA650C8C5FFF0F42FD8C9E449D9
SHA-193F894D114DCE5F023F6E4F94AD3D355539B389A
SHA-2562B7DAFEFA3F4FDAA28DEE3ADAF1A8C2EA59ECE96BE9D4321ADE805B9596EF6CC
SSDEEP384:HR3OFCivPAc7GD0VK4erSGxVyjV9H1ojZs:x3ahvPAcKDJ3VI9H1ojS
TLSHT1C3B208AFFAC89BB1C8C159344D2B8B522A735AF4DA00921B60417B395C813EC5F47BB6
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
MD517DBAC724CAA9E8787B132266066E1E8
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
PackageRelease6.51
PackageVersion3.0.0
SHA-10DE4C8EBDA433BCD5C87DD24C582B708D84201ED
SHA-2568CE31DCB4771924C270E8418C66B0B72F165A5705CFDF85ED347E1D02474A692