in reply to Re^4: Ideas for "fixing" PerlMonks 1.0
in thread Ideas for "fixing" PerlMonks 1.0

... Is it as simple as [a bunch of really complicated sounding stuff] ...

Yes? :-D If you can write the code, I'm willing to create the db table(s) you'll need. (And I can help you write the code, wrt interfacing with the framework.)

Replies are listed 'Best First'.
Re^6: Ideas for "fixing" PerlMonks 1.0
by LanX (Saint) on Dec 18, 2024 at 14:35 UTC
    FWIW I have working and long tested code for the whole process of a safe password reset. (100/day over 9 years)

    Still needs to be tested in a second phase, if PM can be migrated to hashed (and longer) passwords.

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    see Wikisyntax for the Monastery

[reply]

      I extend the same offer to you. Let me know what table(s) you need, and then we can start creating the code nodes.

[reply]
        It's still work because I have to strip and rewrite things, (like passwords rules which are not enforced here + JS to check the passwords) and other proprietary stuff.

        I'm not very motivated to start a lengthy process if the monastery was not capable to hash the passwords in the first place.

        What would be the migration path?

        And I need to know the main mailing interface of PM. Seems like different gods implemented multiple attempts.¹

        Last but not least I would need a Dev environment to test effectively.

        Do I have the possibility to copy code into a node and run it directly?²

        It's a one file CGI, squeezing it into one node should be easy.

        Cheers Rolf
        (addicted to the Perl Programming Language :)
        see Wikisyntax for the Monastery

        Updates

        ¹) I can't find the code for Everything::MAIL.pm

        ²) or the right to locally apply patches

[reply]

In Section Perl Monks Discussion