Sponsored Content
Full Discussion: Login issues
Operating Systems Solaris Login issues Post 302711171 by bitlord on Friday 5th of October 2012 01:00:59 PM
Old 10-05-2012
I think I have the answer. The Solaris 10 servers that are having the issue are older servers. The newer builds are not heaving the issue. It looks like the older servers need a patch. I downloaded the patch 140905-02 and installed it on the older servers. I'm just waiting on permission to restart the server so the patch can take affect.
 

8 More Discussions You Might Find Interesting

1. Linux

Redhat 9 modem login issues

Hi guys , I have redhat 9 and i have no idea what i'm doing. This is my first time taking a break from windows and exploring this new OS. I'm trying to install an External Usrobotic 56K Model Number 5686, after rebooting it was detected. How can i configure the server so i can call (modem... (1 Reply)
Discussion started by: josramon
1 Replies

2. UNIX for Advanced & Expert Users

KSH Login issues

Hi In my environment User have csh have default shell. In some cases some users requires KSH. We are using NIS as well as some local users. here my problem is recently in some of sun servers if users who have ksh as a default shell are trying to login with putty the session terminated after... (3 Replies)
Discussion started by: vkesineni
3 Replies

3. Web Development

APACHE: Tie in Web Page login with server login

Hello, I have created a web page on a server using apache and added .htaccess and .htpasswd in the folder for authentification. I was wondering if there was anyway to tie-in the login for this page with the login used to logon to the server. i.e. the same login info. is used for both,... (2 Replies)
Discussion started by: WhotheWhat
2 Replies

4. Cybersecurity

APACHE: Tie in Web Page login with server login

Hello, I have created a web page on a server using apache and added .htaccess and .htpasswd in the folder for authentification. I was wondering if there was anyway to tie-in the login for this page with the login used to logon to the server. i.e. the same login info. is used for both, when... (1 Reply)
Discussion started by: WhotheWhat
1 Replies

5. Solaris

error message rmclomv ... SC Login Failure for user Please login:

Hello World ~ HW : SUN Fire V240 OS : Solaris 8 Error message prompts 'rmclomv ... SC login failure ...' on terminal. and Error Message prompts continually 'SC Login Failure for user Please login:' on Single Mode(init S) The System is in normal operation, though In case of rain, Can... (1 Reply)
Discussion started by: lifegeek
1 Replies

6. Red Hat

issues with ssh login

I have a Rhel 3 machine. I can login to it through telnet. The config files /etc/ssh/sshd_config and /etc/ssh/ssh_config has not been modified. But the IP address of the system was changed. Could this be issue? It was earlier configured for passwordless login(dsa). I tried moving the... (4 Replies)
Discussion started by: kirtikjr
4 Replies

7. Shell Programming and Scripting

Issues for script that login to a unix box

Hi, I have a script that should login to a different box then the box that i am in and run the commands. I have the script sample below that logins to a unix box and get the files .Looks like ls-lrt command is not running or its wrongly used. #!/bin/bash # Ask the user for build month... (5 Replies)
Discussion started by: learninguser235
5 Replies

8. UNIX for Advanced & Expert Users

Can adding to a new group be effective in current login environment without re-login?

Hey folks, When a user is added to a new group, the user has to be log out and log in again to make the new group effective. Is there any system command or technique to refresh user group ID update without re-login? I am not talking about to use "login" or "su -l" commands which can only make... (2 Replies)
Discussion started by: hce
2 Replies
ssh-agent(1)							   User Commands						      ssh-agent(1)

NAME
ssh-agent - authentication agent SYNOPSIS
ssh-agent [-a bind_address] [-c | -s ] [-d] [command [args]...] ssh-agent [-c | -s] -k DESCRIPTION
ssh-agent is a program to hold private keys used for public key authentication (RSA, DSA). ssh-agent is often started at the beginning of a login session. All other windows or programs are started as clients to the ssh-agent program. Through use of environment variables, the agent can be located and automatically used for authentication when logging in to other machines using ssh(1). See the System Administra- tion Guide: Security Services. If a command line is given, this is executed as a subprocess of the agent. When the command dies, so does the agent. The agent initially does not have any private keys. Keys are added using ssh-add(1), which sends the identity to the agent. Several identi- ties can be stored in the agent; the agent can automatically use any of these identities. Use the -l option in ssh-add(1) to display the identities currently held by the agent. The agent is run in the user's local host. Authentication data need not be stored on any other machine, and authentication passphrases never go over the network. However, if the connection to the agent is forwarded over SSH remote logins, the user can use the privileges given by the identities anywhere in the network in a secure way. There are two main ways to get an agent setup. Either you let the agent start a new subcommand into which some environment variables are exported, or you let the agent print the needed shell commands (either sh(1) or csh(1) syntax can be generated) which can be evalled in the calling shell. Later, use ssh(1) to look at these variables and use them to establish a connection to the agent. A unix-domain socket is created (/tmp/ssh-XXXXXXXX/agent.pid) and the name of this socket is stored in the SSH_AUTH_SOCK environment vari- able. The socket is made accessible only to the current user. This method is easily abused by root or another instance of the same user. The SSH_AGENT_PID environment variable holds the agent's PID. The agent exits automatically when the command given on the command line terminates. OPTIONS
The following options are supported: -a bind_address Binds the agent to the unix-domain socket bind_address. The default is /tmp/ssh-XXXXXXXX/agent.pid. -c Generates C-shell commands on stdout. This is the default if SHELL indicates that it is a csh style of shell. -d Debug mode. When this option is specified, ssh-agent will not fork. -k Kills the current agent (given by the SSH_AGENT_PID environment variable). -s Generates Bourne shell commands on stdout. This is the default if SHELL does not indicate that it is a csh style of shell. EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error occurred. FILES
/tmp/ssh-XXXXXXXX/agent.pid Unix-domain sockets used to contain the connection to the authentication agent. These sockets should only be readable by the owner. The sockets are removed when the agent exits. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsshu | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
ssh(1), ssh-add(1), ssh-keygen(1), sshd(1M), attributes(5) System Administration Guide: Security Services SunOS 5.11 17 Nov 2008 ssh-agent(1)
All times are GMT -4. The time now is 01:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy