Live data from Hacker News

Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes

mac4n6.com

21–30 of 123 posts

Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes

#21
post #8

Please don't link to mac4n6, it serves malware on some page loads. The article author is aware of it but apparently doesn't have the ability to fix the issue

What kind of malware did you run into?

You can see it here — https://twitter.com/iamevltwin/status/976627634066132992

Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes

#22
post #2

Fixed in 10.13.2 - but wow, was High Sierra ever a sloppy release.

Sloppy and marketed as a stability build. There were hardly any new features in it.

Yeah, they just deployed a whole new FS to 100s of millions of users, in record time, with almost zero incidents.

Hardly any new features...

Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes

#23

Earlier quoted context omitted.

After doing a quick sweep of the network and processes, I didn't find anything overtly malicious (unless you count 6 MB pages for a blog, 150k lines for squarespace's JS, and 3000 rules over 400KB).

When I last examined it, the malware was loading from a domain called eventsbysteph. If the page still pulls js from there then the malware's still around (doesn't activate on 100% of loads)

I'm only getting typekit, squarespace, the auther's other domain for the blog, and google analytics -- with ublock off for all pages.

Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes

#25
post #22

Earlier quoted context omitted.

Sloppy and marketed as a stability build. There were hardly any new features in it.

Yeah, they just deployed a whole new FS to 100s of millions of users, in record time, with almost zero incidents. Hardly any new features...

[deleted]

Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes

#26
post #22

Earlier quoted context omitted.

Sloppy and marketed as a stability build. There were hardly any new features in it.

Yeah, they just deployed a whole new FS to 100s of millions of users, in record time, with almost zero incidents. Hardly any new features...

Well... Almost zero but not quite. I remember it causing a lot of trouble for us using Vagrant for development, since the upgrade automatically (and silently) converted the FS to APFS on supported devices and broke all Vagrant's synced folders that were using NFS. The bug was only fixed in 10.13.2. https://github.com/docksal/docksal/issues/377

Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes

#27

Earlier quoted context omitted.

Exactly. More to the point, even if it doesn't log it any more, I bet it's still on the command line itself.

The usual trick here is to pass it as an environment variable instead of cmdline, that can be done without much effort so they're probably doing that.

Bad idea

cat /proc//environ

Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes

#29

Earlier quoted context omitted.

The usual trick here is to pass it as an environment variable instead of cmdline, that can be done without much effort so they're probably doing that.

Bad idea cat /proc/ /environ

Wait, what's your threat model? Surely you're not imagining that you can pass data from one process to another without root being able to see it? (On Linux, since you're using /proc.)

Other users' processes can't see /proc/$pid/environ, unlike using cmdline.

Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes

#30

Earlier quoted context omitted.

Bad idea cat /proc/ /environ

Wait, what's your threat model? Surely you're not imagining that you can pass data from one process to another without root being able to see it? (On Linux, since you're using /proc.) Other users' processes can't see /proc/$pid/environ, unlike using cmdline.

Sure, it still leaves room for malware etc accessing data if it's running as the main user.

I think the better solution is to read it out of a wallet into stdin

Post reply on HN