aboutsummaryrefslogtreecommitdiffstats
path: root/src/tls/tls_channel.h
Commit message (Collapse)AuthorAgeFilesLines
* Indentationlloyd2012-02-271-2/+2
|
* Remove Alert::Level enum, replace with boollloyd2012-01-261-1/+1
|
* Change callback interface to pass the Alert object itself insteadlloyd2012-01-261-2/+2
| | | | | | of just the type code. Implement Alert::type_string
* Make Alert a first class object ala Version. Move the alert codes intolloyd2012-01-261-3/+4
| | | | the Alert class for namespacing.
* Since this branch is hugely API breaking already, go ahead and putlloyd2012-01-231-6/+10
| | | | | everything into a new namespace (Botan::TLS), removing the TLS_ prefixes on everything.
* I'm not sure if I like this asthetically, but passing around thelloyd2012-01-191-1/+1
| | | | | | | | | | | | | | | | | | entire handshake state in many cases makes things simpler to update, in that each message type already knows what it needs depending on the version, params, etc, and this way a) that knowledge doesn't need to percolate up the the actual client and server handshake code and b) each message type can be updated for new formats/version without having to change its callers. Downside is it hides the dependency information away, and makes it non-obvious what needs to be created beforehand for each message to work correctly. However this is (almost) entirely predicated on the handshake message flows, and these we control with the next expected message scheme, so this should be fairly safe to do. This checkin only updates the ones where it was immediately relevant but for consistency probably all of them should be updated in the same way.
* Rename queue_for_sending just sendlloyd2012-01-161-1/+1
|
* If we send the close notify alert, don't reset the reader because thelloyd2012-01-081-8/+9
| | | | | | | | | | | | | | | | | | | | counterparty might want to send us a matching close notify under the currently existing key state. New logic is if we send the alert our writer is reset (we will send nothing more), but leave the reader as is. The reader will then be reset if and when we get a close notify, or if the counterparty doesn't send one, we'll just end the connection normally. This will also deal with the case where there is some application data queued still in the recv buffer. Don't close in ~TLS_Channel: applications should do this explicitly when the application-level protocol is ended. Otherwise we'd send a close_notify upon, for instance, an uncaught exception unwinding the stack. Add an enum for the maximum size of any TLS ciphertext packet including header. Handy for apps. If we get a bad alert size report size we got.
* Remove the version getter in TLS_Channel - caller should use thelloyd2012-01-061-5/+0
| | | | | handshake callback info instead. Clean up the buffer consumption code in the record reader.
* Add a hook in TLS_Channel that is called when an alert is received.lloyd2012-01-041-0/+2
| | | | | | | | | Currently has the same behavior in client and server; if we got a NO_RENEGOTIATION alert, and we appear to be renegotiating, delete the state if it exists. Noticed when talking to OpenSSL 0.9.8g which rejects all renegotiation requests.
* Remove the support for writing application data before the handshakelloyd2012-01-041-2/+0
| | | | | completes. The client gets a callback when the handshake is complete so they can know exactly when it's OK to send.
* Make handshake completion function non-optional. Now returns a boollloyd2012-01-031-2/+2
| | | | specifying if the session should be saved to the session cache.
* Add support for client-side session resumptionlloyd2011-12-311-6/+7
|
* Rename the session type to 'TLS_Session'. Split the manager out intolloyd2011-12-301-3/+3
| | | | its own file. Rename tls_state to tls_handshake_state.
* Add a function for getting the version number of an active connection.lloyd2011-12-301-1/+9
| | | | | | | | Add a new callback that is called with the session info when a handshake completes. Currently only called on the server side as the client doesn't have session resumption yet. Rename CipherSuite to TLS_Cipher_Suite.
* Prevent ping-ponging of close alerts by tracking both if a handshakelloyd2011-12-301-3/+9
| | | | | has been completed and if the connection has been definitely closed by a fatal alert or a close notify.
* Many renegotiation fixes. Add support for the secure renegotiationlloyd2011-12-301-2/+37
| | | | | extension (client side only at the moment). Add an interface that allows applications to request renegotiation.
* About half an implementation of RFC 5746lloyd2011-12-291-0/+3
|
* Centralize a lot of the handshaking and message parsing in TLS_Channellloyd2011-12-231-0/+85
Also delete the obsolete/never worked CMS examples
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-22 23:10:28 +0000