Hi Daniel, Thanks for the quick response.
I understand that approach to add some limitations to the product in order to retain strict confinement, but we do want Proaction to be compatible with the directory structure and code layout that a user already has on their workstation. If the code is not under $HOME (or removable media), this confinement would require that the user either finds a different way to install Proaction or change where they store code on their workstation.
I understand the
--classic flag allows for much more access than we want here, but there are use cases where this is desirable. I know that some people (myself included) mount an external disk (not removable, but just a different block device) to a directory such as /go and use this as my $GOPATH. With the strict confinement, I’d have to change my directory structure in order to use Proaction, which would be undesirable.
Its only a request to get access to more directories, outside of $HOME and removable media, but absent a way to do this in strict confinement, we’d still like to request classic confinement to meet this use case.