Result for A140A883522C415CCF7882D0EF85AB518A1B578A

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize25248
MD5EB645A9F62CCAEA76B4156AEE1602D57
SHA-1A140A883522C415CCF7882D0EF85AB518A1B578A
SHA-2563D28E6E89B63F5794F35A3F8B6D186354AF58B640899B25C1F0BE5C1454515DA
SSDEEP384:sOS+qnr5H0c5MFEqCkpfyFjGpjBDGyK/JUmO+BFs:sfnluF2k45GdB6fO+
TLSHT1FCB2C78FBF86ABB2D1C00A70441746B27BB389B8E687F21F1510B77A1C41658DE57F29
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
MD5561349C871032F7F4A49A65ABDE0D3D5
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
PackageRelease143.1
PackageVersion3.0.6
SHA-109A9377AFEEB7E6586ED869A139B87A1C1DD9A1F
SHA-2569202C8FF485BB67C3F17B79C0536CD6B586A71C3EF4BEE94B64EE21015177FD0