I made a small library which I decided to open-source under the Apache 2.0 License on Github.
Not long afterward I realized that some of the code in here makes use of proprietary information which belongs to the third-party company (let's say that it's the structure of the packets of data) and the fact that anyone can find that structure on the Internet (there're at least two libraries and dozen of articles which describe that structure in great details) does not mean that I can use it in my open-source code. Now, I can write an abstract parser that would handle that format of data and, possibly, some other formats, but the question is - how can I release it so that the company can not claim that I was redistributing their proprietary info?
Is it enough to put some commits on top of the existing code which will destroy all mentions of hard-coded proprietary data package structure? I don't think so, because anybody can check the Git log and see that information here.
Should I add this abstract parser in a new commit and then squash all existing commits into a huge single commit, so that there will be no evidence that this reliance on proprietary info has ever existed in the first place?
I wouldn't want to destroy the overall history of the repository, but if that's the price that has to be paid, then I'm fine with that.