Hi GIJOE,
Quote:Thanks for your attention. Your module is one of the very best and that what I have been advocating to the core developers to include in the CORE and integrate it into such a manner that the security is enhanced.

However, the Nursery of Core Developers is currently going through a communist wave and this fever will last for sometime.

BTW, I am using 2.2.5RC2.

In the meantime there are further problems:

After I updated the Protector i.e. from 2.57 to 3.04, the loginname is not being shown anywhere, i.e. in the templates, I print like "Hello loginname", etc. This is gone after the upgrade. Also the CBB module in the version 3.05 does not show any name as a user in all the forums. People can write the posts though.

I checked the template_c and found out the following:

Hi <?php echo $this->_tpl_vars['xoops_uname']; ?>

This was and is the same, i.e. xoops_uname is not displayed after the protector update anywhere!

Do you have any suggestions? I have kind of tried to put the module to a minimum security level and there is no change.

There was some logging as to spam comments showing as follows:

URI SPAM /modules/news/comment_post.php SPAM POINT:19

Further, regarding the bots signing, I placed a thought for your consideration as below @ SF.net. If this could be a solution, it would be possible to have the protector responsing to it...

My recommendation...