| http://dbpedia.org/ontology/abstract
|
The cookie exchange in IPsec comes under t … The cookie exchange in IPsec comes under the Oakley protocol, which is a protocol of key management. The cookie exchange requires that each side send a pseudorandom number, the cookie, in the initial message, which the other side acknowledges. This acknowledgement must be repeated in the first message of the Diffie–Hellman key exchange. If the source address was forged, the opponent gets no answer. Thus, an opponent can only force a user to generate acknowledgements and not to perform the Diffie–Hellman calculation. Note that "cookies" in the sense of IPsec are unrelated to HTTP cookies used by web browsers. The recommended method for creating the cookie is to perform a fast hash (e.g. MD5) over the IP source and destination addresses, the UDP source and destination ports, and a locally generated secret value.rts, and a locally generated secret value.
|
| http://dbpedia.org/ontology/wikiPageID
|
3441938
|
| http://dbpedia.org/ontology/wikiPageLength
|
1390
|
| http://dbpedia.org/ontology/wikiPageRevisionID
|
981175184
|
| http://dbpedia.org/ontology/wikiPageWikiLink
|
http://dbpedia.org/resource/IPsec +
, http://dbpedia.org/resource/Diffie%E2%80%93Hellman_key_exchange +
, http://dbpedia.org/resource/MD5 +
, http://dbpedia.org/resource/Category:Internet_protocols +
, http://dbpedia.org/resource/Hash_function +
, http://dbpedia.org/resource/Pseudorandom +
, http://dbpedia.org/resource/Oakley_protocol +
, http://dbpedia.org/resource/Internet_Protocol +
, http://dbpedia.org/resource/HTTP_cookie +
|
| http://dbpedia.org/property/wikiPageUsesTemplate
|
http://dbpedia.org/resource/Template:Refimprove +
, http://dbpedia.org/resource/Template:About +
, http://dbpedia.org/resource/Template:Reflist +
|
| http://purl.org/dc/terms/subject
|
http://dbpedia.org/resource/Category:Internet_protocols +
|
| http://purl.org/linguistics/gold/hypernym
|
http://dbpedia.org/resource/Protocol +
|
| http://www.w3.org/ns/prov#wasDerivedFrom
|
http://en.wikipedia.org/wiki/Cookie_exchange?oldid=981175184&ns=0 +
|
| http://xmlns.com/foaf/0.1/isPrimaryTopicOf
|
http://en.wikipedia.org/wiki/Cookie_exchange +
|
| owl:sameAs |
http://www.wikidata.org/entity/Q5167098 +
, https://global.dbpedia.org/id/4iJht +
, http://rdf.freebase.com/ns/m.09cmcs +
, http://yago-knowledge.org/resource/Cookie_exchange +
, http://dbpedia.org/resource/Cookie_exchange +
|
| rdf:type |
http://dbpedia.org/class/yago/Message106598915 +
, http://dbpedia.org/class/yago/Protocol106665108 +
, http://dbpedia.org/ontology/Software +
, http://dbpedia.org/class/yago/Direction106786629 +
, http://dbpedia.org/class/yago/Rule106652242 +
, http://dbpedia.org/class/yago/WikicatInternetProtocols +
, http://dbpedia.org/class/yago/Abstraction100002137 +
, http://dbpedia.org/class/yago/Communication100033020 +
|
| rdfs:comment |
The cookie exchange in IPsec comes under t … The cookie exchange in IPsec comes under the Oakley protocol, which is a protocol of key management. The cookie exchange requires that each side send a pseudorandom number, the cookie, in the initial message, which the other side acknowledges. This acknowledgement must be repeated in the first message of the Diffie–Hellman key exchange. If the source address was forged, the opponent gets no answer. Thus, an opponent can only force a user to generate acknowledgements and not to perform the Diffie–Hellman calculation. Note that "cookies" in the sense of IPsec are unrelated to HTTP cookies used by web browsers.ated to HTTP cookies used by web browsers.
|
| rdfs:label |
Cookie exchange
|
