this may be useful for some here:
If during the build phase on docker you encounter
```
Bundler::HTTPError Could not fetch specs from https://rubygems.org/ due to underlying error <Net::OpenTimeout: execution expired (https://rubygems.org/specs.4.8.gz)>
```
Then an unsatisfactory workaround is to temporarily disable IPv6 on your docker daemon.
@pyreneer @Mastodon You pulled the container when it was already pushed, but the GitHub action that builds and uploads it took 2:15 hours which is not great, especially in case of critical security issues (it's possible to archive arbitrary code execution in any instance simply by making a toot...)
https://github.com/mastodon/mastodon/actions/runs/5475883545/jobs/9972611758
@sven @Mastodon it’s the same about docker. The issue here is on the mastodon’s side on slow building of containers. Furthermore, on a bare metal machine in case a dependency changes (and it did change here as well, afaik minimum node version is now 18) a simple version number change is not enough for instantly updating.
The security impact of running without containers remains
So after looking at the mastodon security report / code commit I think I might have some idea (admittedly vague / incomplete) of how it worked.
No spoilers though I guess. Wait what is the etiquette about speculating about recent security issues anyway?
@Mastodon Thanks for the new version!
The upgrade instructions still need some TLC though https://mastodon.scot/@gunchleoc/110667501611817208
@[email protected] Could you please clarify this bit from the upgrade instructions? " The change is about setting Content-Security-Policy: default-src 'none'; form-action 'none' and X-Content-Type-Options: nosniff on assets." Does this mean we change this section only: location ~ ^/assets/ { Or should we change more sections? Thanks! #MastoAdmin
@Bouncing1981 @Mastodon No worries! 🙂
And this might answer your other question (I was actually also curios about the vulnerabilities they patched)
https://arstechnica.com/security/2023/07/mastodon-fixes-critical-tootroot-vulnerability-allowing-node-hijacking/
I think the important part in this context is:
> There’s no action individual Mastodon users need to take other than to ensure that the instance they’re subscribed to has installed the updates.
@Mastodon I have absolutely no idea how to update my server 😅
I built it kinda for fun, if anyone has any guides I’d love to see them thanks!
I pretty much followed this guide to set mine up (this was before there was the 1 click install)
https://www.linode.com/docs/guides/install-mastodon-on-ubuntu-2004/
@mikaelacaron did you use the marketplace image on Linode? If so I used this guide to upgrade mine: