-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel P. Berrange wrote:
> On Fri, Jan 30, 2009 at 09:06:38AM -0500, Daniel J Walsh wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Daniel P. Berrange wrote:
>>> I don't particularly like the idea of running another program to check
>
On Fri, Jan 30, 2009 at 09:06:38AM -0500, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Daniel P. Berrange wrote:
> >
> > I don't particularly like the idea of running another program to check
> > this because SELinux context isn't the only thing which will potential
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel P. Berrange wrote:
> On Fri, Jan 30, 2009 at 07:38:40AM -0500, Daniel J Walsh wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Met with Cole this morning and we talked about how SELinux can cause
>> people headaches when installi
On Fri, Jan 30, 2009 at 07:38:40AM -0500, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Met with Cole this morning and we talked about how SELinux can cause
> people headaches when installing virtual images from random locations.
>
> User downloads a iso image to his
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Met with Cole this morning and we talked about how SELinux can cause
people headaches when installing virtual images from random locations.
User downloads a iso image to his home directory and then uses
virt-manager to install it. Problem is when the
