Sun Fire E25K Server
 
Sun Fire E20K Server
 
Sun Fire 12K Server
 
Sun Fire 15K Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-Exxk
 
.Old GCS Categories>Sun Microsystems>Servers>High-End Servers
 

Applies to:

Goal

Solution

These two operations needed to complete without the use of rsh and ssh. To do so all usage of rsh/ssh has been removed and replaced with the new communication interface: zoed.

Zoed has been created to handle the communication and execution of these operations.

The new SMS daemon zoed will handle the sending and receiving of these two operations. The communication path is through the I2 network. To ensure security over the path, a root-only numbered socket and the following sequence is used:

1. The sender opens a socket to the receiver and tells it that it has some pending request.
2. The receiver opens a socket to the sender and asks what the request is.
3. The sender verifies the IP address of the receiver is the one configured, and on the same socket, sends the request.

This method ensures that the sender is a root process on the remote SC.

Implementation details:

• The pending request message consists of a simple string, "REQST".
• The asking for request message consists of a simple string, "WHAT?"
• The OS shutdown request message consists of a simple string, "HALT:"
• The post results request message consists of a simple string, "POST:"
• Any other messages received are responded to with the string "ERROR" and are ignored.

This daemon is also a door server that listens for proxy requests from the new proxy library. When it gets a request it will verify via door_cred that the requestor is a root process. Both fomd and the sms startup script, the only clients, are root processes.

Because the startup script (/etc/init.d/zoedsms; /etc/rc3.d/S89zoedsms) is unable to call proxy libraries directly it requires a cli to contact zoed. zoed itself is the cli that the script will use. With a command line flag, zoed will not start as a daemon, but act as a cli and send the request to the zoed daemon. This behavior only implements the sending of post data, not both zoed operations, as the script only performs that one operation.

Zoed uses port 55 and is not managed by secure shell daemon.

This solution has no attachment