05-09-2002
Re: Access to ports < 1024 w/o root
Thanks for the reply!
I didn't think the OS mattered and that's why I didn't mention it. I thought there was a general "Unix" way of doing this. But, if it will help, the OS is OS X (BSD implementation). I have become quite disappointed in Apple in the last few days as I am discovering they have drastically changed the Unix core to a more proprietary OS than most Unix distributions I have worked with.
9 More Discussions You Might Find Interesting
1. Linux
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
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
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
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
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
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
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
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 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
LEARN ABOUT DEBIAN
plack::handler
Plack::Handler(3pm) User Contributed Perl Documentation Plack::Handler(3pm)
NAME
Plack::Handler - Connects PSGI applications and Web servers
SYNOPSIS
package Plack::Handler::AwesomeWebServer;
sub new {
my($class, %opt) = @_;
...
return $self;
}
sub run {
my($self, $app) = @_;
# launch the AwesomeWebServer and run $app in the loop
}
# then from command line
plackup -s AwesomeWebServer -a app.psgi
DESCRIPTION
Plack::Handler defines an adapter (connector) interface to adapt plackup and Plack::Runner to various PSGI web servers, such as Apache2 for
mod_perl and Standalone for HTTP::Server::PSGI.
It is an empty class, and as long as they implement the methods defined as an Server adapter interface, they do not need to inherit
Plack::Handler.
If you write a new handler for existing web servers, I recommend you to include the full name of the server module after Plack::Handler
prefix, like Plack::Handler::Net::Server::Coro if you write a handler for Net::Server::Coro. That way you'll be using plackup command line
option like:
plackup -s Net::Server::Coro
that makes it easy to figure out which web server you're going to use.
METHODS
new
$server = FooBarServer->new(%args);
Creates a new adapter object. %args can take arbitrary parameters to configure server environments but common parameters are:
port Port number the server listens to.
host Address the server listens to. Set to undef to listen any interface.
run
$server->run($app);
Starts the server process and when a request comes in, run the PSGI application passed in $app in the loop.
register_service
$server->register_service($app);
Optional interface if your server should run in parallel with other event loop, particularly AnyEvent. This is the same as "run" but
doesn't run the main loop.
SEE ALSO
rackup
perl v5.14.2 2011-02-27 Plack::Handler(3pm)