This is an awesome idea. What I'd really like to know, however, is if any of the existing loan options will accept this as schooling in order to loan a student money for living expenses. Some students already have a family, and thus they cannot crash at a flophouse.
Constraint programming is an interesting model to discuss here. I've been looking into machine-generated constraints, and there's a lot of potential for transparency when you get into constraint-producing functions that also produce labels, and then go further up the abstraction ladder from there. Structured right, you can produce dynamic labeled matchers, especially if you build a UI tool for marking particular hateful elements of hate speech.
This is a fascinating project. The hardest part of writing crypto software will always be avoiding the little mistakes, and every time we can bottle the understanding needed to detect some of them, we free cognitive labor for finding others. This is a necessary part of the future of crypto development. I tip my hat to the Wycheproof team!
The device could be something like a modified USB condom, but with more processing power. It would have to have all drivers locked unless a sensor verified that nothing was plugged into the suspicious end, and use a fundamentally limited set of drivers. On connection, it looks for any filesystems on the suspicious device, mounts them, and offers them up by proxy as filesystems to the host machine. Nice idea.
On the one hand, my knee-jerk reaction to this involves a meaningful amount of Windows-hate. In short: there is a tight limit to the amount of trust I can give to any build on a platform that I can't build.
On the other hand, reproducible builds are /important/. The better we can trust our tools and verify that they're exactly what we think they are, the less we need to worry about the security of our tools, and the more we can get on with /using them/.
In the end, despite enabling the continued use of a deeply proprietary and anti-freedom platform, this is a good thing.