I sometimes believe that this kind of sudo touch approval is a scam. Quite often when I update some app that comes with an installer (like nextcloud or Edge browser), I am offered to approve the installation / update via touch ID, but it almost never works, but instead I have to type in the admin account and password. So I wonder why they even offer this option, when it has no effect?!
this post was submitted on 18 Aug 2023
45 points (97.9% liked)
Apple
17432 readers
127 users here now
Welcome
to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!
Rules:
- No NSFW Content
- No Hate Speech or Personal Attacks
- No Ads / Spamming
Self promotion is only allowed in the pinned monthly thread
Communities of Interest:
Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple
Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode
Community banner courtesy of u/Antsomnia.
founded 1 year ago
MODERATORS
Did you focus the popup containing the Touch ID symbol? Often times it opens defocused and you have to click it to actually use Touch ID.
The code is such a tangled mess that trying to update one place has no effect on others, or straight up fails because it was expecting a different response
This is great, but I’ve not run sudo on a Mac for daily DevOps duties for at least five years now. If sudo is part of your workflow, question your workflow.
As a SysAdmin sudo is part of daily life.
I'm genuinely curious, what on a Mac do you routinely use root for? We use Jamf for device management, while I appreciate the scripts it runs almost certainly have superpowers, none of our end users do. Homebrew allows for full package management for CLI utilities without admin rights and Installomator handles GUI applications.
I use sudo on my Mac almost daily to edit my /etc/hosts file. My employer is a big user of Akamai, and this is the standard way of testing configuration changes on Akamai’s staging network prior to deploying them in production.
This is how we ensure that a seemingly trivial change, not to mention incredibly complex ones, don’t result in doing something like knocking an entire website offline.
odds and ends like rsync.