| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
The assumption that connections are "Direct TLS" when a TLS context is
supplided should be broken. The goal is to make it easy to add a new API
that can be given a TLS context at creation even if it should do
STARTTLS.
With this commit, only the exposed server_select-compatible API assumes
Direct TLS when a TLS context is included.
|
|
|
|
|
| |
Eventually it should be possible to create a socket that has a TLS
context but that does not automatically start TLS on connect.
|
|
|
|
| |
No longer needed since util.logger does this now
|
| |
|
| |
|
| |
|
|
|
|
| |
(thanks LuaSec)
|
| |
|
|
|
|
| |
callback
|
| |
|
| |
|
| |
|
|
|
|
| |
buffer because the wantwrite flag must be unset regardless
|
| |
|
|
|
|
| |
called so it is only done once
|
| |
|
|
|
|
| |
c2s:show traceback in telnet console)
|
|
|
|
| |
if connection closed in onconnect)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
parent server
|
| |
|
| |
|
|
|
|
| |
data is lost in buffers
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
buffered data in it
|
|
|
|
| |
traceback when closed
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
connection is closed before onincoming returns
|
| |
|
| |
|
| |
|
| |
|