in reply to Re^11: Ideas for "fixing" PerlMonks 1.0
in thread Ideas for "fixing" PerlMonks 1.0
If I can apply the patches on that isolated node it'll take me probably a week, considering all edge cases and the weirdness of the monastery. ¹
If I have to wait for you guys to act, it'll take a month at least.
Sorry, no!
Maybe I'll find time next year to locally set up the old download version of the Everything engine and can develop it locally on my box.
Provided Everything::MAIL.pm is the same. Then you'll get a full node in one go, without patch/dev history.
Or maybe etj will do better and faster.
On another note:
I've reported a serious security issue in 2019 and provided code to patch Everything.pm.
No matter how you patch it - I don't really care anymore if disabled or optional - please patch it.
Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery
¹) The necessity to document and test it included.
There is also injection detection logic to report if someone tried to manipulate the parameters.
It's also limiting the time window and reset attempts to a fixed number per interval to block DNS and brute force attacks.
We are talking about hundreds of LOC.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^13: Ideas for "fixing" PerlMonks 1.0
by jdporter (Paladin) on Dec 20, 2024 at 22:07 UTC | |
by LanX (Saint) on Dec 21, 2024 at 01:36 UTC | |
by jdporter (Paladin) on Dec 21, 2024 at 04:21 UTC | |
by LanX (Saint) on Dec 21, 2024 at 11:20 UTC | |
by LanX (Saint) on Dec 21, 2024 at 13:38 UTC | |
by LanX (Saint) on Dec 22, 2024 at 18:41 UTC | |
|