this post was submitted on 10 Jul 2023
378 points (93.0% liked)

Selfhosted

40313 readers
237 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

This issue is already quite widely publicized and quite frankly "we're handling it and removing this" is a much more harmful response than I would hope to see. Especially as the admins of that instance have not yet upgraded the frontend version to apply the urgent fix.

It's not like this was a confidential bug fix, this is a zero day being actively exploited. Please be more cooperative and open regarding these issues in your own administration if you're hosting an instance. 🙏

you are viewing a single comment's thread
view the rest of the comments
[–] Demigodrick@lemmy.zip 4 points 1 year ago (2 children)

There is already an update. 0.18.2-rc1

You can apply it now.

[–] ablackcatstail@lemmy.goblackcat.com 6 points 1 year ago (2 children)

I will have to wait until I can get home from work. Work does deep packet inspection and blocks SSH. I've tried doing SSH on port 993, one I know for a fact is open because I get my email that way on my phone and I still get a connection refused. Bunch of fascists!

[–] midas@ymmel.nl 3 points 1 year ago (1 children)
[–] ablackcatstail@lemmy.goblackcat.com 2 points 1 year ago (1 children)
[–] BlueBockser@programming.dev 2 points 1 year ago (1 children)

You could try using a VPN or some other kind of proxy which wraps your SSH traffic to prevent packet inspection. Then it should look like normal UDP traffic ;)

They block UDP traffic too. I tried some things like that.

[–] redcalcium@c.calciumlabs.com 1 points 1 year ago (1 children)

Given how strict it is, I assume your company implements some sort of certification such as ISO27001 and really stick their gun on it? So, can you like, not using your company's wifi on your phone if it's heavily monitored? Or is the cell reception poor at your office?

[–] ablackcatstail@lemmy.goblackcat.com 2 points 1 year ago (1 children)

I use my employer's guest wifi. Right now I can't afford adding the hotspot to my plan.

[–] redcalcium@c.calciumlabs.com 2 points 1 year ago

No need to enable hotspot on your phone. Just install Termux from f-droid if you're on android, or Prompt if you're on iOS, and use SSH directly from your phone.

[–] robotrash@lemmy.robotra.sh 1 points 1 year ago

This is probably a dumb question but I used the Ansible install for Lemmy and just did a git pull and --become again but UI wasn’t updated so I assume 0.18.2 isn’t in release yet (which is fine) but is there documentation on updating UI? I see where it’s showing in the docker-compose.yml file but I am uncertain what to do after changing it there (or if that’s the right place to change it).