Sponsored Content
Operating Systems Solaris Enable FTP for root user in Solaris 10 Post 302514283 by nsusheelgoud on Friday 15th of April 2011 10:24:40 AM
Old 04-15-2011
susheel

check services then after go for #vi /etc/ftpd/ftpusers
and place comment beside of root
 

10 More Discussions You Might Find Interesting

1. Solaris

Solaris 8 - FTP server -enable

Hi, I have turn off the FTP service and rebooted the server . (edit /etc/inetd.conf and /etc/inet/services) Now , how can I enable back the FTP without rebooting the server . Thanks (1 Reply)
Discussion started by: civic2005
1 Replies

2. Solaris

Want to block ftp for root user

Hi Friends, I would like to block the root user for doing ftp. As I am aware that I need to put the entry for root in /etc/ftpusers.....am I right...??? But I am not able to edit the file & even more command is not working. #ls -l ftp* total 14 -rw-r--r-- 1 root sys 1249 Jun... (3 Replies)
Discussion started by: jumadhiya
3 Replies

3. Linux

How to Enable TELNET for root user

How to Enable TELNET for root user in Linux. (3 Replies)
Discussion started by: sakthi_13
3 Replies

4. Solaris

Permissions for the root user on Solaris 10

Hi I have a doubt, here if a file does not have the write permissions to the root user my script is going to write the data into that file. when i executed the script as root user. Is it correct ... ? (4 Replies)
Discussion started by: Shreedhar Naik
4 Replies

5. Solaris

How to start CDE for non root user on Solaris 10

Hi, How can I start CDE for non root user created.For root CDE is working fine but for non root user CDE exits back to login screen after trying for some time.Also I cant see .dt and .dtprofile files in the users home directory.How can I create them.Kindly help. Thanks & Regards, Kiran. (1 Reply)
Discussion started by: kiranherekar
1 Replies

6. 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

7. Solaris

About FTP Only User under Solaris 10

Hi, I am using Solaris 10. I am trying to create a restricted user: 1. which can ftp in to and ftp out from a Directory Tree 2. which can use only commands: prompt, get, mget, put, mput, delete, mdelete First of all I would like to know, whether this is possible or not If it is possible,... (1 Reply)
Discussion started by: SnehalRBhatt
1 Replies

8. Shell Programming and Scripting

How to enable "banner" for a user in solaris?

Password: Using keyboard-interactive authentication. Do you agree with the banner terms (y/n)?: y (4 Replies)
Discussion started by: frintocf
4 Replies

9. Solaris

Solaris 10 - 'ls' green for root user only

Welcome to all. Have an issue and looking for help so hope someone is able to give me some clues. I prepared some shell scripts with coloured output to help other guys to have more automated task. Not sure if I did this but now whenever I use 'ls' command for root user every output in... (29 Replies)
Discussion started by: TiedCone
29 Replies

10. Solaris

Root user not recognizing on Solaris-10 (shadow file corruption)

Hello, I got into a wired state on one of solaris 10 server. When I noticed that server is having some issue, I found that there were dumpadm.conf entries in /etc/shadow and real entries were wiped of. Probably somebody fat fingers. I was able to boot into failsafe, break SVM mirror, copied... (25 Replies)
Discussion started by: solaris_1977
25 Replies
REXECD(8)						      System Manager's Manual							 REXECD(8)

NAME
rexecd - remote execution server SYNOPSIS
/usr/libexec/rexecd DESCRIPTION
Rexecd is the server for the rexec(3) routine. The server provides remote execution facilities with authentication based on user names and passwords. Rexecd listens for service requests at the port indicated in the ``exec'' service specification; see services(5). When a service request is received the following protocol is initiated: 1) The server reads characters from the socket up to a null (`') byte. The resultant string is interpreted as an ASCII number, base 10. 2) If the number received in step 1 is non-zero, it is interpreted as the port number of a secondary stream to be used for the stderr. A second connection is then created to the specified port on the client's machine. 3) A null terminated user name of at most 16 characters is retrieved on the initial socket. 4) A null terminated, unencrypted password of at most 16 characters is retrieved on the initial socket. 5) A null terminated command to be passed to a shell is retrieved on the initial socket. The length of the command is limited by the upper bound on the size of the system's argument list. 6) Rexecd then validates the user as is done at login time and, if the authentication was successful, changes to the user's home direc- tory, and establishes the user and group protections of the user. If any of these steps fail the connection is aborted with a diag- nostic message returned. 7) A null byte is returned on the initial socket and the command line is passed to the normal login shell of the user. The shell inherits the network connections established by rexecd. DIAGNOSTICS
Except for the last one listed below, all diagnostic messages are returned on the initial socket, after which any network connections are closed. An error is indicated by a leading byte with a value of 1 (0 is returned in step 7 above upon successful completion of all the steps prior to the command execution). ``username too long'' The name is longer than 16 characters. ``password too long'' The password is longer than 16 characters. ``command too long '' The command line passed exceeds the size of the argument list (as configured into the system). ``Login incorrect.'' No password file entry for the user name existed. ``Password incorrect.'' The wrong was password supplied. ``No remote directory.'' The chdir command to the home directory failed. ``Try again.'' A fork by the server failed. ``<shellname>: ...'' The user's login shell could not be started. This message is returned on the connection associated with the stderr, and is not preceded by a flag byte. SEE ALSO
rexec(3) BUGS
Indicating ``Login incorrect'' as opposed to ``Password incorrect'' is a security breach which allows people to probe a system for users with null passwords. A facility to allow all data and password exchanges to be encrypted should be present. 4.2 Berkeley Distribution November 16, 1996 REXECD(8)
All times are GMT -4. The time now is 09:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy