Earlier quoted context omitted.
You don't agree that you need to provide a way for your customers to replace the Qt libraries? (because that is a fact of LGPL3, read the anti tivoization clause). Do you see any possible security problems with the above? Because in reality it means that you give your customers the possibility to run their own code on your hardware. That is a problem for many companies and products.
>You are forced to help customers replace the Qt libraries in your product. Depends on what you mean by 'help'. You are forced to give the opportunity for them to do the work if they need it. If you have statically linked files, it can't be done by accident. > Do you see any possible security problems with the above? No I don't. When I provide completely closed binaries for my customers, they can hack with the binari…
How do you do that, while said software depends on LGPL3 licensed Qt?