Result for C60B41DF5BE0A487065D6E2D75F5B80F7E20DBAC

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize20496
MD51E158EA3ACA8C14C05F58735571A4A0F
SHA-1C60B41DF5BE0A487065D6E2D75F5B80F7E20DBAC
SHA-256FE0EB6EFF81A1DACDC5942F34697E85F6329DC98F783E2E91BCC06932141DEC4
SSDEEP384:/CzquUO+CivV/Eh3Xf9Ukn5zW8gNRVMTPQ:Mq9/hvV/Eh3v9LntW5VIP
TLSHT1F192C66BFBC98F76CCC2A930846B8A627A3369F0DA10821B0155B77D1D4079C9F1F7A5
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
MD5F7A8B8FD9273862647F8BF9A4B52F256
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.1
PackageVersion3.0.0
SHA-107B2C999EDA69310C8F30930F309B111006233CF
SHA-2561AED0C9FD227298C35725E06DE8EDCF79C98C856126F360DBBCFF9AEC3624EAC