| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This reverts commit aff2234a87c43c44b86d6177d9ca78746a09642e.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 2 new aarch64 build nodes named lavand and majax
- 2 new build nodes named houdini and garcimore
- a deploy server named mandrake
- a web server named webb
- a repo server named melies
- update DNS and monitoring
- prepare to integrate the new build nodes
Preparation for 2 new x86_64 build nodes
Adds pp file for majax
IPs added for garcimore and houdini
update DNS
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The mgagit script was previously run after the SSH keys script, but only
if an SSH key was updated. That meant that any group changes were not
reflected until after someone changed an SSH key.
Decouple the running of the two scripts since they are not (completely)
dependent on each other.
|
| |
|
|
| |
engine (Fix)
|
| | |
|
| |
|
|
|
|
|
| |
These provide potentially sensitive information, so allow access only
from localhost.
Reported-by: bas
|
| | |
|
| |
|
|
| |
These could hold secrets so should not be world-readable.
|
| |
|
|
|
| |
E-mails are now sent in both plain text and HTML for broader maintainer
appeal.
|
| |
|
|
|
|
|
| |
- Send messages also when packages are moved to obsolete
- Mention the maintainer name explicitly in the message
- Be more robust in handling a malformed maintdb.txt with duplicate
entries
|
| |
|
|
|
|
|
| |
If someone other than the registered maintainer of a package submits a
change to that package, notify the maintainer. These notifications are
skipped for robot changes and bulk changes where many packages are
changed at once.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
These were intended to be enabled only on svnweb.mageia.org but
mirrors.mageia.org (and a couple others) were using the same template.
The changes in commit 6802d174 caused the anti-robot mitigation to be
triggered when urpmi downloaded $MIRRORLIST from a URL like
https://mirrors.mageia.org/api/mageia.9.x86_64.list?reason=update which
contains a query part. Fork the template so only svnweb gets these
features, which was the original intent.
|
| |
|
|
|
| |
Try to reduce svnweb load by making anything other than a plain path
require an anti-robot cookie.
|
| | |
|
| |
|
|
| |
The disk just fills up too quickly.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This fails with "Unable to open the chart datafile ./data/mining/0."
because that file isn't writable by apache. Rather than trying to fix
those permissions, just disable the script since nobody seems to be
using whatever statistics are being collected ("data about bugs to be
used in Old and New Charts").
This page has some information about the problem:
https://serverfault.com/questions/182139
|
| | |
|
| |
|
|
| |
Any additional URL parameters after a & were previously dropped.
|
| | |
|
| |
|
|
|
| |
This reduces the possibility of a malicious URL redirecting to another
domain.
|
| |
|
|
|
| |
The intent of this cookie isn't actually to track sessions, so eliminate
any privacy impact by using a fixed number instead.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
If an expensive request comes in from anyone without a cookie attached,
redirect to a page where the cookie is set using JavaScript, then
redirect back. This should block robots from these paths, most of which
do not support JavaScript. The collateral damage is that a JavaScript
browser is now required for users to access those paths. The contents
of the cookie is not currently checked, merely that it is set.
|
| |
|
|
|
|
|
| |
These two don't seem to contribute much to the load seen when robots
start hitting svnweb that hard. Also, remove a separate query block that
seems to not help much (and which was hard to find in a different
location in the file).
|
| |
|
|
|
|
|
| |
The last range was actually another Google bot, which clearly doesn't
support Crawl-Delay:. Rather than block one IP range, which isn't going
to work long-term since they have so many ranges, block only expensive
operations via its new User-Agent: string instead.
|
| | |
|
| |
|
|
| |
These comprise roughly 20% of current requests.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
According to upstream a reasonable starting value for shared_buffers is 25% of the memory which would be actually 8GB in sucuk.
|
| | |
|
| |
|
|
| |
Most probably Presto is not used as user agent in browsers used by potential users of Mageia.
|
| | |
|
| | |
|
| | |
|
| | |
|