Difference between revisions of "Talk:1820: Security Advice"
| Line 14: | Line 14: | ||
Maybe you really should use a secure font [https://technet.microsoft.com/library/security/MS15-078 Font related bug] [[Special:Contributions/162.158.79.161|162.158.79.161]] 15:13, 5 April 2017 (UTC) | Maybe you really should use a secure font [https://technet.microsoft.com/library/security/MS15-078 Font related bug] [[Special:Contributions/162.158.79.161|162.158.79.161]] 15:13, 5 April 2017 (UTC) | ||
| + | |||
| + | Should the blue check mark tip be noted as only being useful on Twitter? Usually, the advice doesn't apply to emails, which are significantly more likely to ask for your less-secret account details, but also significantly less likely to have a blue check mark. [[Special:Contributions/162.158.2.10|162.158.2.10]] 15:15, 5 April 2017 (UTC) | ||
Revision as of 15:15, 5 April 2017
Secret questions are not 2-factor authentication (2FA). They are just a really shitty password, something that you know. --JakubNarebski (talk) 14:33, 5 April 2017 (UTC)
Secret questions are more like 0-factor authentication, since they typically ask for public data. Shirluban 141.101.88.106 14:39, 5 April 2017 (UTC)
Use prime numbers in your password: this would only limit the number of possible passwords for a hacker to check.
Use special characters like & and % : this advice is thoroughly handled in https://xkcd.com/936/ Changing characters into a special one does adds just very little to the search space. However, a video from Computerphile suggests inserting a random character somewhere in the password which might actually be rather helpful
162.158.111.211 14:53, 5 April 2017 (UTC)
Maybe you really should use a secure font Font related bug 162.158.79.161 15:13, 5 April 2017 (UTC)
Should the blue check mark tip be noted as only being useful on Twitter? Usually, the advice doesn't apply to emails, which are significantly more likely to ask for your less-secret account details, but also significantly less likely to have a blue check mark. 162.158.2.10 15:15, 5 April 2017 (UTC)
