In this case keys are per-sensor and revokable. So surely if someone spends a lot of money and extracts a sensor key it can only get minimal use before revocation?
While it's nice to know that I can buy a $100 replacement keyboard (I'm about 6 months out of warranty) it's also frustrating that Framework wouldn't own up to what is obviously a manufacturing failure.
I had a similar idea for take-home tests for software interviews. Run a bash script to commit all changes in a repo every 5 seconds. The candidate then submits a tarball of the git repo.
#!/usr/bin/env bash
while true; do
git add -A
if ! git diff --cached --quiet; then
git commit -m "$(date --iso-8601=seconds)"
fi
sleep 5
done
I want something like this in a keyboard: a completely hidden drive that the OS cannot see until I type in a certain string of characters (password) to activate it with a separate string of characters to deactivate it.
That is actually what my company built. The primary purpose was for encrypted messaging, but it also acted as secrets store and password manager. The great thing about it being built into the keyboard is there is no chance for a rooted host to intercept passwords/messages etc.
reply