1 - 2 - 3 - 4 - 6 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - R - S - T - U - V - W - X
mutual authentication
Click on the red underlined text to get to the source
... USB interface. The
method can be used to provide unilateral or mutual authentication,
and key material, in protocols utilizing EAP, such as PPP ...
... This mode is only to be used within a secured tunnel. A more
advanced variant provides mutual authentication, integrity protection
of the exchange, protection against ...
... EAP server, is intended to be interpreted and acted
upon by humans. Furthermore, EAP-POTP allows for mutual
authentication and establishment of keying material, which GTC does
...
... EAP-POTP method provides user authentication as defined below.
Additionally, it may provide mutual authentication (authenticating
the EAP server to the EAP ...
... authentication server so that the server can
authenticate the user. A more advanced variant provides mutual
authentication, protection against eavesdropping, and establishment
of authenticated ...
... response MUST be protected. Use of this bit also indicates that
mutual authentication will take place, as well as generation of
keying material. It is RECOMMENDED to always set the P bit ...
... POTP-X containing a Confirm TLV for mutual authentication,
the peer MUST save either all the input parameters to the
PBKDF2 ...
... EAP-Request until after the exchange of the Confirm TLV
(i.e., until after mutual authentication has occurred and keys are in
place to protect the TLV). The New PIN TLV ...
... Vendor-Specific TLV before protected
mode mutual authentication has occurred (since the Protected TLV,
Section 4.11.15, then can be used to protect all TLVs ...
... Ciphersuite negotiation: Yes (No in basic variant)
Mutual authentication: Yes (No in basic variant)
Integrity protection: Yes (No in basic variant)
...
...
The basic variant (i.e., when the protection of OTPs and mutual
authentication is not used) of this EAP method does not provide
...
... OTPs and new PINs, negotiation of cryptographic
algorithms, mutual authentication, and protection against replay
attacks and protocol version ...
... B.3. Mutual Authentication without Session Resumption ...
... B.4. Mutual Authentication with Transfer of Pepper ...
... B.5. Failed Mutual Authentication ...
... This example illustrates a failed session resumption, followed by a
complete mutual authentication. The user is identified through the
User Identifier TLV ...
... B.8. Mutual Authentication, and New PIN Requested. ...