Excellent - this security change will be in the SVN on the next update - the newest version will allow the Admin to choose whether or not the GMod will be allowed to ban IP addresses from the error log if the GMod does NOT have Guardian access.

In the meantime, it's working and that's what counts.

i maked see-FIXED!!!

the latter could not do I do not understand what exactly is necessary and where it is written it is not clear, especially until it is finalized, decided not to do anything from the latter

In AdminEdit.pm replace the previously suggested code with:

ipban_err => '$FORM{'errorlog'}',
 blockip => '$FORM{'setup_guardian'}',
 guardian_block => '$FORM{'setup_guardian'}', 

Replace ErorLog.pm with the one in the zip - the GMod/Guardian/IP banning blocking still needs some work.

What I needed to know: guardian_block  not permitted.
GMod Setting - Guardian off.

so fuck to send if you test coordinator to me go and themselves in the urinal try to enter ipi 46.101 or any api, then dilute, it's better to feel for the udder this guardian?

You'll need to either post a picture or the actual error log entry because there is no 'guardian err'

thank you, changed and saved the saved-saved-there's a simple ban ai-write-ai-pi and here's the block in the Guardian-the error is new after the fix

you do not have access to guardian err-

Did you make the recommended changes to AdminEdit.pm and did you then go to the Global Moderator access section and save the settings to rewrite the GMod access settings?

Basically - anyone who has access to viewing the error log should logically have access to the various error log bans.

If enabled, Guardian blocks are written to the .htaccess file in cgi-bin/yabb2. Regular bans are stored in Variables/banlist.txt

However, the easiest way of dealing with an IP block or ban is to login from a different IP address - like a coffee shop - and take care of the problem from within YaBB.

But, if you don't want to risk your GMods banning YOU, don't give them access to Guardian OR the error log.

However, I may need to go and look at how to better configure GMod access if they do have access to the error log but don't have access to Guardian.

exile is access and guardian no access writes

У Вас нет доступа к этой части форума. ipban_err -


there is no access to this part of the forum wrote? -but why then does the coordinator see it-I think if it sees and can fulfill actions, then there is access?

and in which branch are the blocked ones written to ftp? -can just erase with ftp and all

Ah, an actual bug.

In Security.pm find

        $page = $INFO{'page'}; 

and replace with

        $page = $INFO{'page'} || q{}; 

in Admin/AdminEdit.pm find

remghostpmattach => '$FORM{'managepmattachments'}', 

and add below it

 setup_guardian2 => '$FORM{'setup_guardian'}',
 ipban_err => '$FORM{'errorlog'}',
 blockip => '$FORM{'errorlog'}', 

Once that's done, go into Global Moderator Access and resave your settings.

Just remember, anyone with access to the error log or Guardian has the potential of IP blocking the admin.

Обнаружена Ошибка! Use of uninitialized value $page in concatenation (.) or string at Sources/Security.pm line 172

Coordinator-error log-send an ip does not work but add to the black list hell Guardian error above

Rucola wrote on Dec 12^th, 2017 at 3:50pm:

  Huh?