This is amazing -- but every. single. update. disables it again
Why does the sudo file not persist between updates? This case is quite minor for personal computers, but what about companies that log in with yubikeys or smart cards? Do they have to reconfigure after every update too?
This is a very macOS problem. Why does it reset every preference on updates? The one that kills me is wake-on-lan, that gets turned back on regardless. Hate!
Something weird going on, it still asks for password on the command prompt, if I press just Return key then dialog for touch id opens.. after touching it says `Sorry try again` (my touch id works in other places).
You can also use this to secure SSHD on servers by delegating to PAM with keyboard-interactive.
I'm waiting for U2F OpenSSH support to trickle down to stable distros but in the meantime pam_yubico is pretty damn good... not to mention you don't have to worry about terminal support since it relies on the yubikey OTP emulating a keyboard.
I'd love for iPhone and Watch to serve as a second-screen touch id for MacOS. Then I can tuck the laptop (or Mini) away, and not have to type passwords into various systems.
I agree using your watch is cool. However I think you lose out on the security aspect, an important element that a fingerprint provides all on the same device.
This made me realize my usage of sudo has gone down quite a bit. It seems like things mostly get permissions right these days, brew and ports were the main culprits back in the day.
I was thinking the same thing. Since I got my MBP16 I think the only times I’ve typed a password at all have been when the Touch ID session expires or whatever it is that requires reauth.
Interesting, I hacked a small pam module together 4 years ago for the first generation of touch id enabled macbooks[0] and I wonder if pam_tid.so was always present and I just missed it. D'oh!
Every update requires you to redo this. It's so repetitive that I keep a copy of what I want `/etc/sudo` to look like in my homedir and, whenever I get the prompt for a sudo attempt, I instead sudo to cp the file. Then I go on my way with what I was originally intending.has recently sudo'd.
Does anybody know if there's a solution for keychain password copy too? I have a very complicated vpn password that I change often (so I don't remember it), but each day, when connecting to the vpn, I have to open keychain and type my user password to get the vpn password. I couldn't find a way to use touch id for that.
It requires the keychain to be unlocked, which can be handled with touch ID, and you can have it confirm with a "are you sure" dialog box every time.
If you really wanted to be prompted for a fingerprint basically every time, you could probably use a separate keychain that locks after 1 minute of inactivity.
Out of curiousity why do you change a complex password regularly? Is this something your evilCorp policy forces you to do, or something you do out of habit because of something you read on the internet, or even rote habit from something picked up at previous evilCorp policies?
> Since you expect to be be typing in a command line, moving your finger to touch the key is probably not very efficient.
Why is this not very efficient? Isn't moving my finger to touch the key equivalent to a single key stroke? How is a single key stroke less efficient then many key strokes?
Admittedly I've never used Mac's implementation but I could see a slowdown if it takes longer for the fingerprint to register that it takes to type your password (which is probably the fastest combination of characters you can type)
What type of work or activity on macOS requires sudo repeatedly enough that it needs to be automated in this way? I mainly need sudo for the occasional dmesg or for adjusting routes after activating my VPN for work.
I just have a setuid root sudo binary (compiled from sudo-touchid: https://github.com/mattrajca/sudo-touchid) in my home folder ~/bin. This has worked a treat across OS updates, without hacking PAM stuff. It’s extremely convenient and has probably saved me cumulative hours in typing out my long password :)
I'm not sure about the "not efficient" part either. My password is 10+ characters, random alphanumeric with special characters. I sometimes mistype it. Whereas I'm yet to make a mistake tapping my finger on the finger print reader.
Touch ID is awesome, but I semi-regularly use the APFS snapshot rollback feature and it erases my finger prints.
Does anyone know why this happens? I was very happy when I found out APFS is CoW but it kind of sucks that restoring an old snapshot apparently erases the secure enclave in my M1 chip.
More than likely because that's a security risk. If it didn't do this, an attacker could likely roll back your machine to before you had Touch ID set up and then roll it forward again to access your data, now without a Touch ID restriction.
The system will notice changes and disable certain features. I noticed my Apple Pay stopped working after a restore and there are additional settings that can turn off Apple Pay. Such as allowing boot from an external drive.
[+] [-] cprecioso|5 years ago|reply
Why does the sudo file not persist between updates? This case is quite minor for personal computers, but what about companies that log in with yubikeys or smart cards? Do they have to reconfigure after every update too?
[+] [-] beyondcompute|5 years ago|reply
[+] [-] jeffbee|5 years ago|reply
[+] [-] bitlevel|5 years ago|reply
[+] [-] cprecioso|5 years ago|reply
[+] [-] mega_dingus|5 years ago|reply
[+] [-] girishso|5 years ago|reply
On 11.2.1
[+] [-] helsinkiandrew|5 years ago|reply
[+] [-] zaphirplane|5 years ago|reply
[+] [-] philsnow|5 years ago|reply
visudo will lint the resulting file and (should) reject the change if it would break your system.
[+] [-] ivrrimum|5 years ago|reply
[deleted]
[+] [-] Galanwe|5 years ago|reply
[+] [-] tomxor|5 years ago|reply
You can also use this to secure SSHD on servers by delegating to PAM with keyboard-interactive.
I'm waiting for U2F OpenSSH support to trickle down to stable distros but in the meantime pam_yubico is pretty damn good... not to mention you don't have to worry about terminal support since it relies on the yubikey OTP emulating a keyboard.
[+] [-] sdoering|5 years ago|reply
[+] [-] sammorrowdrums|5 years ago|reply
[+] [-] rvz|5 years ago|reply
[0] https://github.com/insidegui/pam-watchid
[+] [-] deergomoo|5 years ago|reply
[+] [-] gumby|5 years ago|reply
I use this feature for other touch cases (e.g. unlocking 1Password) but would hate it when in the flow.
Admittedly my password is well wired into my fingers.
[+] [-] dmitriid|5 years ago|reply
[+] [-] pplante|5 years ago|reply
[+] [-] parhamn|5 years ago|reply
[+] [-] eyelidlessness|5 years ago|reply
[+] [-] antonio-ramadas|5 years ago|reply
Coupled with `expect` I use it to authenticate through SSH (that is the only feasible option I got to connect to hosts I’ve got limited access). I even wrote about it: https://antonio-ramadas.github.io/blog/2020/10/30/ssh-login-...
Here is the gist of it:
Edit: Please remove all permissions from the password file with: I’m also assuming you run this script on an environment you control and trust. Be wary of your password.[+] [-] koffiezet|5 years ago|reply
[+] [-] isatty|5 years ago|reply
[0] https://github.com/spaghetti-/pam-touchid
[+] [-] sigjuice|5 years ago|reply
pam_modules-159.50.4/modules/pam_tid/pam_tid.c appeared in macOS 10.12.4 https://opensource.apple.com/release/macos-10124.html
And macOS 10.12.4 was posted on Mar 27, 2017, according to https://support.apple.com/kb/DL1911
[+] [-] ctur|5 years ago|reply
Rote but effective.
[+] [-] ethanpil|5 years ago|reply
[+] [-] metafunctor|5 years ago|reply
[+] [-] antihero|5 years ago|reply
[+] [-] zuppy|5 years ago|reply
[+] [-] hannibalhorn|5 years ago|reply
If you really wanted to be prompted for a fingerprint basically every time, you could probably use a separate keychain that locks after 1 minute of inactivity.
[+] [-] nikisweeting|5 years ago|reply
https://docs.sweeting.me/s/power-button-password-manager-sho...
[+] [-] dylan604|5 years ago|reply
[+] [-] dustinmoris|5 years ago|reply
Why is this not very efficient? Isn't moving my finger to touch the key equivalent to a single key stroke? How is a single key stroke less efficient then many key strokes?
[+] [-] jedimastert|5 years ago|reply
[+] [-] garettmd|5 years ago|reply
[+] [-] sigjuice|5 years ago|reply
[+] [-] lucideer|5 years ago|reply
[+] [-] oezi|5 years ago|reply
https://github.com/nullpo-head/WSL-Hello-sudo
[+] [-] nneonneo|5 years ago|reply
[+] [-] MatekCopatek|5 years ago|reply
[+] [-] danielyaa5|5 years ago|reply
[+] [-] Simplicitas|5 years ago|reply
[+] [-] nindalf|5 years ago|reply
[+] [-] nunez|5 years ago|reply
[+] [-] float4|5 years ago|reply
Does anyone know why this happens? I was very happy when I found out APFS is CoW but it kind of sucks that restoring an old snapshot apparently erases the secure enclave in my M1 chip.
[+] [-] dkonofalski|5 years ago|reply
[+] [-] wil421|5 years ago|reply
[+] [-] nikisweeting|5 years ago|reply
https://docs.sweeting.me/s/power-button-password-manager-sho...