Everything's been migrated to the new server and ready to change DNS except we're waiting on mailman (2->3 migration) and sudohumans (only works with ancient nodejs). I've got mailman covered, but nodejs experts, please help! I could probably figure it out but I'd rather not. Email me for login info, thanks. On Thu, Nov 25, 2021 at 12:52 AM Jake <jake(a)spaz.org> wrote: affect wrote: time to prevent security warnings.

Sudo-humans is currently using nodejs 0.10.29, which was released 2014-06-09. This version was already pretty decrepit when I installed the server a year later: debian jessie, which was brand new in 2015, is now far past EOL, and cannot be updated. I doubt that anybody has even bothered to compile nodejs 0.10.x for newer OS versions. Nodesource goes back to 12.x (released 2019). So our options are: * do nothing, continue running outdated, unmaintainable server forever * migrate everything but sudo-humans, leave it running at humans.sudoroom.org, pay 2 VPS bills indefinitely * spend time and energy dockerizing the whole mess to run sandboxed on the new server * spend time and energy figuring out how to compile nodejs 0.10.x for newer debian * fix sudo-humans What's the plan, folks? A balloon payment of tech debt is now past due. On Thu, Nov 25, 2021 at 8:43 PM Charles Hughes <c.hughes87(a)gmail.com> wrote: > > I tried looking into upgrading the dependencies of sudo-humans a while ago and it is not arbitrary to do unfortunately. > > On Thu, Nov 25, 2021 at 12:27 PM Yardena Cohen <yardenack(a)gmail.com> wrote: >> >> Everything's been migrated to the new server and ready to change DNS >> except we're waiting on mailman (2->3 migration) and sudohumans (only >> works with ancient nodejs). I've got mailman covered, but nodejs >> experts, please help! I could probably figure it out but I'd rather >> not. >> >> Email me for login info, thanks. >> >> On Thu, Nov 25, 2021 at 12:52 AM Jake <jake(a)spaz.org> wrote: >> > >> > I heard we need help migrating the server to its new instance? >> > >> > apparently there are major issues of node upgrade which are going to affect >> > sudo-humans, which is important because that's how we accept payment from >> > everyone? >> > >> > who is available to help? >> > >> > thank you >> > -jake >> > >> > On Fri, 19 Nov 2021, Yardena Cohen wrote: >> > >> > > I know. I'll be migrating the server. I was waiting til the last >> > > second to be polite... >> > > >> > > >> > > On Fri, Nov 19, 2021 at 7:53 PM danarauz(a)gmail.com <danarauz(a)gmail.com> wrote: >> > >> >> > >> "https://sudoroom.org >> > >> >> > >> SSL Expiration Reminder >> > >> The SSL certificate for this website will expire in 1 days. Renew in time to prevent security warnings. >> > >> Renew in time to prevent your visitors from receiving errors. >> > >> >> > >> Valid from 2021-08-23 until 2021-11-21" >> > >> >> > >> >> > >> >> > >> _______________________________________________ >> > >> sudo-sys mailing list >> > >> sudo-sys(a)lists.sudoroom.org >> > >> https://sudoroom.org/lists/listinfo/sudo-sys >> > > _______________________________________________ >> > > sudo-discuss mailing list >> > > sudo-discuss(a)lists.sudoroom.org >> > > https://sudoroom.org/lists/listinfo/sudo-discuss >> > >

So the old instance is still accessible at https://humans.sudoroom.org/ and I set up redirects, but logging in is now broken. Trying to log in returns "not a POST". I believe this is because some urls are hard-coded. Even with redirects, my guess is it's triggering some csrf protection somewhere. I could be wrong. Both sudoroom and CCL use this thing to make money. This is serious. Help would be very appreciated. Meanwhile, substack made a valiant effort to get sudo-humans working with node 17.x. We got partway, at least the front page displays now, but it still crashes when you try to do anything. _______________________________________________ sudo-discuss mailing list -- sudo-discuss(a)sudoroom.org To unsubscribe send an email to sudo-discuss-leave(a)sudoroom.org