Difference between revisions of "SSLC:ContextInitSharedmem"
Jump to navigation
Jump to search
| Line 37: | Line 37: | ||
This maps the specified sharedmem, and writes the mapped vaddr + size into state. The sharedmem is not used for *anything* else by this command. | This maps the specified sharedmem, and writes the mapped vaddr + size into state. The sharedmem is not used for *anything* else by this command. | ||
| − | While starting the TLS connection, the entire server cert is written to sharedmem+0. Later a network TLS alert is thrown by SSL-module, when the user-process *only* cleared the sharedmem to all-zeros. | + | While starting the TLS connection, the entire server cert is written to sharedmem+0. Later a network TLS encrypted alert is thrown by SSL-module, when the user-process *only* cleared the sharedmem to all-zeros. |
Latest revision as of 22:56, 30 March 2016
Request[edit]
| Index Word | Description |
|---|---|
| 0 | Header code [0x001F0082] |
| 1 | SSL context handle |
| 2 | u32 size |
| 3 | Value 0x0, translate-header for handle transfer. |
| 4 | Sharedmem handle. |
Response[edit]
| Index Word | Description |
|---|---|
| 0 | Header code |
| 1 | Result code |
Description[edit]
This maps the specified sharedmem, and writes the mapped vaddr + size into state. The sharedmem is not used for *anything* else by this command.
While starting the TLS connection, the entire server cert is written to sharedmem+0. Later a network TLS encrypted alert is thrown by SSL-module, when the user-process *only* cleared the sharedmem to all-zeros.