UNIX for Advanced & Expert Users

Hi,
I'm trying to configure ssh for an application Unix account to remotely execute a command without a password but I've been getting a 'No xauth' warning message each time a remote command is executed.

[em1]$ exec /usr/bin/ssh-agent $SHELL
[em1]$ /usr/bin/ssh-add
Enter passphrase for /home/emapp/.ssh/id_rsa: <enter password>

[em1]$ ssh em2 hostname
Warning: No xauth; using fake authentication data for X11 forwarding.
em2

'ssh em2 hostname' returned the name of the remote host but it also displayed a warning message.

Any idea how I can get rid of the warning message?

OS: Solaris 8

Thanks in advance!

geraldine

Try the -q option for ssh -
quiet mode - causes all warning and diag messages to be suppressed.

See the man page for ssh for more info.

Thanks for the reply.

Unfortunately the ssh is issued by a vendor's software during an installation and I could not make any modification to it. The installation failed because of the warning message.

Are there any configuration changes that I need to do to prevent the warning message from appearing?

thanks.

Your examples aren't vendor code - you might have stated the true problem in the original post.

Your two options -
Have the vendor fix their code (Good luck)
or
try setting up an alias for ssh to be equal to ssh -q which may take care of the situation.

The warning isn't a bad thing - but the fact that the vendor didn't realize it could happen and code for the possiblities seems to show how well their software may be. Or, there may be a difference in the versions of ssh you are using which is causing your error (and has nothing to do with the vendor's code). And I've found in the past that vendor code can be changed (if it's a script) to get around these types of errors. If it is a script, is it downloaded to your UNIX server already or on cd?

I didn't find anything with a search that supplies an answer to changing your ssh configuration to get rid of the warning. You might want to post the exact scenerio - what type of servers involved, OS/version, ....

Thanks for your suggestion. The alias actually took care of the problem.

Thanks!