Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Before the 'should have used Linux' bandwagon arrives, I should point out Ubuntu also had this problem.

Don't feed the trolls. You bring the same answer in every thread now. Your horizon must be very limited indeed. If you'd follow the news you'd know that your loving Ubuntu distro was affected by the same fault since ages as well.
 
You must have the wrong person...

For those who don't read the article, you need to edit your sudo config file like so:
Code:
$ sudo visudo
++ Defaults timestamp_timeout=0

This means that your temporary sudo permissions are revoked immediately after the command has executed.

It should look something like this (note the rest of the file is not applicable - it came from a Debian machine):
Code:
#
# This file MUST be edited with the 'visudo' command as root.
#
# Please consider adding local content in /etc/sudoers.d/ instead of
# directly modifying this file.
#
# See the man page for details on how to write a sudoers file.
#
Defaults env_reset
Defaults mail_badpass
Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
Defaults timestamp_timeout=0

# Host alias specification

# User alias specification

# Cmnd alias specification

# User privilege specification
root ALL=(ALL:ALL) ALL
mike ALL=(ALL:ALL) ALL
#karl ALL=(ALL:ALL) ALL

# Allow members of group sudo to execute any command
%sudo ALL=(ALL:ALL) ALL

# See sudoers(5) for more information on "#include" directives:

#includedir /etc/sudoers.d

More info on sudoers: https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man5/sudoers.5.html
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.