Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Solaris 10: Cannot ssh into machine- authentication issues
Top Forums UNIX for Dummies Questions & Answers Solaris 10: Cannot ssh into machine- authentication issues Post 302334914 by agummad on Thursday 16th of July 2009 08:58:23 PM
Old 07-16-2009
Thank you! I'll go though the security issues of the said config..
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

SSH into a linux machine from a windows machine

I basically want to login into different linux machines( on the same network) from a windows machine. I know i can use ssh <machine name>. But i want to automate this process. I dont want to enter the username and password. Is there any way to do it. Can i make some sort of a batch script for it. (4 Replies)
Discussion started by: lassimanji
4 Replies

2. Shell Programming and Scripting

ssh connection from remote machine in solaris

Hi! I have two solaris 10 machines(say 10.1.1.1,10.1.1.2). i have installed rsync on 10.1.1.2, 10.1.1.1::: Sun Microsystems Inc. SunOS 5.10 Generic January 2005 -bash-3.00$ ssh 10.1.1.2 "echo $PATH" Password:... (4 Replies)
Discussion started by: dddkiran
4 Replies

3. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

4. Solaris

SSH and PAM authentication issues on Solaris 10

This is a zone running Solaris 10u8 on a 6320 blade. The global zone is also running 10u8. One my users is attempting to change his password and getting a following screen: $ ssh remotesys Password: Warning: Your password has expired, please change it now. New Password: Re-enter new... (1 Reply)
Discussion started by: bluescreen
1 Replies

5. Shell Programming and Scripting

ssh into another machine without authentication

If another machine has the same account how to ssh into that machine as the same user without re-typing password? Thanks (2 Replies)
Discussion started by: stevensw
2 Replies

6. Solaris

Solaris 8 ssh public key authentication issue - Server refused our key

Hi, I've used the following way to set ssh public key authentication and it is working fine on Solaris 10, RedHat Linux and SuSE Linux servers without any problem. But I got error 'Server refused our key' on Solaris 8 system. Solaris 8 uses SSH2 too. Why? Please help. Thanks. ... (1 Reply)
Discussion started by: aixlover
1 Replies

7. Solaris

Solaris ssh client hangs when connecting to another Solaris machine

Got a strange problem. I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10. When I try to ssh from one Solaris 10 server to another server ssh hangs. I have an identical server and when I try this everything works fine. The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies

8. Red Hat

NTP Authentication Issues: Help Please!

Hello everyone, I've been trying to set up NTP authentication between a server and a workstation. Both point to the same NTP server which is on a different physical box with its own IP address. I followed the steps below but I get the following result. How can I get this working? Expected... (0 Replies)
Discussion started by: rchaud10
0 Replies

9. Red Hat

iptables applied in local machine, can't ssh remote machine after chain changed to DROP

I want to SSH to 192.168.1.15 Server from my machine, my ip was 192.168.1.99 Source Destination was UP, with IP 192.168.1.15. This is LAN Network there are 30 Machine's Connected to the network and working fine, I'm Playing around the local machine's because I need to apply the same rules in... (2 Replies)
Discussion started by: babinlonston
2 Replies

10. Solaris

Solaris 11 ssh on machine with multiple Ethernet ports

I have a server with 6 Ethernet ports. 4 are the the motherboard based 1 GBE ports and 2 are 10 GBE ports on NICs. I have set these all up with static IP addresses and use the standard /etc/nsswitch.files. My IP addresses are net0 192.168.1.82 net1 192.168.2.82 and so on till net5... (4 Replies)
Discussion started by: ashlaw
4 Replies

LEARN ABOUT CENTOS

pulse-client.conf

pulse-client.conf(5)						File Formats Manual					      pulse-client.conf(5)

NAME

       pulse-client.conf - PulseAudio client configuration file

SYNOPSIS

       ~/.config/pulse/client.conf

       /etc/pulse/client.conf

DESCRIPTION

       The  PulseAudio client library reads configuration directives from a file ~/.config/pulse/client.conf on startup and when that file doesn't
       exist from /etc/pulse/client.conf.

       The configuration file is a simple collection of variable declarations. If the configuration file  parser  encounters  either  ;  or  #	it
       ignores the rest of the line until its end.

       For the settings that take a boolean argument the values true, yes, on and 1 are equivalent, resp. false, no, off, 0.

DIRECTIVES

       default-sink=  The default sink to connect to. If specified overwrites the setting in the daemon. The environment variable $PULSE_SINK how-
       ever takes precedence.

       default-source= The default source to connect to. If specified overwrites the setting in the daemon. The environment variable $PULSE_SOURCE
       however takes precedence.

       default-server= The default sever to connect to. The environment variable $PULSE_SERVER takes precedence.

       autospawn= Autospawn a PulseAudio daemon when needed. Takes a boolean value, defaults to yes.

       daemon-binary= Path to the PulseAudio daemon to run when autospawning. Defaults to a path configured at compile time.

       extra-arguments= Extra arguments to pass to the PulseAudio daemon when autospawning. Defaults to --log-target=syslog

       cookie-file= Specify the path to the PulseAudio authentication cookie. Defaults to ~/.config/pulse/cookie.

       enable-shm= Enable data transfer via POSIX shared memory. Takes a boolean argument, defaults to yes.

       shm-size-bytes=	Sets the shared memory segment size for clients, in bytes. If left unspecified or is set to 0 it will default to some sys-
       tem-specific default, usually 64 MiB. Please note that usually there is no need to change this value, unless you are running an	OS  kernel
       that does not do memory overcommit.

       auto-connect-localhost=	Automatically try to connect to localhost via IP. Enabling this is a potential security hole since connections are
       only authenticated one-way and a rogue server might hence fool a client into sending it its private (e.g. VoIP call) data. This was enabled
       by default on PulseAudio version 0.9.21 and older. Defaults to no.

       auto-connect-display=  Automatically  try  to  connect  to the host X11's $DISPLAY variable is set to. The same security issues apply as to
       auto-connect-localhost=. Defaults to no.

AUTHORS

       The PulseAudio Developers <pulseaudio-discuss (at) lists (dot) freedesktop (dot) org>; PulseAudio is available from http://pulseaudio.org/

SEE ALSO

       pulse-daemon.conf(5), pulseaudio(1)

Manuals 							       User						      pulse-client.conf(5)
All times are GMT -4. The time now is 06:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy