08-05-2009
Since the users have access to the server as root, there's little you can do. The only thing I can think of is creating an encrypted volume that is mounted only on-demand. But during that time it's just as accessible as everything else.
By the way, when the higher-ups decided to share the root password, did they think of a way how to discover the person responsible in case something bad happens? rm -rf is a quick, yet deadly command...
10 More Discussions You Might Find Interesting
1. Cybersecurity
restricted access...
Hi
I need to restrict users shell access to only $HOME under /home for each user. I don't want them getting out of their own directories. From what I understand chroot is something I could use, but I want to avoid this since it involves creating symbolic links to a number... (9 Replies)
Discussion started by: alwayslearningunix
9 Replies
2. UNIX for Dummies Questions & Answers
I need to create a user that only has access to 1 directory (e.g. /vol/mita/test). The user needs to be able to rsh into that directory to run a script. The user should not be able to navigate to any other directories above /vol/mita/test. Any help would be appreciated! (4 Replies)
Discussion started by: ngagne
4 Replies
3. UNIX for Dummies Questions & Answers
I have a need to allow only certain IP addresses to access a machine running solaris 9. I am not sure how this can be accomplished.
Thanks in advance for your help.
Patch (2 Replies)
Discussion started by: patch
2 Replies
4. Solaris
Hi All,
I'm on Solaris 8, I need to provide Read-only access to a user to 2 directories only.
Using rsh (restricted shell) as the user's login shell, I can restrict the user's access to a certain directory only, but how can I set in such a way that the user can access only the 2 directories... (4 Replies)
Discussion started by: max_min
4 Replies
5. UNIX for Advanced & Expert Users
I'm the admin in a shop in which my developers have and use the root account, all UNIX newbies.
I've been unable to convince management myself that this is an unacceptable practice.
I've looked in a couple books I have and can't find any chapters, discussions, etc that make the argument that... (2 Replies)
Discussion started by: keith.m
2 Replies
6. Solaris
We want to secure access to a server by restricting the number of users who can login to it. Our users are NIS users. Only few of them can telnet/ssh this server.
Do you have any idea on how to implement that?
thanks. (1 Reply)
Discussion started by: melanie_pfefer
1 Replies
7. UNIX for Dummies Questions & Answers
Hi all,
I have user called "Z". The home directory is /home/Z. I have another directory /home/Z/OP. Within /home/Z/OP, i have 2 directories
/home/Z/OP/OP1 and /home/Z/OP2.
I want to restrict access for Z to only access
/home/Z/OP and
/home/Z/OP1 and
/home/Z/OP2.
What kind of... (4 Replies)
Discussion started by: new2ss
4 Replies
8. Solaris
Dear All,
I have created a user called "x" who is allowed only to FTP and it is working fine. Here my problem is, I want to give access to a particular directory say for eg:- /dump/test directory. I don't find any option in the useradd command to restrict access to this particular directory only... (1 Reply)
Discussion started by: Vijayakumarpc
1 Replies
9. Solaris
Hi all.
I've had a quick look around but cant see anything exactly matching my requirements.
I have a new T2000 running S10. Im looking to restrict the no. cores that a S10 non-global zone can use to 1 only. The box is single CPU but 8core.
I want to do this to save on some software... (4 Replies)
Discussion started by: boneyard
4 Replies
10. UNIX for Dummies Questions & Answers
Hello,
I am using MySecureShell to chroot all sftp accesses. The problem that I have is that my boss does not want root to be able to use sftp. Root should still be able to ssh. Any ideas? (2 Replies)
Discussion started by: mojoman
2 Replies
LEARN ABOUT SUSE
ocf_heartbeat_jboss
OCF_HEARTBEAT_JBOSS(7) OCF resource agents OCF_HEARTBEAT_JBOSS(7)
NAME
ocf_heartbeat_jboss - Manages a JBoss application server instance
SYNOPSIS
jboss [start | stop | status | monitor | meta-data | validate-all]
DESCRIPTION
Resource script for Jboss. It manages a Jboss instance as an HA resource.
SUPPORTED PARAMETERS
resource_name
The name of the resource. Defaults to the name of the resource instance. (optional, string, default default)
console
A destination of the log of jboss run and shutdown script. (optional, string, no default)
shutdown_timeout
Timeout for jboss bin/shutdown.sh. We wait for this timeout to expire, then send the TERM and QUIT signals. Finally, the KILL signal is
used to terminate the jboss process. You should set the timeout for the stop operation to a value bigger than the sum of the timeout
parameters. See also kill_timeout. (optional, integer, default 5)
kill_timeout
If bin/shutdown.sh doesn't stop the jboss process, then we send it TERM and QUIT signals, intermittently and once a second. After this
timeout expires, if the process is still live, we use the KILL signal. See also shutdown_timeout. (optional, integer, default 10)
user
A user name to start a JBoss. (optional, string, default root)
statusurl
URL to test in the monitor operation. (optional, string, default http://127.0.0.1:8080)
java_home
Home directory of Java. Defaults to the environment variable JAVA_HOME. If it is not set, then define this parameter. (optional,
string, no default)
jboss_home
Home directory of Jboss. (required, string, no default)
pstring
With this string heartbeat matches for the right process to kill. (optional, string, default java -Dprogram.name=run.sh)
run_opts
Start options to start Jboss with, defaults are from the Jboss-Doku. (optional, string, default -c default -l lpg4j)
shutdown_opts
Stop options to stop Jboss with. (optional, string, default -s 127.0.0.1:1099)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 60s.
stop
Stops the resource. Suggested minimum timeout: 120s.
status
Performs a status check. Suggested minimum timeout: 30s.
monitor
Performs a detailed status check. Suggested minimum timeout: 30s. Suggested interval: 10s.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5s.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 5.
EXAMPLE
The following is an example configuration for a jboss resource using the crm(8) shell:
primitive example_jboss ocf:heartbeat:jboss
params
jboss_home=string
op monitor depth="0" timeout="30s" interval="10s"
SEE ALSO
http://www.linux-ha.org/wiki/jboss_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents 1.0.3 07/05/2010 OCF_HEARTBEAT_JBOSS(7)