Timeline for Selecting a secure PIN for building access
Current License: CC BY-SA 4.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 1, 2019 at 13:06 | vote | accept | Les | ||
| Apr 30, 2019 at 22:09 | answer | added | John Wu | timeline score: 5 | |
| Apr 30, 2019 at 15:10 | answer | added | Dmitry Grigoryev | timeline score: 4 | |
| Apr 30, 2019 at 12:19 | comment | added | Voo | @aCVn Since we're already nitpicking: No please don't remember that "5 rounds up" because that simplistic approach leads to a significant bias of the rounded numbers. There are many other rounding schemes than the one we learn in grade school, for good reason. | |
| Apr 30, 2019 at 11:21 | comment | added | spender | The medium of distributing the PIN is also a highly important consideration here. | |
| Apr 30, 2019 at 10:16 | comment | added | schroeder♦ | @Les lists of pin patterns will make for a very poor answer. Physical patterns and repeated numbers are the most common. My answer below of using a random generator instead of letting people choose their own PINs is the better way to go else you play whack-a-mole | |
| Apr 30, 2019 at 7:21 | comment | added | BlueCacti | @MartinBonner May I ask why they would've/should've had issues with the repeated digit? I can see no reason as to why this would weaken the PIN. Limiting yourself to non-repeating digits decrease the entropy of the PIN (10*10*10*10 vs 10*9*8*7). | |
| Apr 29, 2019 at 18:10 | answer | added | Kevin Mirsky | timeline score: 16 | |
| Apr 29, 2019 at 16:51 | comment | added | Les | @MartinBonner Yes! this one kind of pattern I'm looking for. Something about the company that might suggest a (bad) PIN. | |
| Apr 29, 2019 at 16:49 | history | edited | Les | CC BY-SA 4.0 |
added 192 characters in body
|
| Apr 29, 2019 at 16:48 | comment | added | Martin Bonner supports Monica | Aside: The entry code for one of my employers was 3141. The security auditors were a little unhappy at the repeated digit but let it slide. They completely missed that the company name was "Pi Research"! | |
| Apr 29, 2019 at 15:00 | history | tweeted | twitter.com/StackSecurity/status/1122878383170433024 | ||
| Apr 29, 2019 at 13:33 | history | became hot network question | |||
| Apr 29, 2019 at 13:26 | answer | added | Matthew | timeline score: 12 | |
| Apr 29, 2019 at 13:23 | comment | added | Les | You list several risks. The primary risk we would like to reduce is vandalism and theft. BTW, thanks for adding the physical-access tag. | |
| Apr 29, 2019 at 13:20 | comment | added | schroeder♦ | We can make a lot of guesses about the risks that a church might face, but can you describe what you think the risks would be if someone got access to a PIN? Vandalism? Hate crime? Access to church records? Access to valuables? What is in the offices that are behind, likely, hollow core doors? Is it staffed or patrolled 24/7? | |
| Apr 29, 2019 at 13:17 | history | edited | Les | CC BY-SA 4.0 |
added 207 characters in body
|
| Apr 29, 2019 at 13:16 | answer | added | schroeder♦ | timeline score: 27 | |
| Apr 29, 2019 at 13:13 | history | edited | schroeder♦ | CC BY-SA 4.0 |
deleted 6 characters in body; edited tags
|
| Apr 29, 2019 at 13:12 | history | edited | Les | CC BY-SA 4.0 |
added 165 characters in body
|
| Apr 29, 2019 at 13:04 | history | asked | Les | CC BY-SA 4.0 |