this post was submitted on 10 Jul 2023
174 points (97.8% liked)
Lemmy.ca's Main Community
2814 readers
2 users here now
Welcome to lemmy.ca's c/main!
Since everyone on lemmy.ca gets subscribed here, this is the place to chat about the goings on at lemmy.ca, support-type items, suggestions, etc.
Announcements can be found at https://lemmy.ca/c/meta
For support related to this instance, use https://lemmy.ca/c/lemmy_ca_support
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So, as an average, less-technical, Lemmy user (this is my backup for now).
What can or should I do to stay safe?
https://lemmy.world/post/1290412?scrollToComments=true
The affected instances are coming back and the vulnerability being mitigated. Apparently no personal data was compromised. So you should be fine.
Id use an app you trust for now
On a site you have to sanitize your data, on a native app you'd have to go out of your way to render this kind of thing...wefwef/voyager is actually a web page (and they might or might not be sanitizing their inputs), the other top options are probably using libraries to do it, and data sanitation is pretty basic. Literally web dev 101. They'd have to choose a very full-featured rendering library that also entirely ignores security, or they'd have to have rolled their own
At least now I know why my renderer has been so annoying about the warnings the last couple days...
For any devs that read this - this is a great example of why you can't trust anything coming off a federated network. Type check and sanitize all your inputs, always. We need to get away from trust - this isn't a trustful situation
Luckily, this was more of a warning than an actual attack - and there will be actual attacks. We have to be defensive - always - every time at every level.
And Flemmy will be that, once I feel good releasing it (2 features left before I'm out of reasons to procrastinate). It'll be just me, always