On Tuesday, 23 January 2018 14:44:21 UTC, Ivan Mitev wrote: > On 01/23/18 16:05, 'Tom Zander' via qubes-devel wrote: > > On Tuesday, 23 January 2018 05:56:05 CET Chris Laprise wrote: > >> But at some point the hardware will make or break us, and the > >> hardware we got now is Wintel; even Linux is an afterthought when you're > >> not looking at server components. > > > > I'm not sure if you guys caught the subtle side-effects of the 'Qubes-Air' > > proposal. It didn't hit me until I slept on it. > > yep - the same thing occurred to me this morning after yesterday's post, > when I thought "hmm, they ended up drinking the cloud kool-aid like > everybody else"... > > I don't think I'll ever use Qubes in the cloud as I'm often in places > where I can't rely on a good internet connection but being able to > locally and securely use different hardware platforms for different > workloads/usage opens a whole new world of use cases. (I liked the idea > of a dumb microcontroller for the vault VM).
You however may want to use cloud services. I.e. a great one like Office 265 and have a VM on Azure to host the browser that connect to it... with the display streamed back home securely (and I agree with your question just below). > > One thing I'm not sure about though is how the "networked" qubes rpc > will be secured (attack surface of the tcp implementation and/or higher > protocols encapsulating rpc, ...). > > Ivan -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/f1b70544-bde7-4bb9-b348-0884c9fd72e7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
