News for hackers. Stuff that matters.
Re:The Surreal Horror of Pam by kps on Tuesday November 09, 2021 @04:51PM (#29167998)
> because /etc/passwd is world-readable by design for some arcane reason that I can’t find on Google

Because it maps user IDs to names so that you can see names in `ls -l` and `who` and such.

Re:The Surreal Horror of Pam by notacoward on Tuesday November 09, 2021 @04:58PM (#29168081)
Also things like "finger" looking up their home directory and showing you their .plan file. Not saying it was a good choice then, let alone now, but the number of Chesterton's Fence violations in this presentation is pretty high.
Re:The Surreal Horror of Pam by lexicality on Tuesday November 09, 2021 @05:33PM (#29168446)
> the number of Chesterton's Fence violations in this presentation is pretty high

The article's tagged as satire, I'm not sure you should be expecting good logic and sources

Re:The Surreal Horror of Pam by notacoward on Tuesday November 09, 2021 @07:09PM (#29169334)
Is there anything besides the tag to indicate that it's satire, in a sense that any teacher or student of writing would recognize? People have used "just kidding" as a way to duck criticism since time immemorial, but that doesn't mean we have to accept it unthinkingly.
Re:The Surreal Horror of Pam by xena on Tuesday November 09, 2021 @07:12PM (#29169365)
> This is a partially satirical talk. It is intended to be mostly factually accurate, however some of the details are stretched for comedic effect.

I'd think this would cover all the bases. But what do I know, I just wrote the talk.

Re:The Surreal Horror of Pam by notacoward on Tuesday November 09, 2021 @08:54PM (#29170218)
Yes, you did, and it was a good talk. I actually did enjoy the snarky tone. PAM is a mess. On the other hand, I don't think that disclaimer really does cover all the bases. You yourself say it's partially satirical, implying that other parts are sincerely meant. Why shouldn't those be subject to the same discussion, correction, or even criticism as any other sincerely meant opinion in any other thing linked here? I'm pretty sure you can handle that back-and-forth better than Sir Lexicality gives you credit for.

And if anyone's still offended: my comments are partially satirical too. There, I'm immunized.

Re:The Surreal Horror of Pam by butwhywhyoh on Tuesday November 09, 2021 @09:05PM (#29170289)
This is the perfect cover to do whatever you want at all times.

I made an incorrect statement? Don't worry, I _meant_ to get that part wrong.

This part here that was insightful and you enjoyed? I meant that part 100%.

[dead]
Re:The Surreal Horror of Pam by notacoward on Tuesday November 09, 2021 @09:31PM (#29170415)
Hey, I'm supposed to be the Bad Guy here, and even I think that was uncalled for.
Re:The Surreal Horror of Pam by dogecoinbase on Tuesday November 09, 2021 @11:59PM (#29171239)
Play Devil's Advocate, and devils sometimes show up to be advocated for.
Re:The Surreal Horror of Pam by shawn-butler on Tuesday November 09, 2021 @09:59PM (#29170568)
Just giving clear non-satirical and honest feedback. The basic facts/history are incorrect. Not to mention the not-so implicit disrespect to the contributors (Sun, lolz! C modules oh-no omgz).

If I was watching this in a 30-second tiktok maybe I would have thought it was funny, or maybe the audience for the talk was expecting such low-grade content? Can't say I wasn't there.

Re:The Surreal Horror of Pam by pxc on Wednesday November 10, 2021 @10:40AM (#29175839)
On the other hand, if it hadn't been playful and glib about the decisions that led up to PAM as we know it, we might have had fewer of these lovely greybeards pop up to teach us some PAM and Unix history in the discussion :)

maybe Xe can address their comments in a followup, perhaps even after consulting with them a bit on the project itself

Re:The Surreal Horror of Pam by throwawayboise on Tuesday November 09, 2021 @05:10PM (#29168197)
And the sensitive parts were split off into the root-only /etc/shadow a long time ago.
Re:The Surreal Horror of Pam by Spivak on Tuesday November 09, 2021 @05:27PM (#29168376)
I mean anything that happened in the 90's seems to be considered "yesterday" in computing history terms.
Re:The Surreal Horror of Pam by mjevans on Tuesday November 09, 2021 @09:31PM (#29170417)
That would be more like E.G. the 1950s or 60s in Aviation terms, or perhaps the 1920s in electricity terms.
Re:The Surreal Horror of Pam by saghm on Tuesday November 09, 2021 @07:08PM (#29169328)
Sounds like maybe "passwd" wasn't the best name for this file, then
Re:The Surreal Horror of Pam by jandrese on Tuesday November 09, 2021 @10:51PM (#29170876)
Not anymore, but it is way too late to change it now, especially since it has been user readable since it was created.

It's really just "accountdetails" now, with the real password living in a different file.

Of course I remember the old "yp" system that would blast the whole file with passwords over the network to anyone who asked. The old Unix guys had a lot of faith in their hash algorithms.

Re:The Surreal Horror of Pam by fulafel on Wednesday November 10, 2021 @12:37AM (#29171443)
Also because there wasn't anything deemed secret there, as the passwords were salted and encrypted. Knowledge about password crackers and crypto became widespread only much later. The pw encryption algorithm was also pretty feeble, a version of some ww2 era rotor machine IIRC.
Re:The Surreal Horror of Pam by Spivak on Tuesday November 09, 2021 @05:22PM (#29168318)
But that doesn't really answer the question. Nothing was really stopping a setuid program from granting access to the non-sensitive bits of the passwd/group files.
Re:The Surreal Horror of Pam by p_l on Tuesday November 09, 2021 @05:25PM (#29168347)
Efficiency (spawning setuid program for every line printed by ls -alv is a bit too much), and you don't want to make too privileged programs too (suid ls?)
Re:The Surreal Horror of Pam by Spivak on Tuesday November 09, 2021 @05:29PM (#29168398)
I mean the hypothetical program would have just dumped the whole file minus the sensitive bits.
Re:The Surreal Horror of Pam by mindwok on Tuesday November 09, 2021 @05:52PM (#29168640)
Exposing a setuid program that prints the file would be more dangerous though. The result is the same (you can read /etc/passwd) except now you have a vector for gaining root access through an exploit to this setuid program.
Re:The Surreal Horror of Pam by chungy on Tuesday November 09, 2021 @07:19PM (#29169439)
And then you've reinvented /etc/shadow but worse. :)
Re:The Surreal Horror of Pam by a-dub on Tuesday November 09, 2021 @06:31PM (#29168992)
see getpwnam, which was already public for years and linked by everything. it queries one record at a time.
Re:The Surreal Horror of Pam by tremon on Tuesday November 09, 2021 @09:37PM (#29170434)
getpwnam() gets its data by parsing /etc/{passwd,shadow}[0]. It isn't a magical system call that elevates the privileges of the calling program.

[0] assuming your nsswitch says so

Re:The Surreal Horror of Pam by a-dub on Wednesday November 10, 2021 @11:31AM (#29176586)
yeah. agree, was merely pointing out the public interface for querying passwd records for the purposes of highlighting why said interface might be another reason to reconsider the proposed idea of a setuid shim that reads a read protected /etc/passwd that contains password hashes and returns only the public components.
Re:The Surreal Horror of Pam by ectopod on Tuesday November 09, 2021 @06:11PM (#29168846)
...and nobody thought of dictionary attacks when it was designed.

So it was world readable.