Solaris SSH weird behaviour

Byetzion

Sun likes IPv6. They like it so badly that they strive to use it in all cases.

Solaris 9 and 10 SSH daemon is bounded to IPv6, which leads to a problem when trying to forward X. Editing the config file /etc/ssh/sshd_conf and assigning the SSH daemon to IPv4 address (bind to address 0.0.0.0) is not enough. You need to make sure that the sshd process is started with the “-4” flag. In Solaris 10, it means editing /lib/svc/method/sshd and appending “-4” to the sshd start command.

I wonder what will happen after an upgrade or a patch…

Related posts:

  1. How to create self-contained Solaris 10 x86 Jumpstart kit
  2. NetApp internals – how to add SSH keys without C$ nor NFS shares
  3. Minimal Centos5 and SSH Server with X forwarding

Powered by YARPP.

Similar Posts

SSH Client improvements

SSH Client improvements

Byetzion

This article is going to concentrate several SSH client related topics and optimisations I have implemented. Amongst are: SSH client modular configuration Initially, the configuration for SSH client should be present (per-user) in the user’s home directory, under .ssh/config. I believe that this configuration file is not modular enough, and when you want to add/edit/remove…

Service account

Byetzion

Assume you have a single purpose account. Maybe some service account, user which should run a single task ever, or even a case of a limited menu interface. You want your user(s) to reach there using SSH because that is the method to do it right and secured. You want it to be easy for…

VNC minimal server on RHEL8 / CentOS8 / OEL8

VNC minimal server on RHEL8 / CentOS8 / OEL8

Byetzion

With the update to version 8 (or, if to be accurate, according to common documentations, 8.3 and above), VNC configuration has had a major overhaul, and it is entirely different. Most documentations will refer to using ‘gnome’ as the desktop manager, however – if you want something lightweight with minimal impact (both package-wise and performance-wise),…

sign_and_send_pubkey: signing failed for RSA from agent: agent refused operation

sign_and_send_pubkey: signing failed for RSA from agent: agent refused operation

Byetzion

This is a problem which bugs the Internet. Many solutions were suggested. All of them work sometimes (like making sure that the permissions on the private/public SSH key files are correct). One solution which never gets mentioned is about DNS. When attempting login to a remote server, the server attempts to resolve the connecting address…

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.