▲ 1015 ▼ Brute force protection (rytter.me) submitted 2 years ago by anders@rytter.me to c/memes@lemmy.ml 103 comments fedilink hide all child comments Brute force protection @memes
[–] gibmiser@lemmy.world 128 points 2 years ago (4 children) As a non programmer, is the joke that humans will retype their password assuming that they made a typo? If so, sick indeed. permalink fedilink source hideshow 8 child comments replies: [–] Infynis@midwest.social 103 points 2 years ago (1 child) The guy coding made it so, on your first attempt, even if you answer correctly, it will tell you your login failed due to incorrect username or password, to joke about how it feels like you always get it wrong on the first try permalink fedilink source parent hideshow 2 child comments replies: [–] soloner@lemmy.world 17 points 2 years ago* (2 children) The logic is bugging me, though. It should be if isFirstAttempt || !isPasswordCorrect I understand the meme is trying to convey in spite of being correct to still return an error, but then it doesn't account for when the password is actually incorrect. permalink fedilink source parent hideshow 4 child comments replies: [–] QuaternionsRock@lemmy.world 47 points 2 years ago* That defeats the brute-force attack protection… The idea is that brute-force attackers will only check each password once, while real users will likely assume they mistyped and retype the same password. The code isn’t complete, and has nothing to do with actually incorrect passwords. permalink fedilink source parent [–] reflectedodds@lemmy.world 17 points 2 years ago (1 child) Like the other person said, it's not meant to always fail the first time you enter any password. It is meant to fail the first time you enter the correct password. permalink fedilink source parent hideshow 2 child comments replies: [–] winterayars@sh.itjust.works 1 point 2 years ago So it should be: if password == correct and first_success == true then { login failure; first_success = false } Something like that. permalink fedilink source parent [–] HopFlop@discuss.tchncs.de 83 points 2 years ago Yeah, hackers have automated tools and they will, of course, only try each password once. permalink fedilink source parent [–] NutWrench@lemmy.world 11 points 2 years ago I would assume that I was being phished and the attacker wanted me to re-type the password to verify that it's correct. permalink fedilink source parent [–] anders@rytter.me [S] 1 point 2 years ago @gibmiser Yes exactly 😂 permalink fedilink source parent
[–] Infynis@midwest.social 103 points 2 years ago (1 child) The guy coding made it so, on your first attempt, even if you answer correctly, it will tell you your login failed due to incorrect username or password, to joke about how it feels like you always get it wrong on the first try permalink fedilink source parent hideshow 2 child comments replies: [–] soloner@lemmy.world 17 points 2 years ago* (2 children) The logic is bugging me, though. It should be if isFirstAttempt || !isPasswordCorrect I understand the meme is trying to convey in spite of being correct to still return an error, but then it doesn't account for when the password is actually incorrect. permalink fedilink source parent hideshow 4 child comments replies: [–] QuaternionsRock@lemmy.world 47 points 2 years ago* That defeats the brute-force attack protection… The idea is that brute-force attackers will only check each password once, while real users will likely assume they mistyped and retype the same password. The code isn’t complete, and has nothing to do with actually incorrect passwords. permalink fedilink source parent [–] reflectedodds@lemmy.world 17 points 2 years ago (1 child) Like the other person said, it's not meant to always fail the first time you enter any password. It is meant to fail the first time you enter the correct password. permalink fedilink source parent hideshow 2 child comments replies: [–] winterayars@sh.itjust.works 1 point 2 years ago So it should be: if password == correct and first_success == true then { login failure; first_success = false } Something like that. permalink fedilink source parent
[–] soloner@lemmy.world 17 points 2 years ago* (2 children) The logic is bugging me, though. It should be if isFirstAttempt || !isPasswordCorrect I understand the meme is trying to convey in spite of being correct to still return an error, but then it doesn't account for when the password is actually incorrect. permalink fedilink source parent hideshow 4 child comments replies: [–] QuaternionsRock@lemmy.world 47 points 2 years ago* That defeats the brute-force attack protection… The idea is that brute-force attackers will only check each password once, while real users will likely assume they mistyped and retype the same password. The code isn’t complete, and has nothing to do with actually incorrect passwords. permalink fedilink source parent [–] reflectedodds@lemmy.world 17 points 2 years ago (1 child) Like the other person said, it's not meant to always fail the first time you enter any password. It is meant to fail the first time you enter the correct password. permalink fedilink source parent hideshow 2 child comments replies: [–] winterayars@sh.itjust.works 1 point 2 years ago So it should be: if password == correct and first_success == true then { login failure; first_success = false } Something like that. permalink fedilink source parent
[–] QuaternionsRock@lemmy.world 47 points 2 years ago* That defeats the brute-force attack protection… The idea is that brute-force attackers will only check each password once, while real users will likely assume they mistyped and retype the same password. The code isn’t complete, and has nothing to do with actually incorrect passwords. permalink fedilink source parent
[–] reflectedodds@lemmy.world 17 points 2 years ago (1 child) Like the other person said, it's not meant to always fail the first time you enter any password. It is meant to fail the first time you enter the correct password. permalink fedilink source parent hideshow 2 child comments replies: [–] winterayars@sh.itjust.works 1 point 2 years ago So it should be: if password == correct and first_success == true then { login failure; first_success = false } Something like that. permalink fedilink source parent
[–] winterayars@sh.itjust.works 1 point 2 years ago So it should be: if password == correct and first_success == true then { login failure; first_success = false } Something like that. permalink fedilink source parent
[–] HopFlop@discuss.tchncs.de 83 points 2 years ago Yeah, hackers have automated tools and they will, of course, only try each password once. permalink fedilink source parent
[–] NutWrench@lemmy.world 11 points 2 years ago I would assume that I was being phished and the attacker wanted me to re-type the password to verify that it's correct. permalink fedilink source parent
[–] anders@rytter.me [S] 1 point 2 years ago @gibmiser Yes exactly 😂 permalink fedilink source parent