Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

macOS lock screen: “I just sent my session pass to my whole team”

twitter.com

Post reply on HN
Print view View original

171–180 of 276 posts

Re: macOS lock screen: “I just sent my session pass to my whole team”

#171

Post by leonroy »

djsumdog wrote: post #7
sigzero wrote: post #3

How about people stop releasing this sh*t on twitter?

Most people not in tech or infosec have never heard of and are totally uneducated about the concept of responsible disclosure. Maybe it needs to be added to high school computer class?

The #iamroot bug was actually filed mid November with product-security@apple.com according to this weeks ATP - A couple of weeks before it all blew up on Twitter.

I think the cause is more pertinent than the symptom here - Apple don't seem to notice filed bugs unless they blow up on Twitter.

Re: macOS lock screen: “I just sent my session pass to my whole team”

#172

Post by wruza »

I also typed my apple id password to my peer, not into chat, but into another mac in the same room. Mac keyboards can disconnect and connect to wrong devices if used with them once.

That specific setting was: my keyboard was used to setup his mini, mini was turned off and on later. My keyboard, already properly reconnected to my mac at that time, disconnects on timeout (or for whatever reason it does that few times a day). Mini “grabs” my keyboard when it goes back on air. I wake my sleeping mac via trackpad and try to type my password into focused password field. Non-obviously, no characters appear on my screen.

Re: macOS lock screen: “I just sent my session pass to my whole team”

#173

Post by sangnoir »

joeblau wrote: post #152
abakker wrote: post #142

So, Apple has the most available cash resource of any company out there (or at least close to). Yet, bugs galore, and strange product decisions. The obvious conclusion is that their management is failing to staff accordingly to the work that needs to be done. This could be because they are not aware that work needs to be done, which means engineers are not telling them, or that the management is not succeeding in hir…

I'm guessing that it's going to be pretty difficult to hire an engineer who is: - Very good - Wants to live near Palo Alto - Is able to live in the US - Wants to be subjected to Apple's privacy rules - Wants to work on fixing bugs instead of making new features In the software engineering game, money only goes so far.

Only the first issue can't be solved by throwing more money at it.

Re: macOS lock screen: “I just sent my session pass to my whole team”

#174

Post by kogepathic »

DigitalJack wrote: post #117
brazzledazzle wrote: post #114

Earlier quoted context omitted.

I don't know how far out it would be but with the changes to their keyboard and the addition of their touchbar I wonder if their long term plan is a touch screen in the bottom half to replace the keyboard and pad. Without some kind of tactile interface I hope I'm wrong about my suspicions.

dear God I hope not. I wouldn't mind if they made the touch pad into a screen. Probably not that useful, but it wouldn't bother me.

> I wouldn't mind if they made the touch pad into a screen.

You mean like making the laptop LCD a touchscreen?

Like other PC manufacturers have been doing for years?

Re: macOS lock screen: “I just sent my session pass to my whole team”

#175

Post by ryandrake »

tracker1 wrote: post #161
gruez wrote: post #95

Earlier quoted context omitted.

what did other companies not get right?

Linux specifically has a horrible track record for sleep/battery management in laptops, and worse recovery. Windows used to be far more buggy, but the long XP era a lot of that was fixed by XP SP3. Aside: I just wish there was an option in Mac to use "PC Shortcuts" in all my apps... it's the only place where some of the key combinations feel truly alien in most apps. I use a "PC" keyboard, but remap CMD to CTRL, ALT…

Not just a horrible track record, but the current state is also bad. I have a pretty recent Debian install on a bog standard Lenovo which otherwise runs Linux beautifully. It took days of fiddling with conf files and trying things out to get Suspend and Hibernation to work in a sensible way. The kernel, systemd and Gnome all try to do stuff, but they can't seem to agree on who's responsible for what part of power management. This is something that should work out of the box.

Re: macOS lock screen: “I just sent my session pass to my whole team”

#176

Post by perfectstorm »

pixelHD wrote: post #86
malchow wrote: post #31

Not to pile on, but my MBP (with "TouchBar" which will assuredly not exist in another year) is always in clamshell mode and connected to two external LG 4K displays. Whether, on which screen(s), or in what state the Mac wakes each morning is completely random. Sometimes it doesn't wake at all. Sometimes I have artifacts on one screen and a desktop on another screen. The sleep/wake sequence is a complete mess, and it…

