Home
last modified time | relevance | path

Searched refs:tunneled (Results 1 – 19 of 19) sorted by relevance

/third_party/wpa_supplicant/wpa_supplicant-2.9_standard/wpa_supplicant/
Deap_testing.txt124 5) PEAPv1 required termination of negotiation on tunneled EAP-Success and new
361 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
367 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
378 - sends tunneled EAP-Success with MPPE keys and expects the authentication to
384 - sends tunneled EAP-Success with MPPE keys and expects to receive TLS ACK
389 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
DChangeLog937 * started using separate TLS library context for tunneled TLS
1392 * added support for configuring Phase 2 (inner/tunneled) authentication
1978 i.e., not tunneled, EAP-Success to terminate session since; this can
2064 i.e., not tunneled, EAP-Success to terminate session since; this can
2252 * PEAPv1: fixed tunneled EAP-Success reply handling to reply with TLS
2253 ACK, not tunneled EAP-Success (of which only the first byte was
2256 * PEAPv1: added support for terminating PEAP authentication on tunneled
2259 (some RADIUS servers require this whereas others require a tunneled
/third_party/wpa_supplicant/wpa_supplicant-2.9/wpa_supplicant/
Deap_testing.txt124 5) PEAPv1 required termination of negotiation on tunneled EAP-Success and new
361 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
367 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
378 - sends tunneled EAP-Success with MPPE keys and expects the authentication to
384 - sends tunneled EAP-Success with MPPE keys and expects to receive TLS ACK
389 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
DChangeLog884 * started using separate TLS library context for tunneled TLS
1339 * added support for configuring Phase 2 (inner/tunneled) authentication
1924 i.e., not tunneled, EAP-Success to terminate session since; this can
2010 i.e., not tunneled, EAP-Success to terminate session since; this can
2198 * PEAPv1: fixed tunneled EAP-Success reply handling to reply with TLS
2199 ACK, not tunneled EAP-Success (of which only the first byte was
2202 * PEAPv1: added support for terminating PEAP authentication on tunneled
2205 (some RADIUS servers require this whereas others require a tunneled
/third_party/gstreamer/gstplugins_base/gst-libs/gst/rtsp/
Dgstrtspconnection.c178 gboolean tunneled; member
868 conn->tunneled = FALSE; in setup_tunneling()
872 conn->tunneled = TRUE; in setup_tunneling()
950 conn->tunneled = FALSE; in setup_tunneling()
954 conn->tunneled = TRUE; in setup_tunneling()
973 conn->tunneled = TRUE; in setup_tunneling()
1049 if (conn->tunneled) { in gst_rtsp_connection_connect_with_response_usec()
1089 if (conn->tunneled) { in gst_rtsp_connection_connect_with_response_usec()
1954 if (conn->tunneled) { in gst_rtsp_connection_send_messages_usec()
2622 conn->tunneled = TRUE; in build_next()
[all …]
Dgstrtspconnection.h221 void gst_rtsp_connection_set_tunneled (GstRTSPConnection *conn, gboolean tunneled);
/third_party/wpa_supplicant/wpa_supplicant-2.9/hostapd/
Dhostapd.eap_user12 # [2] flag in the end of the line can be used to mark users for tunneled phase
DChangeLog800 * added support for fragmenting EAP-TTLS/PEAP/FAST Phase 2 (tunneled)
1017 tunneled identity into accounting messages when the RADIUS server
1100 * fixed PEAPv1 to use tunneled EAP-Success/Failure instead of EAP-TLV
/third_party/wpa_supplicant/wpa_supplicant-2.9_standard/hostapd/
Dhostapd.eap_user12 # [2] flag in the end of the line can be used to mark users for tunneled phase
DChangeLog843 * added support for fragmenting EAP-TTLS/PEAP/FAST Phase 2 (tunneled)
1060 tunneled identity into accounting messages when the RADIUS server
1143 * fixed PEAPv1 to use tunneled EAP-Success/Failure instead of EAP-TLV
/third_party/ffmpeg/doc/
Dprotocols.texi881 Real-Time Messaging Protocol tunneled through HTTP.
883 The Real-Time Messaging Protocol tunneled through HTTP (RTMPT) is used
889 Encrypted Real-Time Messaging Protocol tunneled through HTTP.
891 The Encrypted Real-Time Messaging Protocol tunneled through HTTP (RTMPTE)
897 Real-Time Messaging Protocol tunneled through HTTPS.
899 The Real-Time Messaging Protocol tunneled through HTTPS (RTMPTS) is used
979 functions needed to support RTMP, RTMP tunneled in HTTP (RTMPT),
980 encrypted RTMP (RTMPE), RTMP over SSL/TLS (RTMPS) and tunneled
1207 Watch a stream tunneled over HTTP:
/third_party/python/Doc/library/
Dhttp.client.rst345 The host and port arguments specify the endpoint of the tunneled connection
/third_party/nghttp2/
DREADME.rst917 The backend HTTP/2 connections can be tunneled through an HTTP proxy.
/third_party/gstreamer/gstplugins_good/
DNEWS851 - rtspsrc: now supports IPv6 also for tunneled mode (RTSP-over-HTTP);
/third_party/gstreamer/gst_libav/
DNEWS851 - rtspsrc: now supports IPv6 also for tunneled mode (RTSP-over-HTTP);
/third_party/gstreamer/gstplugins_bad/
DNEWS851 - rtspsrc: now supports IPv6 also for tunneled mode (RTSP-over-HTTP);
/third_party/gstreamer/gstreamer/
DNEWS851 - rtspsrc: now supports IPv6 also for tunneled mode (RTSP-over-HTTP);
/third_party/gstreamer/gstplugins_base/
DNEWS851 - rtspsrc: now supports IPv6 also for tunneled mode (RTSP-over-HTTP);
DChangeLog2848 gstrtspconnection: Add IPv6 support for tunneled mode
2850 Add brackets for IPv6 address used for tunneled mode,
2851 for non-tunneled this is already supported.
4956 gstrtspconnection: correct data_size when tunneled mode
4957 gst_rtsp_connection_send_messages_usec in tunneled mode does base64
53458 rtspconnection: Use relative URI for non-proxy tunneled requests
53473 connection is configured to be tunneled. The motivation for this is to
69527 tunneled connections can be modified.
69612 rtspconnection: Call closed() when GET is closed in tunneled mode
69613 This patch adds read source on the write socket in tunneled
[all …]