Thanks for this useful component, Walter.
However, v4.0.0 has a few bugs and the instructions about putting the right code into the joomla files is not very accurate. Here's a few fixes for v4.0.0 I've done to make it work for me.
in file: inserImage.php, function:
function privateinsertSecurityImageInternal($packageName, $itswidth, $itsheight, $size, $desiredPluginName = null, $desiredPluginVersion = null) {
changed:
$insertstr = "<script type='text/javascript' src='".$mosConfig_live_site."/components/com_securityimages/js/securityImages.js"."'/>".
to:
$insertstr = "<script type='text/javascript' src='".$mosConfig_live_site."/components/com_securityimages/js/securityImages.js"."'></script>".
Also in pluginsA/core/1.1/adminpanel.php I had to add this code at line 80 to get the admin for to save the parameters to the config file:
foreach ($params_request as $val) {
$$val = mosGetParam($_REQUEST, $val, '');
}
Also, I realised that "_try" and "_refid" gets appended automatically to the package name that is passed in insertSecurityImage(packagename). So the instructions need to change for that. Also if you use the joomla.login.php patch for the login, you have to pass "security_joomlalogin" as the package name in the calls on your login form.
Apart from those little things (which can annoy people who don't know php) it's all good. Those are the problems that I've encountered when just starting to try out this component.