Earlier quoted context omitted.
I’m aware of that claim. I can’t verify it of course. But even if I take it as true, doesn’t mean that DEFCON couldn’t have believed he was subcontracting for EE. Similarly if it was DEFCON who introduced the firmware author to EE, EE might believe the firmware author is with DEFCON. Obviously the contracts should be crystal clear about who is with who, and who is responsible for what. We hear that the fimware develo…
> We hear that the fimware developer had no contract with anyone. I see this occasionally with small companies, usually it's more of a personal request from one of the employees to provide some code on a volunteer basis, perhaps solely because they are passionate about that sort of thing and someone knew that about them. In the end, if the favor is upheld and they provide the code/binary/whatever to the company (who…
That is not the only legal liability. If EE has a contract with DEFCON saying that they will give DEFCON the firmware and the rights to distribute it. But EE does not have those rights (because they haven't signed a thing with the developer) that can go very wrong for EE.
Basically the developer can sue DEFCON, since they are distributing his code. DEFCON believes they have the rights to do so, because of their contract with EE, but basically EE is giving away something they don't have. That can be a lot worse than just failing to deliver the contracted firmware. In my opinion.