Result for 4473D175078F883BCAEB8335DB012A7B58BC8FEE

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize28760
MD55FE5072DB3183B723F031D74617C52B7
SHA-14473D175078F883BCAEB8335DB012A7B58BC8FEE
SHA-25698E765C1192C57602373BA6FFF7CC495EF7E34CC1046064FAE9F18DAFB468271
SSDEEP192:GwLT3gYdj170Q6js4c7MxfFcpZSLk3FMDqf4LyR6cIMVB0uPPo0+2bG6XVYHqJ8W:7LDgwt0xc7KEoErTcMBIb5ONukoClf
TLSHT15CD2C84FFFD69772E1C2897400170A266BF32574DA62A61B54807BBA1C8035CDEDBF29
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
MD50F628042CCC484DF75B7D7C467728BAD
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
PackageRelease125.41
PackageVersion2.5.1
SHA-17C7143A5830AA730390BB50B79D97F5BBDD6DB39
SHA-256FB09EA6806D6057DD6EF56ABAF202EB5AA2D5BC908EEDB48458230CD46F35F92