this post was submitted on 29 Jun 2023
30 points (100.0% liked)

Technology

37728 readers
653 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

Found the error Not allowed to load local resource: file:///etc/passwd while looking at infosec.pub's communities page. There's a community called "ignore me" that adds a few image tags trying to steal your passwd file.

You have to be extremely poorly configured for this to work, but the red flags you see should keep you on your toes for the red flags you don't.

you are viewing a single comment's thread
view the rest of the comments
[–] farthom@lemmy.ca 7 points 1 year ago (8 children)

Holy shit this is kind of unsettling. Though I would expect ALL major browsers to reject reading any local files like this..... would this kind of thing actually succeed somewhere/somehow?

[–] Rooster@infosec.pub 4 points 1 year ago (7 children)

If you ran your browser as root and configured your browser to load local resources on non-local domains maybe. I think you can do that in chrome://flags but you have to explicitly list the domains allowed to do it.

I'm hoping this is just a bad joke.

[–] fox@vlemmy.net 1 points 1 year ago (3 children)

you don't need to be root to read /etc/passwd

[–] trachemys@iusearchlinux.fyi 4 points 1 year ago

That’s because passwd doesn’t store the password hashes. Just user names.

load more comments (2 replies)
load more comments (5 replies)
load more comments (5 replies)