Sponsored Content
Operating Systems Solaris Enable FTP for root user in Solaris 10 Post 302511048 by Perderabo on Tuesday 5th of April 2011 03:56:26 PM
Old 04-05-2011
From the in.ftpd man page:
Quote:
Third, the users must have a standard shell returned by getusershell(3C).
Read the man page for getusershell. You will probably need to create /etc/shells, populate it will the default list of shells and then add root's shell.
 

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
auth.adm(1M)															      auth.adm(1M)

NAME
auth.adm - activate, deactivate, or query about HP-UX Integrated Login SYNOPSIS
tech_name [ tech_name ] [ tech_name[:tech_name]... ] [ tech_name:parameter=value[:parameter=value]... ]... [ filename ] DESCRIPTION
The command makes it easy to activate, deactivate or query about HP-UX Integrated Login. During activation, sets up a machine to obtain integrated login behavior using any of the following commands: and saves the Integrated Login configuration, specified by and arguments, in the file This configuration file specifies the authentication technologies used to authenticate users on a system. System administrators can specify the technology for system login; where this login technology is unavailable, a fallback technology for system login can also be specified. System administrators can also specify technologies for additional user authentications that will be done after a user has successfully completed the system login phase. Integrated behavior of and is obtained by replacing the current with one that specifies the behavior requested by the arguments. auth.adm provides an option of enabling the nsswitch for DCE technology. The is updated with "dce" keyword if this option has been selected. In this scenario the name service requests for user/group information will be obtained from DCE depending on the configuration. After NSS switch is enabled, an option is provided to export the DCE user/group information to and via a cron job. program could also be run manually to do this job. Upon deactivation, restores files that were present on the system before Integrated Login was installed. It also removes the configuration file. When making a query, reads the file and prints the result of the query to stdout or to filename specified by the argument. All actions performed by are logged into the file ARGUMENTS
recognizes the following arguments: activates HP-UX Integrated Login. tech_name an abbreviated name representing an authentication technology. Starting with the 10.0 release, the tech_name's supported are: for DCE Registry for /etc/passwd and other HP-UX login technologies. tech_name specifies the technology used for system login. tech_name specifies the technology used for fallback login. tech_name[:tech_name]... specifies technologies used for additional authentications after a user has been successfully logged in to a system. tech_name:parameter=value[:parameter=value]... specifies configurable parameters applicable to a technology. Parameters for different technologies can be specified by repeating the argument. Starting with the 10.30 release, the configurable parameters supported include the following: Timeout (in seconds) on communications with a technology. Default values for TIMEOUT are as follows. 180 seconds ignored Password expiration warning period (in days). If the user's password is due to expire within the specified number of days, the user receives a warning message during login. This parameter applies to DCE technology only. If this parameter is not specified, no warning is given. Password force-change period (in days). If the user's password is due to expire within the specified number of days, the user is forced to change the password before login is allowed. This parameter applies to the DCE technology only. If this parameter is not specified, a password change is not forced. Enable DCE TGT to be forwardable. When forwarding a user's DCE TGT from machine A to machine B, it enables the user from machine A to reuse its Kerberos credentials on machine B. A parameter value is required, but its content is ignored. This parameter applies to DCE technology only. deactivates HP-UX Integrated Login. makes a query about the current Integrated Login configuration. filename prints result of a query to filename. EXAMPLES
The following command activates HP-UX Integrated Login. The configuration is set to login the user upon successful password verification by DCE. In the case where DCE is not available, a fallback for login via /etc/passwd or another HP-UX technology is configured. (Note that this strategy is effective only if the HP-UX password and DCE password are identical.) The following command activates HP-UX Integrated Login. The configuration is set to login the user upon successful password verification by /etc/passwd or another HP-UX technology. After machine access has been granted to the user, the configuration specifies that a DCE login should also be done. RETURN VALUE
returns one of the following: Successfully completed Error(s) occurred WARNING
If activation or deactivation fails to complete, the error(s) should be corrected and re-execution of the activation/deactivation should be done. cannot deactivate a failed activation. NOTE
auth.adm will restart the pwgrd daemon after the ilogin daemon is started, if it was already running. AUTHOR
was developed by HP. FILES
log file containing records of actions performed by SEE ALSO
auth.adm(1M)
All times are GMT -4. The time now is 07:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy