@Hubzilla Support Forum Apparently there is a workaround for this: https://j

⁨1⁩ ⁨like⁩

Submitted ⁨⁨15⁩ ⁨hours⁩ ago⁩ by ⁨buckaroo@hub.netzgemeinde.eu⁩ to ⁨adminsforum@hubzilla.org⁩

@Hubzilla Support Forum Apparently there is a workaround for this: https://jackalsyn.com/posts/php-up-2026.html

So
session.upload_progress.enabled = Off
can/should be set until the patches/upgrades are ready

Comments

Sort:hotnew top

jrp@hub.kliklak.net@hub.kliklak.net ⁨4⁩ ⁨hours⁩ ago
@Mark Nowiasz Where would one apply this partly fix of yours then exactly? Thank you in advance.
original
- harald@hub.volse.no@hub.volse.no ⁨4⁩ ⁨hours⁩ ago
  @*jayrope Add it to your php.ini file.
  original
  - jrp@hub.kliklak.net@hub.kliklak.net ⁨3⁩ ⁨hours⁩ ago
    @Harald Eilertsen Done, thank you. HZ has one, while mot of my CMS installs to not have such file in their root dirextory, though.
    original
    -> View More Comments
harald@hub.volse.no@hub.volse.no ⁨14⁩ ⁨hours⁩ ago
@Mark Nowiasz Thanks, that's a likely stopgap measure for one of the problems, the other is not so easily mitigated. It's still advisable to upgrade as soon as the patch is dropped.
original
- buckaroo@hub.netzgemeinde.eu ⁨14⁩ ⁨hours⁩ ago
  @Harald Eilertsen Of course. But since there's no upgrade available yet it can't hurt to (temporarily) disable session.upload_progress :-)
  original
  - harald@hub.volse.no@hub.volse.no ⁨14⁩ ⁨hours⁩ ago
    @Mark Nowiasz Absolutely agree! Definitely apply the mitigation, but be aware it's not sufficient for all (most?) attack vectors.
    original