Result for 614011C9118F914ECE89EA55E03C65ED7A55D4F0

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize32216
MD56DCE71C8A20548D4123497CAB880B904
SHA-1614011C9118F914ECE89EA55E03C65ED7A55D4F0
SHA-25688FF6FA3E90DEE073D1F7C9727A1B6BE146CF0C95CF3C25FA6AAE0A8E1634FC9
SSDEEP384:+d2rqO0OMMFWq7vrNzzxRfc8U953K2pqKF:+d2FtF1vxzzzfc8UnKJK
TLSHT1FEE2A68DBBCEAB73D4C05F74452743633BF1858DE787E357A010EAB9A441B8C9A26706
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5B688DDDB24C5D76815E79D3EDD1B116E
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
PackageVersion3.0.6
SHA-10913F4B217ECD31EA8FFF6538F717EF81F12EC1E
SHA-256B59C7AC2F2D748F7AFC352C729E4F2CFDB2B17EF2B26F21AE2A89DDDB54D17EF
Key Value
MD540C846896ED84DFEF4D8D44E9E0FC5DE
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-1125E441DDD7A3BEBE9AA7164C3543A5884E17FB7
SHA-256E7EB276B93B94569B7AEAD3991E708F3B85D753A8809CB2F09A22F6C0131B05B