Result for 63C2688F987A1D6497CA1461201904FDD6CA97A2

Query result

Key Value
FileName./usr/sbin/tao-cosnaming
FileSize25256
MD591185350896CA663866CDF9ECA0734D0
SHA-163C2688F987A1D6497CA1461201904FDD6CA97A2
SHA-2563A3DB7B4DC128C47B56AB933ECD80018F66939507A641279B871E1B9A64F890B
SSDEEP192:G7sfr0DArqgA8Zji/WMFoWfxrh64EjPdDiZcVDCnHiMMWoRacoQE+HojWk5l0Qf/:1bqgvMFCZ1vij1lpK4n4n7B+vd
TLSHT186B2C48BBF958EB2D5C14A7004374B736AB34AB4E617B21F2450BBB61C01798DE53F26
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
MD5E23FDA4E8E43A8944D57A34540E6F187
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
PackageRelease33.643
PackageVersion3.0.0
SHA-1091E88D784EE98CE825FBD5DF1A84CC15C2B8FC1
SHA-256576C83DA3B71B5C597D2017ABFF55059141DDB79EBC63825D96125BA8A7FBC25