5 ms·
I understand where you're coming from. On the other hand, there's a lesson to learn from the teacher's point of view as well. We always need to take a step back
by dfxm12 1y ago
I understand where you're coming from. On the other hand, there's a lesson to learn from the teacher's point of view as well. We always need to take a step back to understand the weakest links in security. A small piece of electrical tape or maybe even a strategically placed VHS cover could solve the issue. Hopefully, this hadn't happened again.
It also comes to: should a teacher "trust" their students not to be intentionally disruptive in interesting ways? Now I wonder if I should similarly trust my users (who are co-workers who are at least getting paid to not cause disruptions)...
- i80and 1y agoI'd be willing to bet that's the only time the teacher had to deal with that specific skulduggery. Is it actually worth it for a teacher to spend time red-teaming basic lesson equipment? I really think not unless the teacher has reason to believe her students are particularly mischievous.
- dfxm12 1y agoA punishment may (or may not) be deterrent enough for the people who saw it. However, when you get a new class/userbase regularly or when new technology becomes available (including devices that can control your hardware remotely), an ounce of prevention is worth a pound of cure. Perhaps using your watch as intended doesn't seem particularly mischievous in the moment. In this way, legitimate users/sys admins/script kiddies get into trouble because a sys admin didn't have reason to believe their users would be "particularly mischievous".
- brassattax 1y agoExactly. I did the same with my wrist remote in class. After the second time the TV turned off, without saying anything the teacher went to his desk, picked up a notecard, and propped it up over the remote sensor.