TPM isn't all that reliable. You will have people upgrading their pc, or windows update updating their bios, or any number of other reasons reset their tpm keys, and currently nothing will happen. In effect people would see Signal completely break and loose all their data, often seemingly for no reason.
Talking to windows or through it to the TPM also seems sketchy.
In the current state of Windows, the sensible choice is to leave hardware-based encryption to the OS in the form of disk encryption, unfortunate as it is. The great number of people who loose data or have to recover their backup disk encryption key from their Microsoft account tells how easily that system is disturbed (And that Microsoft has the decryption keys for your encrypted date).
The problem is "indistinguishable" levers.
In the strict sense, if there was a lever you could see first, they would not be indistinguishable. They should not be distinguishable by any property including location
SSB is still around, but also not what I was looking for. I just wanted a frameless window (and no other pwa functionality).
Fullscreen I disabled using my window manager. Under Linux you can commonly use alt+F3 to bring up the "right click on titlebar" menu, then disable fullscreen there. Generally ever window manager can disable fullscreen for windows, in a more or less accessible way (cough ms windows dll calls cough).
As mentioned below, This is recovery. I could ban kiosk mode to a separate profile, but unless you invent a time machine this won't undo having opened kiosk mode in an in-use profile.
Yes, this is more of a recovery operation. Whatever the fix may be, modifying the browser itself to open a window without decorations would be easier.
There are some usecases in which you really don't want to restart your browser.
The easiest way to update your kernel is to restart your pc, yet there is a market for live-patch kernels.
If someone accidentally infects their instance with kiosk, it may occasionally be preferable for them to follow a complex procedure to recover the instance, rather than doing the "simple" thing of restarting it.
Restarting may solve many problems, but there is a more difficult but less invasive solution almost every time.
Much like reinstalling may solve even more problems, but you can see that doing a reinstallation is not usually the right course of action.
Kiosk mode doesn't just force fullscreen, it disables right click, the tab and title bar, ...
Basically the browser is close to unusable until kiosk mode is ended, which I currently only know how to do via restarting Firefox.
And F11 is also disabled by kiosk mode. Interestingly, on the windows that were started before kiosk mode, it puts them into proper kiosk mode (after which F11 stops working of course).
I guess adb backup was before my time. I did use adb to transfer my apps when I last restored a twrp backup. In perhaps a similar manner to what that did, going by the name. But I did use adb root for that.
Otherwise, I use it to set a lot of otherwise inaccessible settings, like making the back gesture a lot thinner than intended because my touchscreen can handle it, or forcing 120Hz everywhere. I can also set my dpi there without anoying apps.
And ofc I use it to uninstall system apps I don't need.
After initial setup I do all of that in a root bash session in termux admittedly, but if I hadn't rooted my device I would still want to do most of that using an adb shell, as most of it doesn't require root (besides maybe the restoring backups part).
I also use shell environment to semi-automatically transfer media files for certain processes, though I'll probably move that over to syncrhing at some point.
The main remaining advantage is the ability to automate things on my phone from my pc, I don't see a lot of those as replacable unless my rom installs kde connect as a system app and they add an immense amount of functionality
redjard @ Redjard @lemmy.dbzer0.com Posts 2Comments 449Joined 2 yr. ago
TPM isn't all that reliable. You will have people upgrading their pc, or windows update updating their bios, or any number of other reasons reset their tpm keys, and currently nothing will happen. In effect people would see Signal completely break and loose all their data, often seemingly for no reason.
Talking to windows or through it to the TPM also seems sketchy.
In the current state of Windows, the sensible choice is to leave hardware-based encryption to the OS in the form of disk encryption, unfortunate as it is. The great number of people who loose data or have to recover their backup disk encryption key from their Microsoft account tells how easily that system is disturbed (And that Microsoft has the decryption keys for your encrypted date).