Wow, I have similar issue. I have an acer 4k monitor at home with both HDMI and Display Ports. I used to use HDMI before to connect it to my 15inch 2016 MBP, and the mac used to crash very often. Close the mac, and connect the dongle with hdmi? crash. So I'd have to restart the mac, and connect the monitor while keeping it open, and then close. But once i disconnect the monitor - crash. I then got a usb c/thunderbolt…

I've noticed this crash as well. i've my MacBook Pro connected to an external monitor via an USB-C/Thunderbolt cable. I close my laptop when I leave work which would put it to sleep/lock and approx. 10% of the time when I come back the next day my machine wouldn't wake up and I've to do a hard restart. I can see some things flashing on my screen but the laptop screen would be completely blank.

Re: macOS lock screen: “I just sent my session pass to my whole team”

#178

Post by feelin_googley »

gonational wrote: post #63

With no disrespect to the developers at Apple, et al, each one of these problems that goes viral before reaching “proper” channels is a well-deserved slap in the face of these behemoth organizations. Perhaps, if the entire tech community regards Apple as a joke, they will start paying attention. “Responsible disclosure” is great stuff for creating a culture of free outsourcing of tech companies’ most imporant feature…

"With no disrespect to the developers at Apple, et. al., each one of these problems that goes viral before reaching "proper" channels..."

s/that goes viral before reaching \"proper\" channels//

The fact that the problems existed to begin with is more troubling than whether they became known outside the company or not. IMO.

With an open source UNIX-like OS (like the ones Apple sourced from for parts of macOS), both the developers and the users can watch the commits as they happen. Developers and users anywhere can choose to watch the commits and may be able to detect a series of poor quality ones. At least they can make informed decisions on the relative merits of changes from one version to the next. (Edit: They might choose not to compile or install certain components. I do not use X11. Nor do I use systemd.)

The fact that development of macOS is hidden from those outside Apple and that problems are protected from "going viral" does not make the problems any less of an issue for macOS users.

The issue is not how fast and secretively they fix problems, it is how many problems their developers are introducing into the existing version to begin with.

If there are problems routinely being introduced then no amount of fixing after the fact and behind the scenes is going to make the OS higher quality. Only due care taken before introducing changes will guard against further deterioration of quality level.

(Edit: The mention of open source is not intended to be interpreted as an argument that open source inherently results in better software. Perhaps skill and attention to detail are at cause. This is a debate worth avoiding.

The relevance of the mention of open source is intended to suggest that detecting and avoiding problematic software may be easier for some users, e.g. yours truly, if they can access the source code. As opposed to hoping that Acme Hardware and Software Corporation will quickly and secretly fix all software problems that slipped through their QC procedures. Too late for the user who has already paid for the software and updated to the new version. That argument should not be too controversial.)

Re: macOS lock screen: “I just sent my session pass to my whole team”

#179

Post by ssijak »

ebbv wrote: post #76

The quality of the software and the sacrifice of key functionality in the hardware (dropping of MagSafe, which was a huge differentiator, going to just USB-C ports which almost nothing supports, not even Apple's own in box phone chargers) demonstrates that Apple is purely a design house lately. It has completely faltered on the engineering side. Tim Cook is not an engineer and Jony Ive is not an engineer. There are e…

Yeah, magsafe is paramount to doing professional work on a professional machine.

Re: macOS lock screen: “I just sent my session pass to my whole team”

#180

Post by eridius »

yeukhon wrote: post #118
tachion wrote: post #13

Oh, wow - I've reported this problem along with na example exploit to Apple about 6-7 years ago. Never got any recognition for it, but It was fixed some time after that. It's quite sad to see old bugs getting new lives like that. For those interested, the sample exploitation that I've discovered was connecting any iPod/iPhone device to a OSX laptop while screen was locked was taking the focus away from login prompt '…

> Oh, wow - I've reported this problem along with na example exploit to Apple about 6-7 years ago Any proofs? Perhaps you can demand a bounty payout or sue them ignoring!

You can't demand a bug bounty payout, especially because Apple didn't have a bug bounty back then (and their bug bounty today is invite-only).

Also, if you read the rest of the comment, Apple didn't ignore it. They fixed it.

Post reply on HN