RE: https://ruby.social/@mame/117640254153433278
Update your Ruby asap. This is really bad especially if it serves HTTP.
Updated Mastodon container images are coming soon.
RE: https://ruby.social/@mame/117640254153433278
Update your Ruby asap. This is really bad especially if it serves HTTP.
Updated Mastodon container images are coming soon.
@renchap are there workarounds that involve not updating ruby (yet) ?
@RGrunblatt this monkey patch makes the http exploit more difficult but requires a recent rack and testing with your own app: https://gist.github.com/byroot/db331487935e344a70cab1c41b722006
Best fix right now is really to update Ruby
@RGrunblatt using jemalloc might (not confirmed) make it harder to exploit or avoid the issue entirely. Any production deployment should use it as it really helps with memory usage, so that might be good to ensure you have it enabled
@renchap apparently rbenv install 4.0.10 isn't enough and some extra manipulations are needed to actually switch to it.
I edited .ruby-version and then ran bundle update which broke everything, and then after git reset --hard bundle install actually did something and now dashboard does show 4.0.10p0.
Wonder what the correct sequence of actions is!
@renchap Thanks for the heads up!
4.0.10 doesn't seem to be available yet through rbenv, do you confirm?
@oldestHouse not according to the information I got.
@renchap Et pour celleux qui n'utilisent pas Docker ? :blob_cat_mlem:
@lodart mettre à jour Ruby selon la méthode utilisée pour installer Ruby
@renchap How do you update mastodon's embedded ruby in non-docker environment? All I know about rbenv is cutting and pasting commands from mastodon's installation and upgrade instructions.
Edit: Never mind, new mastodon versions are up on github, so I can just follow normal upgrade procedures.
@renchap scary ! 😱 merci pour l’info !!