Restricting Usage of Setuid Programs to the Admin User In MacOsx Post: 302623825

10 More Discussions You Might Find Interesting

1. OS X (Apple)

Root user in MacOSX

Hello, Do you guys know how does the root user works in this system? from the terminal i try to su to root, and i thought the password was the same as the macosx password, at the /etc/passwd file the passwd field appears as *, so it's system bussines only, is there a way to become root? i...

2. UNIX for Advanced & Expert Users

ping/traceroute setuid programs

This may be a dumb question, but I've been wondering why programs such as ping and traceroute must be setuid? Are there some restrictions which prevent normal users from accessing the world via sockets? $ pwd /bin $ ls -l ping traceroute -rwsr-xr-x 1 root root 35616 Apr 7 2005 ping...

3. Shell Programming and Scripting

restricting user input as required

Hi, I want the user to enter only numeric values and also he should only enter 2 digits only ( eg 23 or 23 or 03 any 2 digits) For the above purpose how should i declare my variable ? integer value if I read 03 in variable value then it gives me error ...also user can enter n number...

4. UNIX for Dummies Questions & Answers

Unix/Solaris admin programs

Hi, Im working for a company that has over 400+ unix/solaris boxes. Obviously when we get a new unix guy join the company, its take us AGES to set them up on all these boxes. Can people recommend any programs/packages that can be added to our unix/solaris boxes to make this easier? ...

5. UNIX for Dummies Questions & Answers

Restricting SSH usage

Hello, For one of our servers, we have had people trying to illegally loggon using the ssh service. My manager has asked me to restrict ssh access to users in our internal network but close ssh access to the "outside" world. Could someone at the very least point me to some resources on the...

6. Solaris

pkgadd and setuid in admin file

Hi I am trying to automate the install of a package, I realise that I need to create an admin file, but as part of the install I am asked if I want to install these as setuid/setgid files, I want to say yes. What value am I supposed to use for setuid= in the admin file Thanks

7. Shell Programming and Scripting

Admin user command usage restrictions

Hi, I need to work on restricting the Linux commands to the ADMIN user to some extent. It means for example, Admin users should not use passwd command to change the password of "root" or other important accounts like oracle, etc., So, I want to know which commands should be restricted upto which...

8. UNIX for Dummies Questions & Answers

Difference between inbuilt suid programs and user defined root suid programs under bash shell?

Hey guys, Suppose i run passwd via bash shell. It is a suid program, which temporarily runs as root(owner) and modifies the user entries. However, when i write a C file and give 4755 permission and root ownership to the 'a.out' file , it doesn't run as root in bash shell. I verified this by...

9. UNIX for Beginners Questions & Answers

What keeps me from abusing setuid(0) and programs with setuid bit set?

Just learning about the privilege escalation method provided by setuid. Correct me if I am wrong but what it does is change the uid of the current process to whatever uid I set. Right ? So what stops me from writing my own C program and calling setuid(0) within it and gaining root privileges ? ...

10. Shell Programming and Scripting

Setuid usage

I'm trying - as an ordinary user - to create a file in the root directory of my system. For that purpose I wrote a simple script that echoes a string into a file. I made the file executable, used sudo to change ownership to root. Like this: $ cat hello #!/bin/bash echo hello > /hello $...

LEARN ABOUT MOJAVE

submitdiaginfo

SubmitDiagInfo(8)					    BSD System Manager's Manual 					 SubmitDiagInfo(8)

NAME

     SubmitDiagInfo -- sends diagnostic information to Apple

SYNOPSIS

     SubmitDiagInfo

DESCRIPTION

     SubmitDiagInfo is a system process which runs periodically.  If the user has opted-in for automatic reporting of diagnostic and usage infor-
     mation, then SubmitDiagInfo collects and sends to Apple any recent diagnostic information which has not yet been sent to Apple.
     SubmitDiagInfo also cleans up any diagnostic and usage information which was created more than one month ago and is no longer needed.

     Sending diagnostic and usage reports to Apple helps us improve the quality and performance of our products and services.  It helps Apple
     identify common usage trends and issues that enable us to allocate our resources efficiently, and it helps us provide better support services
     to you and other customers.  All of the diagnostic and usage information is collected anonymously from your computer in a way that does not
     personally identify you.  Reports may include the following information:

     -	 Details about application or system crashes, freezes, or kernel panics.
     -	 Information about events on your computer (e.g. whether a certain function, such as waking your computer was successful or not).
     -	 Usage information (e.g. data about how Apple and third party software, hardware and services are being used).

     Automatic reporting of diagnostic information is off by default and no information is sent to Apple unless a user has opted-in to automatic
     collection of diagnostic information.  A user is offered the opportunity to opt-in for automatic collection of additional diagnostic and
     usage information after the user has manually sent a crash, hang or panic report to Apple.  Users may at any time opt in or out of automatic
     reporting in the Security & Privacy pane of the System Preferences application under the "Privacy" tab.

     All diagnostic and usage information which is eligible for automatic reporting is visible in the Console application under the "DIAGNOSTIC
     AND USAGE INFORMATION" heading in the application's sidebar.  (The information appears here even if a user has not yet opted-in for automatic
     reporting.)  For security purposes, some system diagnostic information will only be visible to admin users and will only be submitted when an
     admin user is logged in.

     Users who need technical support should use http://www.apple.com/support or other authorized support channels.  Developers who are ADC mem-
     bers should submit bug reports using http://bugreporter.apple.com in order to allow for two way communication between Apple and the bug
     reporter.

SEE ALSO

     ReportCrash(8) DumpPanic(8) diagnostics_agent(8)

Mac OS								   May 31, 2019 							    Mac OS

10 More Discussions You Might Find Interesting

1. OS X (Apple)

Root user in MacOSX

Discussion started by: sx3v1l_1n51de

2. UNIX for Advanced & Expert Users

ping/traceroute setuid programs

Discussion started by: nathan

3. Shell Programming and Scripting

restricting user input as required

Discussion started by: dhananjayk

4. UNIX for Dummies Questions & Answers

Unix/Solaris admin programs

Discussion started by: JamieP