Live data from Hacker News

Show HN: A fork of sudo with Touch ID support

github.com

101–110 of 134 posts

Re: Show HN: A fork of sudo with Touch ID support

#101

You two are both doing the "ATM machine" thing. (PAM = Pluggable Authentication Module) "Written as a PAM" sure feels wrong on the lips, though.

We detached this subthread from https://news.ycombinator.com/item?id=12834661 and marked it off-topic.

Re: Show HN: A fork of sudo with Touch ID support

#102

Earlier quoted context omitted.

Yeah, but you're ignoring the functionality loss from not having the function keys. You may not use them, but many people do. For example, in Emacs (and I'm assuming most IDEs) I can map a function key to run my tests and have a status bar entry saying how many passed or failed. It's the exact functionality in your screenshot, no touch bar required. At best the touch bar is a nice gimmick, and it's not adding anythin…

Remind me again how function keys can produce full colour multitouch interfaces, such as video/image scrubbers, colour pickers, etc. The standard "function keys can do anything" response is getting old.

Who cares? It's a gimmick. Video scrubbers and color pickers already exist. I don't need a silly keyboard screen to do them.

The "I need to pick colors and scrub video" response is getting old. Nobody does that stuff often enough for it to be a good trade off.

Re: Show HN: A fork of sudo with Touch ID support

#103

I have a feeling this is EXTREMELY DANGEROUS to have on your Mac. Using DYLD_INSERT_LIBRARIES and attacker could inject code that swizzles -[LAContext evaluatePolicy: localizedReason:reply] to always invoke the callback block with success set to YES. e.g. DYLD_FORCE_FLAT_NAMESPACE=1 DYLD_INSERT_LIBRARIES=evil.dylib my_sudo rekt This won't work on SIP protected binaries (n.b. system binaries), but might still work on…

This would not work. setuid binaries do not respect these flags, for obvious reasons. But if you're at the point where you can inject environment vars into a devs workstation, it's probably too late for that dev.

You're right. I had a suspicion of this (hence the non-committal "I have a feeling") but a quick Google search before writing the comment didn't yield much. After seeing your reply I looked at the dyld source: http://opensource.apple.com//source/dyld/dyld-210.2.3/src/dy..., see the function pruneEnvironmentVariables.

Re: Show HN: A fork of sudo with Touch ID support

#104
post #88

Earlier quoted context omitted.

I don't understand the general moan about the touch bar. These are exactly the cases I think will make the touch bar great. Is it the most innovative concept ever? No, but it looks like it's been executed very well. I think developers will like this macbook.

To what exact cases are you referring? Do you not use an ide with a test runner? What exactly is desirable about triggering and monitoring this from a second display on the keyboard--where you're looking all the time, naturally--over clicking a button on screen?

[deleted]

Re: Show HN: A fork of sudo with Touch ID support

#105
post #88

Earlier quoted context omitted.

I don't understand the general moan about the touch bar. These are exactly the cases I think will make the touch bar great. Is it the most innovative concept ever? No, but it looks like it's been executed very well. I think developers will like this macbook.

To what exact cases are you referring? Do you not use an ide with a test runner? What exactly is desirable about triggering and monitoring this from a second display on the keyboard--where you're looking all the time, naturally--over clicking a button on screen?

Take a good look at the IDE running there. It's Vim. I use that all the time, and so do many other people on HN.

Do you need a button like this on your keyboard? No, you could set up a new Vim bind. But this is more dynamic; what if the test re-run buttons were only visible after having modified a file, and replaced with a deploy or commit button if tests succeed?

If you're vigorously opposed to it, don't buy a Mac. But some people can definitely see use in it. It's like your function row, but with visibly context-aware functions.

Re: Show HN: A fork of sudo with Touch ID support

#106
post #61
post #2

This sounds amazing, and Id love if Apple allowed touchid for regular account-password prompts in macOS 10.13 (or a Sierra point update but let's be realistic) If they integrated this down to the built in sudo/su that would be even more amazing, but I imagine that's much less likely.

They've probably implemented TouchID support using PAM. If so, using with sudo/su is just a matter of configuration.

Seems unlikely to me, considering the auth is taking place on a separate SoC running WatchOS...

Re: Show HN: A fork of sudo with Touch ID support

#107

Earlier quoted context omitted.

Remind me again how function keys can produce full colour multitouch interfaces, such as video/image scrubbers, colour pickers, etc. The standard "function keys can do anything" response is getting old.

Who cares? It's a gimmick. Video scrubbers and color pickers already exist. I don't need a silly keyboard screen to do them. The "I need to pick colors and scrub video" response is getting old. Nobody does that stuff often enough for it to be a good trade off.

But they didn't add a dedicated hardware video scrubber. They added a dedicated hardware input device that can present basically any type of input. Those are just examples of what's possible that wasn't possible before.

Re: Show HN: A fork of sudo with Touch ID support

#108

This here is what gets me salivating: Using the toolbar as a context-sensitive test runner/controler: https://pbs.twimg.com/media/CwC8SNvW8AQgeWN.png:large

Yeah, but you're ignoring the functionality loss from not having the function keys. You may not use them, but many people do. For example, in Emacs (and I'm assuming most IDEs) I can map a function key to run my tests and have a status bar entry saying how many passed or failed. It's the exact functionality in your screenshot, no touch bar required. At best the touch bar is a nice gimmick, and it's not adding anythin…

You're not losing function keys, they're just becoming more powerful. You can still set the touch area to be a row of function keys, if you like that! Or they might become more dynamic, by updating which binds are available based on what's on screen.

It is a nice gimmick. Is there anything wrong with an improvement, even if it's a little one?

Re: Show HN: A fork of sudo with Touch ID support

#109

Earlier quoted context omitted.

Yeah, but you're ignoring the functionality loss from not having the function keys. You may not use them, but many people do. For example, in Emacs (and I'm assuming most IDEs) I can map a function key to run my tests and have a status bar entry saying how many passed or failed. It's the exact functionality in your screenshot, no touch bar required. At best the touch bar is a nice gimmick, and it's not adding anythin…

Remind me again how function keys can produce full colour multitouch interfaces, such as video/image scrubbers, colour pickers, etc. The standard "function keys can do anything" response is getting old.

> The standard "function keys can do anything" response is getting old.

That "function keys can do anything" is, in my opinion, the exact reason they had to go. They're scary for the typical user. What is F7? You may know, but it's not obvious in any way. That some of them cause destructive actions (e.g. Alt+F4 on Windows) makes it worse - they're scary to many users. And even when after figuring out what some of them do, one is stuck wondering "was that F8? Or F9? Oh! It was F10" (which, includes the worry that a wrong guess could cause problems).

Though, I cannot believe they shipped it without the haptic feedback to make it clear that a button was actually clicked.

^ Also, none of that, to me, includes Esc. Esc seems clear enough in its intent, and I hold no ill-will toward the Esc key.

Re: Show HN: A fork of sudo with Touch ID support

#110
The Surface line-up provides a similar feature for User Access Control (UAC) prompts via Windows Hello facial recognition (or the available fingerprint scanner for older Surfaces). It's a pretty slick and natural application of biometric authentication, and this seems a natural for Touch ID as well.
Post reply on HN