Static vs shared library security?

Indeed replacing the shared library is an easy way to capture the key. However, putting a breakpoint and capturing the key in the running application when you link the library statically isn't hard either. So as a library developer you need to live with it - there's no good solution for this problem.

Methods to counteract stealing keys and using the "pirated" versions of your library are mainly non-technical - track users and deny support to those who are not registered, provide updates via restricted area on your web site etc.

In general yes it's possible to replace a shared library with your own version that provides the same interface, in linux you can set LD_LIBRARY_PATH for example to tell it where to look for libraries, and in windows you can put DLLs in the search path.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.