Lines Matching refs:SSL
13 * These represent running "tunnels". Eg. if you wanted to do SSL in a
20 * The underlying SSL state machine. This is a data-only processing unit
25 * The file-descriptors for the "dirty" (encrypted) side of the SSL
31 * The file-descriptors for the "clean" (unencrypted) side of the SSL
70 * Our SSL_CTX, which is configured as the SSL client or server and has
75 * Simple flag with complex logic :-) Indicates whether we're an SSL
76 * server or an SSL client.
150 " -server <0|1> (default = 0, ie. an SSL client)\n"
151 " -flipped <0|1> (makes SSL servers be network clients, and vice versa)\n"
164 " -out_state (prints SSL handshake states)\n"
169 "(1) It is recommended to specify a cert+key when operating as an SSL server.\n"
182 " as an ssl *server* in the SSL/TLS protocol), and an 'ssl client tunala'\n"
184 " SSL/TLS protocol) and proxies 'clean' to the end destination. This can\n"
314 " SSL traffic; %8lu bytes in, %8lu bytes out\n";
532 fprintf(stderr, "WARNING: you are running an SSL server without "
559 fprintf(stderr, "Info, set to operate as an SSL %s\n",
859 /* out_state (output of SSL handshake states to screen). */
1015 SSL *new_ssl = NULL;
1020 fprintf(stderr, "Error creating new SSL\n");
1044 * We use the SSL's "app_data" to indicate a call-back induced "kill"
1161 * If the SSL closes, it will also zero-out the _in buffers and will
1171 * If only one side closed, notify the SSL of this so it can take