Asklemmy

51678 readers

390 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 6 years ago

MODERATORS

How to evaluate software security? (lemmy.ml)

submitted 1 week ago by QuestionMark@lemmy.ml to c/asklemmy@lemmy.ml

6 comments fedilink hide all child comments

Without going through the whole source code. You can just look up the information on the web, but how do you know whether to trust that information?

(Assuming no security audit has been listed on the website, or the audit seems outdated.)

you are viewing a single comment's thread
view the rest of the comments

[–] communism@lemmy.ml 5 points 1 week ago

I mean someone pointing out a vulnerability in a piece of software should be a falsifiable claim, e.g. "they store their passwords in plaintext"—if it's foss then just look at the source. You don't need to read the entire source because you have been given a specific part of the code to look at. You need to only look at the process between the software receiving a password and its query to the database.

And if it's not foss I don't use it, and the claim may be unfalsifiable for an outsider who isn't bothered to try reverse engineering.