Matches in DBpedia 2016-04 for { <http://dbpedia.org/resource/Challenge–response_authentication> ?p ?o }
Showing triples 1 to 81 of
81
with 100 triples per page.
- Challenge–response_authentication abstract "In computer security, challenge-response authentication is a family of protocols in which one party presents a question (\"challenge\") and another party must provide a valid answer (\"response\") to be authenticated.The simplest example of a challenge-response protocol is password authentication, where the challenge is asking for the password and the valid response is the correct password.Clearly an adversary who can eavesdrop on a password authentication can then authenticate itself in the same way. One solution is to issue multiple passwords, each of them marked with an identifier. For instance, p1=pv4OAFx1Q2cQ, p2=DsYfX3Ke, and so on. The verifier can ask for any of the passwords, and the prover must have that correct password for that identifier. Assuming that the passwords are chosen independently, an adversary who intercepts one challenge-response message pair has no clues to help with a different challenge at a different time.For example, when other communications security methods are unavailable, the U.S. military uses the AKAC-1553 TRIAD numeral cipher to authenticate and encrypt some communications. TRIAD includes a list of three-letter challenge codes, which the verifier is supposed to choose randomly from, and random three-letter responses to them. For added security, each set of codes is only valid for a particular time period which is ordinarily 24 hours.A more interesting challenge-response technique works as follows: Say \"Bob\" is controlling access to some resource. Alice comes along seeking entry. Bob issues a challenge, perhaps \"52w72y\". Alice must respond with the one string of characters which \"fits\" the challenge Bob issued. The \"fit\" is determined by an algorithm \"known\" to Bob and Alice. (The correct response MIGHT be as simple as \"63x83z\" (each character of response one more than that of challenge)... but in the real world, the \"rules\" would be much more complex.) Bob issues a different challenge each time, and thus knowing a previous correct response... even if it isn't \"hidden\" by the means of communication used between Alice and Bob... is of no use. A part of Alice's response might convey that it is Alice (or the specific dongle she was supposed to be keeping secure) who is seeking authentication.Software in the 1980s and 1990s often used a similar method for copy protection: challenges would be questions like \"What is the second word in the third paragraph on page 418 of the manual?\". The security assumption was that copying the manual was more difficult than copying the software disk. Sometimes the manual would be printed in such a way that contemporary photocopy machines couldn't duplicate the pages.".
- Challenge–response_authentication wikiPageExternalLink ssh-procedures.
- Challenge–response_authentication wikiPageID "412627".
- Challenge–response_authentication wikiPageLength "10142".
- Challenge–response_authentication wikiPageOutDegree "60".
- Challenge–response_authentication wikiPageRevisionID "698083434".
- Challenge–response_authentication wikiPageWikiLink AKAC-1553.
- Challenge–response_authentication wikiPageWikiLink Algorithm.
- Challenge–response_authentication wikiPageWikiLink Alice_and_Bob.
- Challenge–response_authentication wikiPageWikiLink Authentication.
- Challenge–response_authentication wikiPageWikiLink Brute-force_attack.
- Challenge–response_authentication wikiPageWikiLink CAPTCHA.
- Challenge–response_authentication wikiPageWikiLink CRAM-MD5.
- Challenge–response_authentication wikiPageWikiLink Category:Authentication_methods.
- Challenge–response_authentication wikiPageWikiLink Category:Computer_access_control.
- Challenge–response_authentication wikiPageWikiLink Challenge-Handshake_Authentication_Protocol.
- Challenge–response_authentication wikiPageWikiLink Channel_(communications).
- Challenge–response_authentication wikiPageWikiLink Communications_security.
- Challenge–response_authentication wikiPageWikiLink Computer_security.
- Challenge–response_authentication wikiPageWikiLink Copy_protection.
- Challenge–response_authentication wikiPageWikiLink Cryptographic_hash_function.
- Challenge–response_authentication wikiPageWikiLink Cryptographic_nonce.
- Challenge–response_authentication wikiPageWikiLink Cryptographically_secure_pseudorandom_number_generator.
- Challenge–response_authentication wikiPageWikiLink Dictionary_attack.
- Challenge–response_authentication wikiPageWikiLink Distance-bounding_protocol.
- Challenge–response_authentication wikiPageWikiLink Dongle.
- Challenge–response_authentication wikiPageWikiLink Eavesdropping.
- Challenge–response_authentication wikiPageWikiLink Encryption.
- Challenge–response_authentication wikiPageWikiLink Internet.
- Challenge–response_authentication wikiPageWikiLink Kerberos_(protocol).
- Challenge–response_authentication wikiPageWikiLink Key_derivation_function.
- Challenge–response_authentication wikiPageWikiLink Man-in-the-middle_attack.
- Challenge–response_authentication wikiPageWikiLink Mutual_authentication.
- Challenge–response_authentication wikiPageWikiLink Needham–Schroeder_protocol.
- Challenge–response_authentication wikiPageWikiLink Optical_character_recognition.
- Challenge–response_authentication wikiPageWikiLink Otway–Rees_protocol.
- Challenge–response_authentication wikiPageWikiLink Password.
- Challenge–response_authentication wikiPageWikiLink Password-authenticated_key_agreement.
- Challenge–response_authentication wikiPageWikiLink Plaintext.
- Challenge–response_authentication wikiPageWikiLink RSA_(cryptosystem).
- Challenge–response_authentication wikiPageWikiLink Reflection_attack.
- Challenge–response_authentication wikiPageWikiLink Replay_attack.
- Challenge–response_authentication wikiPageWikiLink SQRL.
- Challenge–response_authentication wikiPageWikiLink Salted_Challenge_Response_Authentication_Mechanism.
- Challenge–response_authentication wikiPageWikiLink Secure_Remote_Password_protocol.
- Challenge–response_authentication wikiPageWikiLink Secure_Shell.
- Challenge–response_authentication wikiPageWikiLink Shared_secret.
- Challenge–response_authentication wikiPageWikiLink Spambot.
- Challenge–response_authentication wikiPageWikiLink Turing_test.
- Challenge–response_authentication wikiPageWikiLink United_States.
- Challenge–response_authentication wikiPageWikiLink Unix.
- Challenge–response_authentication wikiPageWikiLink Wide_Mouth_Frog_protocol.
- Challenge–response_authentication wikiPageWikiLink World_Wide_Web.
- Challenge–response_authentication wikiPageWikiLink Zero-knowledge_password_proof.
- Challenge–response_authentication wikiPageWikiLinkText "Challenge–response authentication".
- Challenge–response_authentication wikiPageWikiLinkText "challenge question".
- Challenge–response_authentication wikiPageWikiLinkText "challenges/responses".
- Challenge–response_authentication wikiPageWikiLinkText "challenge–response authentication".
- Challenge–response_authentication wikiPageWikiLinkText "challenge–response".
- Challenge–response_authentication wikiPageUsesTemplate Template:For.
- Challenge–response_authentication wikiPageUsesTemplate Template:Reflist.
- Challenge–response_authentication wikiPageUsesTemplate Template:Wikibooks.
- Challenge–response_authentication subject Category:Authentication_methods.
- Challenge–response_authentication subject Category:Computer_access_control.
- Challenge–response_authentication hypernym Family.
- Challenge–response_authentication type Method.
- Challenge–response_authentication type Protocol.
- Challenge–response_authentication type Redirect.
- Challenge–response_authentication comment "In computer security, challenge-response authentication is a family of protocols in which one party presents a question (\"challenge\") and another party must provide a valid answer (\"response\") to be authenticated.The simplest example of a challenge-response protocol is password authentication, where the challenge is asking for the password and the valid response is the correct password.Clearly an adversary who can eavesdrop on a password authentication can then authenticate itself in the same way. ".
- Challenge–response_authentication label "Challenge–response authentication".
- Challenge–response_authentication sameAs Q1059963.
- Challenge–response_authentication sameAs Challenge-response.
- Challenge–response_authentication sameAs Challenge-Response-Authentifizierung.
- Challenge–response_authentication sameAs Protocolos_desafío-respuesta.
- Challenge–response_authentication sameAs פרוטוקול_אתגר-מענה.
- Challenge–response_authentication sameAs Challenge_response-authenticatie.
- Challenge–response_authentication sameAs m.0258y2.
- Challenge–response_authentication sameAs Вызов-ответ_(аутентификация).
- Challenge–response_authentication sameAs Q1059963.
- Challenge–response_authentication wasDerivedFrom Challenge–response_authentication?oldid=698083434.
- Challenge–response_authentication isPrimaryTopicOf Challenge–response_authentication.