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.
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.
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.
[This comment has been deleted by an automated system]
you don't need to be root to read
/etc/passwdAre you sure? What do you get when you run
$ cat /etc/passwdin terminal? Just paste the results here 😇Edit: to anyone reading this on the future, don't actually do this, it was a joke
yup pretty sure
😉
Weird, all I see is *******
Since you told me not to. There isn't a risk on most linux systems; passwords were moved to /etc/shadow a long time ago. It only leaks the names of your users and largely useless info for most attackers:
Well it's not completely useless. It offers some insights into the system. Which service accounts exists, what usernames are used.
If an attacker finds a valid username they can then start bruteforcing the password.
From your account list we can see you have sshd and xrdp. Do they both provide the same kind of bruteforce protection? Are there any recent exploits for either?
That’s because passwd doesn’t store the password hashes. Just user names.
Yeah, seems highly unlikely to ever yield any results. Even if you did manage to read a file, you have to get lucky finding a password hash in a rainbow table or the password being shit enough to crack.
I cracked the BMC on my workstation motherboard by binwalking the publicly available firmware and finding, to my delight and dread, that the built in root user password was laughably weak. If a top5 motherboard manufacturer is still doing shit like that, users are too.
I also work in support and have seen first hand the bananas things people do, even smart people that should know better