{"push_id":1597156096,"size":1,"distinct_size":1,"ref":"refs/heads/2fa","head":"5e41ba8747e843ed8a64016810fcaf42d13c7904","before":"2ad4e7469c8da0b0304d06ba4af85a024160540b","commits":[{"sha":"5e41ba8747e843ed8a64016810fcaf42d13c7904","author":{"name":"Kyra","email":"c7c3b9c9c3fdfb33d09b8515f7478f31148e0e52@users.noreply.github.com"},"message":"Opt for string.replace() vs. re.sub() (#15)\n\n* Opt for string.replace vs. re.sub\r\n\r\nThe totp.verify() call in tfa.verify() will normally fail and return False if a space is in a TOTP code, as some 2FA apps like to put a space in the code. For instance, \"123 456\". The code would need to be provided as \"123456\" or the function would return False. Logically, the code is correct, technically, it is incorrect with the space. So tfa.verify() was altered to force the logically correct case to also be technically correct by force-stripping spaces. The space character is not a valid character in the recovery code charset. Add a test to make sure it functions as expected with a successful verification.","distinct":true,"url":"https://api.github.com/repos/kfkitsune/weasyl/commits/5e41ba8747e843ed8a64016810fcaf42d13c7904"}]}
{"actor":{"display_login":"kfkitsune"}}