Earlier quoted context omitted.
Not to disagree, but could you provide some references to the statement?
If you run the ps command you can see all processes with all the command line arguments. They’re not secret, which is why you shouldn’t put passwords there. Now typically these processes only run for a short time so it’s difficult to catch passwords manually but it’s predictable so a script can.
Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes
91–100 of 123 posts
Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes
#92Earlier quoted context omitted.
My theory: the NeXT developers who were around for osx v10.0 and around then have all retired.
I understand what you're trying to say but still, 10.0 was quite unusable at the time due to performance and stability issues ;-)
Most of worst issues were sorted out by 10.1.
Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes
#93Earlier quoted context omitted.
The main feature is that it is a modern filesystem that doesn’t carry around 25 years of baggage.
That doesn't mean anything other than "it's new which is somehow better."
Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes
#94Earlier quoted context omitted.
If you run the ps command you can see all processes with all the command line arguments. They’re not secret, which is why you shouldn’t put passwords there. Now typically these processes only run for a short time so it’s difficult to catch passwords manually but it’s predictable so a script can.
So what is the proper way?
Note that you do need to take care to clean up the environment if you create new, unprivileged subprocesses or these secrets may leak.
Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes
#95That's pretty bad. It's been known for decades on other Unix systems that you shouldn't pass passwords by command line parameter, or even support doing so. I guess no-one told Apple.
By my estimation, I would guess the number is smaller than people think for a few reasons.
1. How many people who aren't technically saavy have external drives at all? If they do, it's probably a Time Machine volume. Which leads me to my second point...
2. Directory hardlinks - the tech which makes TM work - don't exist on APFS, so a fair number of these drives are probably still using HFS+, and last I checked, external SSDs of any sufficient capacity are still pretty costly, which brings me to the last point...
3. Given that APFS is really SSD-only (with a small asterisk for Fusion Drives), converting a TM volume on a spinning disk is a recipe for pain.
I'm not excusing the bug, only reiterating that its effect is probably less than you might imagine among people who aren't nerds (or HN readers for that matter).
Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes
#96What exactly happened to macOS development at Apple? There's always bad luck but Apple has had multiple very visible and very serious vulnerabilities over the last few quarters. They've made multiple grave errors with encrypted volumes. I don't think Microsoft with Bitlocker or Linux with dm-crypt has ever made mistakes as bad as Apple has made here and multiple other times. Forget the stability issues, a lot of the…
Working full time on macOS might not be all that exciting, but it's the foundation that holds the rest of the house up.
Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes
#97What exactly happened to macOS development at Apple? There's always bad luck but Apple has had multiple very visible and very serious vulnerabilities over the last few quarters. They've made multiple grave errors with encrypted volumes. I don't think Microsoft with Bitlocker or Linux with dm-crypt has ever made mistakes as bad as Apple has made here and multiple other times. Forget the stability issues, a lot of the…
Didn't Apple essentially get rid of their MacOS team by taking them off it full time and putting them into the iOS team? (So they essentially had to apply their time between the 2).
Got to pay off that debt one of these days, but 'not today' I guess...
Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes
#98Earlier quoted context omitted.
If you run the ps command you can see all processes with all the command line arguments. They’re not secret, which is why you shouldn’t put passwords there. Now typically these processes only run for a short time so it’s difficult to catch passwords manually but it’s predictable so a script can.
So what is the proper way?
Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes
#99Earlier quoted context omitted.
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...
You have to give Apple credit that they showed some restraint and didn't just add all the features to their new file system that they found in a table on some Wikipedia page. https://en.wikipedia.org/w/index.php?title=Comparison_of_fil...
Re: Logs in High Sierra Show Plaintext Password for APFS Encrypted External Volumes
#100Earlier 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.
Exactly; macOS doesn't use /proc.