OSDev.org

That sounds like Windows' BitLocker and encrypted filesystems. And it has a lot of vulnerabilities, such as inserting malicous code in the decryptor (which can't be encrypted) or pulling the decryption key from memory during reboot. In any case its already been implemented on multiple operating systems.

This should be covered by the open source release of a boot loader patch I will make once completed.

But in some cases, like if you're on the go and you want to access your desktop at home, this won't be enough. It also means that programmers have to implement remote access in their application themselves if they want it to work. This is the exact opposite of your idea of spending less time coding repetivive things. Its much easier to just allow encrypted remote desktop, which will work just fine.

It seems that most of the things you are suggesting are a) already implemented or b) not implemented because they're not particulary useful.

It doesn't mean users have to implement remote access past defining the core inputs and outputs of the GUI and letting the OS patches handle the networking interface, past that someone with the same OS and application on a remote computer could use the same software in a remote fashion (using a console window as a basis for this example, theres no need to forward an image of a console window if you have the same program on the other end and let the two operating systems forward the in/out/error of the console to the GUI - this exists to a marginal degree in X when you consider remote sessions).

I just stumbled upon a method for doing exactly this on an X system. You can run ssh with X forwarding enabled, and run programs normally over the ssh connection.

JohnnyTheDon wrote:I just stumbled upon a method for doing exactly this on an X system. You can run ssh with X forwarding enabled, and run programs normally over the ssh connection.

I do this all the time - it's a little slow over the internet though.