Josh Soref
b3ab7a48cc
* accumulating * acquire * alignment * appropriate * argument * assign * attribute * authenticate * authentication * authenticator * authority * auxiliary * brackets * callback * camellia * can't * cancelability * certificate * choinyambuu * chunk * collector * collision * communicating * compares * compatibility * compressed * confidentiality * configuration * connection * consistency * constraint * construction * constructor * database * decapsulated * declaration * decrypt * derivative * destination * destroyed * details * devised * dynamic * ecapsulation * encoded * encoding * encrypted * enforcing * enumerator * establishment * excluded * exclusively * exited * expecting * expire * extension * filter * firewall * foundation * fulfillment * gateways * hashing * hashtable * heartbeats * identifier * identifiers * identities * identity * implementers * indicating * initialize * initiate * initiation * initiator * inner * instantiate * legitimate * libraries * libstrongswan * logger * malloc * manager * manually * measurement * mechanism * message * network * nonexistent * object * occurrence * optional * outgoing * packages * packets * padding * particular * passphrase * payload * periodically * policies * possible * previously * priority * proposal * protocol * provide * provider * pseudo * pseudonym * public * qualifier * quantum * quintuplets * reached * reading * recommendation to * recommendation * recursive * reestablish * referencing * registered * rekeying * reliable * replacing * representing * represents * request * request * resolver * result * resulting * resynchronization * retriable * revocation * right * rollback * rule * rules * runtime * scenario * scheduled * security * segment * service * setting * signature * specific * specified * speed * started * steffen * strongswan * subjectaltname * supported * threadsafe * traffic * tremendously * treshold * unique * uniqueness * unknown * until * upper * using * validator * verification * version * version * warrior Closes strongswan/strongswan#164.
12 lines
750 B
Plaintext
12 lines
750 B
Plaintext
The roadwarriors <b>carol</b> and <b>dave</b> set up a connection to gateway <b>moon</b>.
|
|
At the outset the gateway authenticates itself to the clients by sending
|
|
an IKEv2 <b>RSA signature</b> accompanied by a certificate.
|
|
The roadwarriors then use the <i>Extensible Authentication Protocol</i>
|
|
in association with an <i>MD5</i> challenge and response protocol
|
|
(<b>EAP-MD5</b>) to authenticate against the gateway <b>moon</b> and includes
|
|
a <b>Postquantum Preshared Key (PPK)</b> that's also mixed into the
|
|
derived key material. The PPK_ID used by <b>dave</b> is unknown to <b>moon</b>
|
|
but since both peers don't enforce the use of a PPK they fall back to regular
|
|
authentication by use of the authentication data provided in the NO_PPK_AUTH
|
|
notify.
|