Unified · Split
| @@ -1,53 +1,11 @@ | |||
| 1 | .TH RSTYXD 8 | 1 | .TH RSTYXD 8 |
| 2 | .SH NAME | 2 | .SH NAME |
| 3 | rstyxd, styxd \- Styx-based remote execution and file service | 3 | rstyxd \- Styx-based remote execution and file service |
| 4 | .SH SYNOPSIS | 4 | .SH SYNOPSIS |
| 5 | .B auxi/rstyxd | 5 | .B auxi/rstyxd |
| 6 | .I alg | 6 | .I alg |
| 7 | \&... | 7 | \&... |
| 8 | .PP | ||
| 9 | .B auxi/styxd | ||
| 10 | .I alg | ||
| 11 | \&... | ||
| 12 | .SH DESCRIPTION | 8 | .SH DESCRIPTION |
| 13 | These services are normally started by | ||
| 14 | .IR svc (8) | ||
| 15 | in response to incoming network calls. | ||
| 16 | Each expects the standard input to be connected to the client; | ||
| 17 | unusually, it is both read and written. | ||
| 18 | .PP | ||
| 19 | Both commands first authenticate the incoming call using | ||
| 20 | .IR keyring-auth (2) | ||
| 21 | via | ||
| 22 | .IR security-auth (2). | ||
| 23 | On successful authorisation, the server sets | ||
| 24 | its user identity to that of the caller, | ||
| 25 | and the client can request that a digest and/or encryption | ||
| 26 | algorithm be applied using | ||
| 27 | .IR ssl (3) | ||
| 28 | to protect the data exchanged with the server. | ||
| 29 | Each | ||
| 30 | .I alg | ||
| 31 | names a digest or encryption algorithm that the server will allow | ||
| 32 | the client to use, | ||
| 33 | in any form accepted by | ||
| 34 | .IR ssl ; | ||
| 35 | the special name | ||
| 36 | .B none | ||
| 37 | is usually listed, to allow the client to choose not to use | ||
| 38 | .IR ssl . | ||
| 39 | .PP | ||
| 40 | .I Styxd | ||
| 41 | provides Styx file service to its client. | ||
| 42 | Having authorised the client and optionally established | ||
| 43 | .IR ssl , | ||
| 44 | as described above, | ||
| 45 | it exports its name space (usually the name space inherited from | ||
| 46 | .IR svc (8)) | ||
| 47 | on the connection using | ||
| 48 | .B Sys->export | ||
| 49 | (see | ||
| 50 | .IR sys-dial (2)). | ||
| 51 | .PP | 9 | .PP |
| 52 | .I Rstyxd | 10 | .I Rstyxd |
| 53 | provides a remote-execution service. | 11 | provides a remote-execution service. |
| @@ -82,6 +40,34 @@ and opens the new · 28 unmodified lines | |||
| 82 | .BR /dev/cons ) | 40 | .BR /dev/cons ) |
| 83 | on file descriptors 0, 1 and 2. | 41 | on file descriptors 0, 1 and 2. |
| 84 | Finally, it executes the command. | 42 | Finally, it executes the command. |
| 43 | .PP | ||
| 44 | .I Rstyxd | ||
| 45 | is normally started by | ||
| 46 | .IR svc (8) | ||
| 47 | in response to incoming network calls. | ||
| 48 | It expects the standard input to be connected to the client; | ||
| 49 | unusually, it is both read and written. | ||
| 50 | It | ||
| 51 | first authenticates the incoming call using | ||
| 52 | .IR keyring-auth (2) | ||
| 53 | via | ||
| 54 | .IR security-auth (2). | ||
| 55 | On successful authorisation, the server sets | ||
| 56 | its user identity to that of the caller, | ||
| 57 | and the client can request that a digest and/or encryption | ||
| 58 | algorithm be applied using | ||
| 59 | .IR ssl (3) | ||
| 60 | to protect the data exchanged with the server. | ||
| 61 | Each | ||
| 62 | .I alg | ||
| 63 | names a digest or encryption algorithm that the server will allow | ||
| 64 | the client to use, | ||
| 65 | in any form accepted by | ||
| 66 | .IR ssl ; | ||
| 67 | the special name | ||
| 68 | .B none | ||
| 69 | is usually listed, to allow the client to choose not to use | ||
| 70 | .IR ssl . | ||
| 85 | .SH FILES | 71 | .SH FILES |
| 86 | .TF /usr/user/keyring/default | 72 | .TF /usr/user/keyring/default |
| 87 | .TP | 73 | .TP |
| @@ -96,8 +82,6 @@ run as given · 8 unmodified lines | |||
| 96 | .I user | 82 | .I user |
| 97 | .SH SOURCE | 83 | .SH SOURCE |
| 98 | .B /appl/cmd/auxi/rstyxd.b | 84 | .B /appl/cmd/auxi/rstyxd.b |
| 99 | .br | ||
| 100 | .B /appl/cmd/auxi/styxd.b | ||
| 101 | .SH SEE ALSO | 85 | .SH SEE ALSO |
| 102 | .IR keyring-auth (2), | 86 | .IR keyring-auth (2), |
| 103 | .IR security-auth (2), | 87 | .IR security-auth (2), |