Split from #22.
+1
Someone referenced this link on the original ticket this was split off from: http://www.pythian.com/blog/repost-oracle-protocol/ (it has useful information on the Oracle TNS protocol).
I did some research.
Here are some interesting references:
Conclusion:
method, resource, path and query.@tsg If Elastic is willing to get the licensing resolved I can have a further look at the implementation.
+1
+1
How's it going now?
How can we help?
@darxriggs
@darxriggs +1
Any progress? :+1:
From my side it's on hold until someone resolves the legal aspects.
We are currently not planning to add support for Oracle TNS as it's a proprietary protocol and an implementation would require a special license from Oracle. If you are an Oracle partner/customer you might be able to help us with this. Please contact me privately at [email protected].
@darxriggs expect
to add to @monicasarbu note, we would love to work with Oracle to make sure this is available. The best solution from my perspective is that it will end up being a joint work with the community, Elastic, and Oracle, to make sure this is something that is well maintained. We will try and reach out and see what we can do, but we need your help as Oracle customers to raise it with Oracle as well.
+1
+1
@monicasarbu Sounds strage to me that Wireshark team can openly (like in opensourced code) analyse Oracle protocol whereas Elastic team could not.
In fact as mentioned in the links posted by @darxriggs (on this issue), The code in Wireshark is based on reversed engineering and not on the official partnership access to Oracle documentations.
Might be worth to contact Wireshark team about it?
@monicasarbu do you recall if there was a conversation with Oracle about this one?
If no actions were made can we close this issue?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue doesn't have a Team:<team> label.