Re: [qubes-users] Wine/PlayOnLinux Best Practices

2017-01-31 Thread john.david.r.smith
On 31/01/17 22:24, mojosam wrote: it does protect you from user errors. e.g.: you have some malicious pdf in a vm. if you have noting to open the pdf, you can't accidentally open it and corrupt your vm. Isn't that the concept behind "attack surface"? If the code is there, something malicious

Re: [qubes-users] Wine/PlayOnLinux Best Practices

2017-01-31 Thread mojosam
> it does protect you from user errors. e.g.: > you have some malicious pdf in a vm. > if you have noting to open the pdf, you can't accidentally open it and > corrupt your vm. Isn't that the concept behind "attack surface"? If the code is there, something malicious might have the ability to ca

Re: [qubes-users] Wine/PlayOnLinux Best Practices

2017-01-31 Thread john.david.r.smith
Since this is in my regular Fedora 24 template, won't this codebase be included in every app VM I run, whether I'm running PlayOnLinux in that app VM or not? yes Presumably none of that code would be running, so there should be no problem (at least i can't see any problems) but it would

[qubes-users] Wine/PlayOnLinux Best Practices

2017-01-30 Thread mojosam
I am in the process of installing PlayOnLinux into my Fedora 24 template. Currently, my only use for it is the Kindle app. I suspect I'll find further need for it in the future. My original plan was to just use the Kindle app in one of my existing app VMs. In the future, I might want some ot