How to open ports below 1024 as a user (Redirect maybe)

Hello,

My problem is with Slackware Linux. I need to start a tunneling server written in java, but I cannot use port 443, because I have no root permissions. However the proxy I need to bypass only allows connect to 443. So is there any way for me as a user to start my server on this port or to redirect this port to so higher and listen there. I could ask the admin to do something, so if it's the only way, I would appreciate such solution also. Thank you!
avokAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

paranoidcookieCommented:
Users dont have access to the privilaged ports below 1024 for very good security reasons. I suggest you talk to your admin, he/she might take offence if you start effectivly hacking the network to access the privilaged ports.
0
avokAuthor Commented:
I'm not going to argue about how good these security reasons are. If you must know he/she does not care much to help me configure my servers. So I am trying to do it myself. As I mentioned I would be glad to hear for something that the admin must do himself. But I need to tell him what to do exactly. If you are now satisfied with my moral, could you please answer something on the topic?
0
CaseybeaCommented:
Opening up a server on a privileged port requires root access.     The short answer to this question is "yes, only the system administrator can do this".

I also suspect your sysadmin will not give you the root password.

I do, however, have a USEFUL alternative that you and your sysadmin might wish to consider:

There is a really great workaround- a nifty tool called "sudo".   it stands for SUPER USER DO.   It allows regular users to do "root level" commands.    For example, let's say that you want the ability to stop and start the apache webserver on that box.   You don't want to have to keep bothering the system administrator.   With sudo, you both can have the best of both worlds.   He doesn't have to give you the root account, and you can do your ONE (or two, or three....) root-level commands.  And ONLY those commands.

This will, of course, require cooperation from your sysadmin to install this initially, and configure the specific commands s/he wants to allow you to do.  

This is where you obtain the code and documentation:  http://www.courtesan.com/sudo/

We use it in our organization a lot.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

paranoidcookieCommented:
Alternativly you can get the sysadmin to setuid ou binary chmod + s which will give it root priv when it runs.
0
avokAuthor Commented:
paranoidcookie could you clarify the last one a little bit? What command needs to be executed on what? I don't have much experience in UNIX.
0
paranoidcookieCommented:
Basicall binaries (programs) have permission read write execute normally however there are special permissions that allow programs to run are root. Its used on tools like ping (which uses a privilaged port but can be run by a user).

In order to change permissions you use a program called chmod

To make a program setuid run

chmod +s program name

Hope that explains things a little better
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
avokAuthor Commented:
OK, I understand now. The user who sets the s bits is allowing execution of the script with his privileges. But that means that I could later modify that script and do anything that the root could do. Maybe he can deny write access to that script after setting suid.
0
paranoidcookieCommented:
Yes I would also recommend restricting the permissions so only local users (or just you) can see it as setuid is very dangerous
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.