Result for 91A03D4AEAB9A4FDA6DD1BFA2963451B04D3181D

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize24560
MD522995162701D2D96AF95AD0F75F7AD15
SHA-191A03D4AEAB9A4FDA6DD1BFA2963451B04D3181D
SHA-256B449117CAEFE4EF393A8B015DED22342045771D1AFE7B4F96DACFF888235205C
SSDEEP384:vpkIOsCivV/EX6K0K7Y2mPSqdzFqGV44SvMn:2IBhvV/EXNTNqpkGVnSv
TLSHT127B2086BE6C99B76CCD2A930CD7B4621663329F4DA20530B9154BB391D403AC8F1BB65
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
MD524CF9D1C159A83A9B2180616D7D89B48
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
PackageRelease23.1
PackageVersion3.0.0
SHA-109DAC6A5C84678D520AE8C2145ECB9F4F2332DDD
SHA-2562D55AB20B2DE874CA0B14BDAFEEC279568D06D1919A0DE8FE6489E840260A4A5