Agent does not protect against shaded jars

[JoeBeeton]

The agent checks for the fully qualified path to the JNDILookup class. Normally this will work fine, however if the application the agent is protecting was compiled using the maven-shade plugin the log4j class package paths could have been rewritten. So instead of
"org.apache.logging.log4j.core.lookup.JndiLookup"
It might become
"com.example.org.apache.logging.log4j.core.lookup.JndiLookup"
In this case the agent will fail to protect against the JNDI lookup vulnerability.

So instead of
return "org.apache.logging.log4j.core.lookup.JndiLookup".equals(target.getCanonicalName());
it was changed to check that the target.getCanonicalName() ends with "org.apache.logging.log4j.core.lookup.JndiLookup" this should protect against this vulnerability.

[wajda]

Please take a look at the PR #3. It adds shading supports and a few other things.