3 ms·
Secure paths are a big issue. Windows used to have a "secure attention sequence", CNTL-ALT-DEL, which you had to push when you really wanted to talk to the sec
by Animats 4y ago
Secure paths are a big issue.
Windows used to have a "secure attention sequence", CNTL-ALT-DEL, which you had to push when you really wanted to talk to the security functions of the operating system. That stopped being mandatory in Windows 10, due to "customer confusion", although some enterprise configurations turn it back on.
The concept comes from some DoD security projects from around 1980. Microsoft picked it up when Windows NT was being developed. Some DoD systems have also used a brightly colored screen border to indicate the degree of classification of the content. But that's too intrusive for consumer use.
There are so many layers now that it's hard to provide a secure path that can't be compromised.
- dfox 4y agoSAK is controlled by group policy since Windows 2000 and is disabled by default on client SKUs that are not domain member. On the other hand all current iOS devices have some hardware level SAK-like gesture that directly confirms the user intent to the secure enclave. The overall UX design is such that it is not especially noticeable unless you know that there is such a thing.