Intended usage case has the server as a physically-secured box in home or office, not somebody else's cloud.
-
-
Browser exploits are mitigated by having a sufficiently powerful cpu on the server to be running something Qubes-like.
-
Virtualization works fine on existing mobile hardware. Implementing that is not a hardware issue.
-
Virtualization also isn't the only good approach to tight sandboxing, and is used for compatibility not security properties.
End of conversation
New conversation -
-
-
No it isn't. The device has access to the data on the server. The server clearly exists too.
-
No it doesn't. Input side of session is closed as soon as screen locks.
-
So the user can't receive a notification that they've received a call or a message? And they type server addr each time?
-
One-way channel for ring/vibrate commands is kept open. To regain full access, have to auth.
-
So the phone is even still connected to the server. It's clear it exists. It's not deniable at all.
- End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.