Sponsored Content
Full Discussion: More command insecure
Top Forums UNIX for Advanced & Expert Users More command insecure Post 73035 by tmarikle on Thursday 26th of May 2005 05:50:25 PM
Old 05-26-2005
Quote:
Originally Posted by odashe
Sorry guys,
I found the solution:
the pg command with -r option does the job.
By the way, the same thing happens with vi, view, etc.
 

2 More Discussions You Might Find Interesting

1. Cybersecurity

PCI DSS Compliance : Insecure Communication Has Been Detected

From the nessus scanner tool report i got below vulnerability PCI DSS Compliance : Insecure Communication Has Been Detected http://www.tenable.com/plugins/index.php?view=single&id=56208 As per the description given in above link - I am not able to understand How to find insecure port... (2 Replies)
Discussion started by: saurabh84g
2 Replies

2. AIX

How to disable insecure protocols?

Hello all, planning to secure AIX sever by disabling insecure protocols/cipher suites; got the below requirements from secuirty team. 1.configure the server to disable support for DES and IDEA cipher suites 2.disable insecure TLS/SSL protocol support Configure the server to... (4 Replies)
Discussion started by: Kumar7997
4 Replies
SETUID(1)						      General Commands Manual							 SETUID(1)

NAME
setuid - run a command with a different uid. SYNOPSIS
setuid username|uid command [ args ] DESCRIPTION
Setuid changes user id, then executes the specified command. Unlike some versions of su(1), this program doesn't ever ask for a password when executed with effective uid=root. This program doesn't change the environment; it only changes the uid and then uses execvp() to find the command in the path, and execute it. (If the command is a script, execvp() passes the command name to /bin/sh for processing.) For example, setuid some_user $SHELL can be used to start a shell running as another user. Setuid is useful inside scripts that are being run by a setuid-root user -- such as a script invoked with super, so that the script can execute some commands using the uid of the original user, instead of root. This allows unsafe commands (such as editors and pagers) to be used in a non-root mode inside a super script. For example, an operator with permission to modify a certain protected_file could use a super command that simply does: cp protected_file temp_file setuid $ORIG_USER ${EDITOR:-/bin/vi} temp_file cp temp_file protected_file (Note: don't use this example directly. If the temp_file can somehow be replaced by another user, as might be the case if it's kept in a temporary directory, there will be a race condition in the time between editing the temporary file and copying it back to the protected file.) AUTHOR
Will Deich local SETUID(1)
All times are GMT -4. The time now is 04:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy