Sponsored Content
Special Forums Cybersecurity Allowing access to ports < 1024 w/o root Post 20317 by rpollard on Wednesday 24th of April 2002 01:42:14 PM
Old 04-24-2002
Allowing access to ports < 1024 w/o root

I need to set up an application to run in a script which will be running as a web server but is a database. I need to allow users to use the web server but the app must be run as root in order for the ports to be accessible. This is not a very secure environment would like to know how this could be solved.

I just need to know the basic commands and concept and I should be able to figure it out, hopefully!?!?

Thanks

Robert Pollard
 

9 More Discussions You Might Find Interesting

1. Linux

how to access root priveliges if root password is lost

wish to know how to access root password it root password is forgotten in linux (1 Reply)
Discussion started by: wojtyla
1 Replies

2. UNIX for Advanced & Expert Users

Are ports above 1024 closed by default ?

Hi guys, Just needed to know if all the ports above 1024 are closed by default. I know that below 1024 the ports are reserved for the kernel and ports above 1024 are reserved for user applications. But by default, if I do not have a rule in my firewall to block ports above 1024, Will my... (4 Replies)
Discussion started by: firefox211
4 Replies

3. Solaris

Non-root user access to privileged ports-Solaris 8

Please let me know how to setup a non-root user to be able to access a privileged port (<1024) on Solaris 8. I am currently running tomcat as "tomcat" user and I get the following error during to start up: SEVERE: Error initializing endpoint java.net.BindException: Permission denied<null>:443 (5 Replies)
Discussion started by: pingmeback
5 Replies

4. UNIX for Dummies Questions & Answers

How to allow access to some commands having root privleges to be run bu non root user

hi i am new to unix and i have abig task. i have to \run particular commands having root privileges from a non root user. i know sudo is one of the way but i need sum other approach kindly help Thanks (5 Replies)
Discussion started by: suryashikha
5 Replies

5. SuSE

Auditors want more security with root to root access via ssh keys

I access over 100 SUSE SLES servers as root from my admin server, via ssh sessions using ssh keys, so I don't have to enter a password. My SUSE Admin server is setup in the following manner: 1) Remote root access is turned off in the sshd_config file. 2) I am the only user of this admin... (6 Replies)
Discussion started by: dvbell
6 Replies

6. Cybersecurity

IP Tables not allowing ports

Hi guys, I'm trying to configure iptables to only allow certain ports access. I set the first set of rules to block everything and then subsequently open ports as needed, but everything still seems to be blocked. I have read that the order matters (new to iptables), perhaps this is an issue.... (6 Replies)
Discussion started by: 3therk1ll
6 Replies

7. Ubuntu

Root access that can't change root password?

We are having a little problem on a server. We want that some users should be able to do e.g. sudo and become root, but with the restriction that the user can't change root password. That is, a guarantee that we still can login to that server and become root no matter of what the other users will... (2 Replies)
Discussion started by: 244an
2 Replies

8. UNIX for Advanced & Expert Users

One user to su to another without allowing root access and password

Hello Gurus, I want One user to su to another without allowing root access and password. I want to run a specific command as below from user am663: --------------------------------------------------------- sudo -u appsprj4 /home/appsrj4/scripts/start_apache.sh ------------------- But... (6 Replies)
Discussion started by: pokhraj_d
6 Replies

9. SCO

SCO 5.0.7 server - Message - Root Account is disabled - but allowing entry via daemon.

SCO 5.0.7 server on an HP Proliant ML350G5 with E200 raid controller. The message on the server during boot says this message in several places. "Root Account Disabled, but allowing entry via deamon" At this point, there are some hardware issues to work through first. One is that we don't... (2 Replies)
Discussion started by: cjdavis618
2 Replies
murmur-user-wrapper(1)					      General Commands Manual					    murmur-user-wrapper(1)

NAME
murmur-user-wrapper - User wrapper for murmurd. SYNOPSIS
murmur-user-wrapper [options] DESCRIPTION
Murmur is the server component of Mumble, a low-latency, high quality VoIP application. Murmur-wrapper is a wrapper script to make it eas- ier for normal users to set up their own, private murmur server. OPTIONS
-d "directory" Set directory to use. By default, the wrapper script uses $HOME/murmur -s Check if murmur process is running. -k Terminate running murmur process. -i Initialize only, do not start the server. -p "password" Specify password for the SuperUser account and exit. SuperUser is the mumble equivalent of root, a special user which bypasses all access restrictions. NOTES
To create your own private server, you first want to run murmur-user-wrapper -i Then edit ~/murmur/murmur.ini to set the various configuration settings. The most important is probably the port; unless you're the only murmur process running on this server, you'll need to change it. When you're happy with your settings, you need to set the password for SuperUser, which is your administrator account. murmur-user-wrapper -p <password> Once this is done, simply run murmur-user-wrapper to start the server. SEE ALSO
murmurd(1). AUTHOR
mumble and murmurd was written by Thorvald Natvig <slicer@users.sourceforge.net>. 2008 May 09 murmur-user-wrapper(1)
All times are GMT -4. The time now is 05:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy