| @@ -2,24 +2,27 @@ · 1 unmodified line |
| 2 | .SH NAME | 2 | .SH NAME |
| 3 | ssl \- secure sockets layer device | 3 | ssl \- secure sockets layer device |
| 4 | .SH SYNOPSIS | 4 | .SH SYNOPSIS |
| 5 | .B bind '#D' /n/ssl | 5 | .B #D/clone |
| 6 | .PP | 6 | .br |
| 7 | .B /n/ssl/clone | 7 | .BI #D/ n |
| | 8 | .br |
| | 9 | .BI #D/ n /data |
| 8 | .br | 10 | .br |
| 9 | .BI /n/ssl/ n | 11 | .BI #D/ n /ctl |
| 10 | .br | 12 | .br |
| 11 | .BI /n/ssl/ n /data | 13 | .BI #D/ n /secretin |
| 12 | .br | 14 | .br |
| 13 | .BI /n/ssl/ n /ctl | 15 | .BI #D/ n /secretout |
| 14 | .br | 16 | .br |
| 15 | .BI /n/ssl/ n /secretin | 17 | .BI #D/ n /encalgs |
| 16 | .br | 18 | .br |
| 17 | .BI /n/ssl/ n /secretout | 19 | .BI #D/ n /hashalgs |
| 18 | .SH DESCRIPTION | 20 | .SH DESCRIPTION |
| 19 | The | 21 | The |
| 20 | .I ssl | 22 | .I ssl |
| 21 | device provides access to a Secure Socket Layer that implements the record layer protocol | 23 | device provides access to a Secure Socket Layer that implements the record layer protocol |
| 22 | of SSLv2. | 24 | of SSLv2 |
| | 25 | (but not its handshaking). |
| 23 | The device provides encrypting and digesting for many independent connections. | 26 | The device provides encrypting and digesting for many independent connections. |
| 24 | Once associated with a network connection, the | 27 | Once associated with a network connection, the |
| 25 | .I ssl | 28 | .I ssl |
| @@ -29,6 +32,10 @@ can send data in the clear, digested or encrypted. In all cases, if · 3 unmodified lines |
| 29 | .I ssl | 32 | .I ssl |
| 30 | is associated with both ends of a connection, all messages are delimited. | 33 | is associated with both ends of a connection, all messages are delimited. |
| 31 | As long as reads always specify buffers that are of equal or greater lengths than the writes at the other end of the connection, one write will correspond to one read. | 34 | As long as reads always specify buffers that are of equal or greater lengths than the writes at the other end of the connection, one write will correspond to one read. |
| | 35 | The device is unusual because it is not bound into the name space but named directly by its local name, |
| | 36 | .BR #D . |
| | 37 | That is because the interface described below requires writing a local file descriptor number to a file, |
| | 38 | which will not work remotely. |
| 32 | .PP | 39 | .PP |
| 33 | The top-level directory contains a | 40 | The top-level directory contains a |
| 34 | .B clone | 41 | .B clone |
| @@ -41,16 +48,17 @@ will be open on the control file, · 6 unmodified lines |
| 41 | .BR ctl , | 48 | .BR ctl , |
| 42 | in the directory that represents the new connection. | 49 | in the directory that represents the new connection. |
| 43 | Reading the control file will return a text string giving the connection number | 50 | Reading the control file will return a text string giving the connection number |
| 44 | (and thus the directory name). | 51 | .IR n , |
| | 52 | and thus the directory name. |
| 45 | .PP | 53 | .PP |
| 46 | Writing to | 54 | Writing to |
| 47 | .B ctl | 55 | .B ctl |
| 48 | controls the corresponding connection. | 56 | controls the corresponding connection. |
| 49 | The following control messages are possible: | 57 | The following control messages are possible: |
| 50 | .TP | 58 | .TP |
| 51 | .BI fd " n" | 59 | .BI fd " m" |
| 52 | Associate the network connection on file descriptor | 60 | Associate the network connection on existing file descriptor |
| 53 | .I n | 61 | .I m |
| 54 | with the | 62 | with the |
| 55 | .I ssl | 63 | .I ssl |
| 56 | device. | 64 | device. |