03-19-2017
Privileged port
I have read in many articles that ports below 1024 are privileged ports. My question is if port 1024 is an privileged or a unprivileged port. Some say privileged and some unprivileged..
Last edited by Scrutinizer; 03-19-2017 at 03:30 PM..
Reason: Spelling
9 More Discussions You Might Find Interesting
1. AIX
Hi!
I need to know what is the risk involved if a user with UID >100 is attached to a group with gid =1 .i.e., a user is attached to a priviliged group in AIX .
Kindly let me know what security implication can arise in this case?
Early reply in this regard will be highly appreciated. (1 Reply)
Discussion started by: faraz82
1 Replies
2. UNIX for Advanced & Expert Users
Hi friends,
I am having ibm pseries615c3 server. previously i set privileged access password for the firmware. Now i forgot that password. Help me to reset or remove the firmware password from the server. Otherwise anyone plz help me how to change the default boot device in pseries servers. I... (8 Replies)
Discussion started by: muthulingaraja
8 Replies
3. Solaris
Hi Buddys,
We are using SUN-ONE LDAP and We need to define and implement a quarterly review of privileged accounts in the Unix environment.So, in the unix world, this would involve knowing what accounts are on each server, who has root access, what privileged accounts exist, who can sudo to... (0 Replies)
Discussion started by: bhupals
0 Replies
4. 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
5. Solaris
Hi Everyone,
In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies
6. AIX
Hi,
I am trying to implement a service on AIX based on ONCRPC protocal and I want to use a RPC library called oncrpc4j because it is a non-blocked i/o library. I found it works fine on my work machine (WIndows 7) but failed on my AIX work station. The author of oncrpc4j told me that check that... (1 Reply)
Discussion started by: derekhsu
1 Replies
7. Solaris
Hello,
I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build.
The first part is what confuses me -the cabling.
I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 Replies
8. Solaris
please find the below o/p for your reference
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000024ff295a34
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
9. Shell Programming and Scripting
How to view the cron jobs that ran on kinit i keep getting must be privileged to use -u
this is the control used,
echo 'cat /usr/local/bin/tpthadoop/secret/hadoop.txt' | kinit hdfs
what happens with above command kinit is using kerberos and the account used to run the processes jobs are... (1 Reply)
Discussion started by: cplusplus1
1 Replies
IOPERM(2) Linux Programmer's Manual IOPERM(2)
NAME
ioperm - set port input/output permissions
SYNOPSIS
#include <sys/io.h> /* for glibc */
int ioperm(unsigned long from, unsigned long num, int turn_on);
DESCRIPTION
ioperm() sets the port access permission bits for the calling thread for num bits starting from port address from. If turn_on is nonzero,
then permission for the specified bits is enabled; otherwise it is disabled. If turn_on is nonzero, the calling thread must be privileged
(CAP_SYS_RAWIO).
Before Linux 2.6.8, only the first 0x3ff I/O ports could be specified in this manner. For more ports, the iopl(2) system call had to be
used (with a level argument of 3). Since Linux 2.6.8, 65,536 I/O ports can be specified.
Permissions are inherited by the child created by fork(2) (but see NOTES). Permissions are preserved across execve(2); this is useful for
giving port access permissions to unprivileged programs.
This call is mostly for the i386 architecture. On many other architectures it does not exist or will always return an error.
RETURN VALUE
On success, zero is returned. On error, -1 is returned, and errno is set appropriately.
ERRORS
EINVAL Invalid values for from or num.
EIO (on PowerPC) This call is not supported.
ENOMEM Out of memory.
EPERM The calling thread has insufficient privilege.
CONFORMING TO
ioperm() is Linux-specific and should not be used in programs intended to be portable.
NOTES
The /proc/ioports file shows the I/O ports that are currently allocated on the system.
Before Linux 2.4, permissions were not inherited by a child created by fork(2).
Glibc has an ioperm() prototype both in <sys/io.h> and in <sys/perm.h>. Avoid the latter, it is available on i386 only.
SEE ALSO
iopl(2), outb(2), capabilities(7)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2017-09-15 IOPERM(2)