this post was submitted on 28 Jan 2024
95 points (97.0% liked)

No Stupid Questions

35947 readers
2095 users here now

No such thing. Ask away!

!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules (interactive)


Rule 1- All posts must be legitimate questions. All post titles must include a question.

All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.



Rule 2- Your question subject cannot be illegal or NSFW material.

Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.



Rule 3- Do not seek mental, medical and professional help here.

Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.



Rule 4- No self promotion or upvote-farming of any kind.

That's it.



Rule 5- No baiting or sealioning or promoting an agenda.

Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.



Rule 6- Regarding META posts and joke questions.

Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.

On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.

If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.



Rule 7- You can't intentionally annoy, mock, or harass other members.

If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.

Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.



Rule 8- All comments should try to stay relevant to their parent content.



Rule 9- Reposts from other platforms are not allowed.

Let everyone have their own content.



Rule 10- Majority of bots aren't allowed to participate here.



Credits

Our breathtaking icon was bestowed upon us by @Cevilia!

The greatest banner of all time: by @TheOneWithTheHair!

founded 1 year ago
MODERATORS
 

I read an article about ransomware affecting the public transportation service in Kansas, and I wanted to ask how this can happen. Wikipedia says these are "are typically carried out using a Trojan, entering a system through, for example, a malicious attachment, embedded link in a phishing email, or a vulnerability in a network service," but how? Wouldn't someone still have to deliberately click a malicious link to install it? Wouldn't anyone working for such an agency be educated enough about these threats not to do so?

I wanted to ask in that community, but I was afraid this is such a basic question that I felt foolish posting it there. Does anyone know the exact process by which this typically can happen? I've seen how scammers can do this to individuals with low tech literacy by watching Kitboga, but what about these big agencies?

Edit: After reading some of the responses, it's made me realize why IT often wants to heavily restrict what you can do on a work PC, which is frustrating from an end user perspective, but if people are just clicking links in emails and not following basic internet safety, then damn.

you are viewing a single comment's thread
view the rest of the comments
[–] fidodo 15 points 10 months ago (3 children)

An advanced phishing attack can be incredibly hard to detect. Here's an example of a browser vulnerability that allowed malicious sites to spoof legitimate looking domains. It's been fixed since then, but it's a constant battle between fixing exploits and new ones being found. A sophisticated operator can come up with ways to trick even the most tech savvy user, and most users will fall for more obvious tricks than that.

[–] [email protected] 5 points 10 months ago* (last edited 10 months ago)

There's a new similar phishing attack thanks to Google and their .zip domain. Web browsers support a feature that lets you use addresses of the form protocol://username:[email protected]{.text}. That feature allows you to log in to domain.tld{.text} with the given credentials. When you combine that with Unicode forward slashes, you can craft addresses that look like https://microsoft.com/files/@windowsupdate.zip{.text}, where the part between https://{.text} and @{.text} is a username and the part after @{.text} is the actual address most likely used for malicious intends. My example uses normal slashes, so will lead to Microsoft's website and page not found error. windowsupdate.zip{.text} is a domain someone has registered, but leads to no-where as of today. PSA: Don't go to random web addresses you find on the Internet or elsewhere.

[–] [email protected] 4 points 10 months ago (1 children)

Oh yes, the Latin vs. Cyrillic characters trick! Now that you mention it, I remember watching a YouTube video about this. Scary shit.

[–] Archer 2 points 10 months ago

Homoglyph attacks!

[–] [email protected] 1 points 10 months ago (1 children)

How is this shit not fixed yet? That's literally undetectable phishing

[–] fidodo 6 points 10 months ago* (last edited 10 months ago)

It is fixed, if you follow one of their example links you should see a warning now. I was using it as an example of how there can be hard to detect exploits.

EDIT: it's fixed in Chrome. Just tried Firefox and they don't have a warning 😕