Hacker News new | past | comments | ask | show | jobs | submit login

There's actually many solutions to this.

>You can use certificate based authentication instead of password based. Certificate based authentication COMPLETELY prevents this attack because the student's computer never sees the private key which actually authenticates the teacher to bypass

>You can use time based one-time passwords/HMAC instead of using certificates, with a teacher pulling up an app

>You can have the computer have its password managed by a centralised store which has the ability to rotate said password. When the teacher needs to unlock a computer, they request that computers password from the centralised store, and after it's used, the password is then rotated.

>What I would recommend the most, is just giving each teacher their own credentials and sending the teacher an alert when their credentials were used.

You could easily lock this down, but I honestly don't think it's a good idea. I think using weak security measures actually has a merit, as it grants the teacher some degree of flexibility in how to deal with things, and it grants the kids a greater degree of freedom and education in both what weak security looks like and how cracking security just because it's weak might not be the best idea.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: