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

211–220 of 276 posts

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

#211

Post by AlexandrB »

hashbig wrote: post #191
csomar wrote: post #88

I'm really bothered. While I had relatively no issues with the fresh OS X update, I'm having a hard time with the iPhone 7 and the new iOS that is supposed to run their flagship device: iPhone 10. While most of the bugs have disappeared with the recent update, there are still some minor ones that really pisses me off: Screen freezing unresponsively for 30-60 seconds before things get back to control; and music playin…

Wouldn't be surprised if it was intentional. Apple is known for planned obsolescence for their products, especially iPhones.

I hear this line a lot and yet iPhones get the latest iOS updates for many years after release while many Android phone are lucky to get 1 year of updates.

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

#212

Post by eridius »

vthriller wrote: post #209
eridius wrote: post #181

Earlier quoted context omitted.

> Strongly disagree, and I can not conceive of how it could be viewed as "better" than hardware keys. I hope this is hyperbole, because it shouldn't be hard to understand. The TouchBar is absolutely an improvement. I can't remember the last time I actually used a laptop keyboard's F-keys for anything, but the TouchBar makes that space useful.

> I can't remember the last time I actually used a laptop keyboard's F-keys for anything Not even F5 in a web browser?

That's Windows. F5 doesn't do anything in Mac browsers.

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

#213

Post by cuckcuckspruce »

pornel wrote: post #185
floatboth wrote: post #149

Earlier quoted context omitted.

If you reused the password, yeah, instant pwnage everywhere. If your local account password isn't used anywhere else, meh, random IRC people don't have physical access to your machine :)

Unless you have remote SSH logon enabled and IRC exposes your IP address.

Yet another reason to only use SSH keys.

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

#214

Post by CodeWriter23 »

daveFNbuck wrote: post #108
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…

Responsible disclosure is about preventing the bug from being exploited before it can be fixed. Knowing about this bug doesn't help me compromise someone else, but it does help me avoid getting compromised.

So, security through obscurity. No thanks. I'd rather know about the exploit ASAP so I can implement a workaround, rather than wait months for the vendor to get off their ass while my systems are getting hacked by the hundreds if not thousands of hackers that have 0-day knowledge.

Calling what you describe as "Responsible" is intellectually dishonest.

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

#215

Post by zeveb »

eridius wrote: post #208
zeveb wrote: post #198

Earlier quoted context omitted.

> I can't remember the last time I actually used a laptop keyboard's F-keys for anything I use them regularly to switch consoles. MacOS supports multiple consoles, right?

By consoles do you mean terminals? Terminal.app uses ⌘⌥1–9 to switch windows and ⌘1–9 to switch tabs. The F-keys aren't used by Terminal.app at all (well, they're sent to the terminal as an escape sequence).

No, I mean complete GUI heads: completely separate GUI login sessions which use the same screen and can be switched between. Also called 'virtual framebuffers,' I think.

Very awesome. I'm sure that Macs support something similar.

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

#216

Post by Grimm665 »

eridius wrote: post #212
vthriller wrote: post #209

Earlier quoted context omitted.

> I can't remember the last time I actually used a laptop keyboard's F-keys for anything Not even F5 in a web browser?

That's Windows. F5 doesn't do anything in Mac browsers.

What? Fn+F5 works fine in chrome.

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

#217

Post by itbeho »

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…

Very similar issues here. MBP Touchbar with one external 5K LG display. I love the LG when it works.

Super frustrating when I I sit down and wake up the machine to find both displays flashing. Usually unplugging the LG clears things up, but replugging often results in the brightness on one display being set randomly.

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

#218

Post by tachion »

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!

Proofs of what? My story? Don't feel like I need to provide any. Proofs again Apple in lawsuit you're suggesting? I'm not an American, so suing everyone for everything is not really in my custom ;) Rather than them paying me anything after being dragged to court (and I doubt I'd have any chance given disparity between their legal resources and mine) I'd like to get an acknowledgement tied to my name, but I was told not only they don't do that, but also they can't and won't tell me wether I was right and I've found a real security bug. Steve Jobs era secrecy in all its glory.

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

#219

Post by wlesieutre »

nerpderp83 wrote: post #154
wlesieutre wrote: post #143

Earlier quoted context omitted.

For what it's worth (anecdote incoming) I use a touchbar MBP with a Dell UP2414Q, which is driven using multi-stream transport. Effectively its panel is presented to the system as two separate displayport streams running daisy-chained over a single port. Once I found the right cable, everything worked fine. (The first cable was advertised with DP1.2 and MST support, but it would only operate in the legacy mode that d…

Do you have a link for this cable? I am always interested in foisting esoteric firmware and poorly implemented protocol bugs upon myself.

They're USB-C to DisplayPort cables, so these will mainly be useful to people with the 2016-2017 MBP.

MST worked: https://www.amazon.com/gp/product/B01N11K30W/

MST did not work: https://www.amazon.com/gp/product/B06XFG1YKT/

I can't say for sure if it's the cable's fault or if it's the particular combination of cable/computer/screen that has some obscure compatibility problem. Makes me miss the days when a cable was a cable and we could tell people "Just buy any HDMI cable, no need to spend $60 on it."

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

#220

Post by j_s »

jerf wrote: post #89
j_s wrote: post #60

Earlier quoted context omitted.

Yes hopefully the commenter will edit in time to remove the http:// prefix so that it is not clickable. https://news.ycombinator.com/item?id=11135200 >sirsar: JWZ used to detect the hacker news referrer and redirect all links that originated on hacker news to goatse. Now it's only slightly less graphic

Sorry. Pity. It's actually crammed full of good stuff, which is why I linked it. It's a classic easy-looking problem that gets really hard when you get down in the weeds.

Not that it's somehow my place to say it, but I appreciate the spirit of your apology; you too are among the victims who deserve no blame.
Post reply on HN