Hello,
For information, there's this script: https://corz.org/server/tools/anti-hammer/?. After, it's just a start, against such attacks. As this script is open-source, it can evolve according to your needs (this script need to be installed, either via a `php_value auto_prepend_file command "/home/etc.../anti-hammer.php"` in the Apache server's .htaccess settings, or in the first line of the?Php source code inside the `bootstrap.php` file).
This script limits @IP's consumption of resources, per each @IP. When one @IP hammers too much, the said @IP is warned that it's abusing CPU consumption, and then,?the said @IP is? automatically banned for 12h ,or 24, or ... hours (Cf. config). The @IPs are logged, too: so, it's possible to insert them manually in a `deny from @IP` inside the .htaccess.
Regards.
?
De :
A :
Envoy?: samedi 1 Mars 2025 12:00
Objet :
?
Send lazarus mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit https://lists.lazarus-ide.org/listinfo/lazarus
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific than "Re: Contents of lazarus digest..."
Today's Topics:
1. Re: New MacOS user (Matthieu Giroux)
2. Re: Forum login times out (gabor)
3. Re: Forum login times out (Michael Van Canneyt)
----------------------------------------------------------------------
Message: 1
Date: Fri, 28 Feb 2025 17:18:07 +0000 (UTC)
From: Matthieu Giroux
To: Juha Manninen via lazarus
Subject: Re: [Lazarus] New MacOS user
Message-ID:
Content-Type: text/plain; charset="utf-8"
I am searching Mac OS packagers and testers with www.Ancestromania.eu .
Matthieu Giroux 13 Rue Fr Tanguy PRIGENT A.15 - 35000 RennesT?l : 09 61 37 01 82 - 06 44 733 008 http://www.liberlog.fr
Le vendredi 28 f?vrier 2025 ? 11:10:52 UTC+1, Juha Manninen via lazarus a ?crit :
On Fri, Feb 28, 2025 at 8:56?AM DougC via lazarus wrote:
I'd really like to contribute to the Lazarus and FPC projects, but I need to get familiar with them more before making suggestions. I think I would be most helpful in editing documentation, but we will see.
While I do this I think it will be worthwhile to test if the current state of the documentation is as good as we want it to be. So, I'll be doing what I think are smart steps and reporting on the problems I encounter. That way we can turn around and clarify instructions where it seems necessary.
There is HTML documentation for the public APIs, functions and components.Other instructions for installation and usage etc. are in a community wiki. It has the same problems as any?community wiki, namely poorly structured and partly duplicate data spread around because there is no editor-in-chief.If you make corrections there, observe how the bigger structure looks. Don't be afraid to remove data when it is outdated or duplicate. Juha
