On 04/28/2015 09:21 PM, Matthew Schumacher wrote:
> On 04/28/2015 05:13 PM, Laine Stump wrote:
>> Bah. Your debug symbols aren't enough to give a full stack trace - what
>> I was really looking for was those things marked as ??.
>>
>> However, your debug output shows several things leading up tothe
Hi. Is is possible to use GPG on the host instead of NSS with virtual
smartcards? Please document how or add support for it.
Can a virtual smartcard make the host less secure? If there are bugs in
GPG/NSS backend on the host can they be abused by untrusted code in the
vm?
___
Hi. Is is possible to use GPG on the host instead of NSS with virtual
smartcards? Please document how or add support for it.
Can a virtual smartcard make the host less secure? If there are bugs in
GPG/NSS backend on the host can they be abused by untrusted code in the
vm?
___
On 04/28/2015 05:13 PM, Laine Stump wrote:
> Bah. Your debug symbols aren't enough to give a full stack trace - what
> I was really looking for was those things marked as ??.
>
> However, your debug output shows several things leading up tothe
> qemuProcessStop that might have been the reason for
> On Friday 10 April 2015 13:07:38 Matthew Schumacher wrote:
>> Hello List,
>>
>> Seems like blockcopy --wait doesn't work work qemu-2.2.x.
>>
>> I found someone else having the same problem, but it never went anywhere:
>>
>> https://www.redhat.com/archives/libvirt-users/2015-January/msg00045.html
On 04/28/2015 06:03 PM, Matthew Schumacher wrote:
>
> On 04/22/2015 08:19 AM, Laine Stump wrote:
>> If you're compiling yourself, then you should be all set to run under
>> gdb. libvirt-debuginfo is just a separate subpackage that contains all
>> the symbol and line number info from the build so th
On 04/22/2015 08:19 AM, Laine Stump wrote:
> If you're compiling yourself, then you should be all set to run under
> gdb. libvirt-debuginfo is just a separate subpackage that contains all
> the symbol and line number info from the build so that backtraces in
> gdb make sense. Try attaching gdb to
Dear libvirt team,
we a currently in a pci-dss certification process and our security
scanner found weak ciphers in the vlc_tls service on our centos6 box:
When I scan using sslscan I can see that sslv3 and rc4 is accepted:
inf0rmix@tardis:~$ sslscan myhost:16514 | grep Accepted
Accepted SS
(I'm not sure what the settings/commands are in the email application
you use ("foxmail" apparently), but please configure it / use it such
that you *reply* to messages rather than adding text onto a *forwarded*
copy of the message you mean to reply to - in a "reply", everything in
the original mes
From: Laine Stump
Date: 2015-04-27 21:41
To: libvirt-users
CC: Daniel P. Berrange; w...@foxmail.com
Subject: Re: [libvirt-users] How does the libvirt deal with the vnet mac address
On 04/27/2015 04:59 AM, Daniel P. Berrange wrote:
> On Sun, Apr 26, 2015 at 10:51:34AM +0800, w...@foxmail.com wrote
From: Daniel P. Berrange
Date: 2015-04-27 16:59
To: w...@foxmail.com
CC: libvirt-users
Subject: Re: [libvirt-users] How does the libvirt deal with the vnet mac address
On Sun, Apr 26, 2015 at 10:51:34AM +0800, w...@foxmail.com wrote:
> How does the libvirt deal with the vnet mac address?
>
> Gre
11 matches
Mail list logo
