-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Jun 15, 2017 at 09:53:11PM +0200, Zrubi wrote:
> On 06/15/2017 06:34 PM, Reg Tiangha wrote:
>
> > Curious: For those apps that exhibit that behavior, are they
> > running on Debian 9 or Fedora 25 templates?
>
> Nope.
> Fedora 24 mainly,
On 06/18/2017 05:51 PM, Rusty Bird wrote:
> Rusty Bird:
>> Patrik Hagara:
>>> Single-use key file code committed
>
>> Whee, I finally get it... Seeing how it all fits together, it looks
>> really cool!
>
>> What do you think about making replay protection a self-contained
>> secret? If we'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Patrik Hagara:
> The initramfs would, upon next boot, read both the sealed LUKS key file
> (unsealing it, along with stored counter value) and the publicly
> readable counter value from TPM -- and, assuming the values match,
> continue booting. An
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Marek Marczykowski-Górecki:
> I think PNG support is a nice half-measure against shoulder surfing -
> details on the image are harder to copy/remember (or even photograph
> with a small camera), than some text.
You're right, it is better. I hadn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, Jun 16, 2017 at 01:47:25PM +, Rusty Bird wrote:
> Hi everyone,
>
> What do you think about getting rid [1] of .png image secret support in
> the next major version of Anti Evil Maid? This would offset some of the
> increase in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Jun 18, 2017 at 04:17:02PM +0100, Matt McCutchen wrote:
> I have a Bluetooth headset that I'd like to use with multiple VMs.
> Assigning the Bluetooth controller to each VM (at either the PCI or USB
> level) when I want to use that VM isn't
> If I copy the same pairing key to all of the VMs, then an
> attacker within Bluetooth range who had access to one VM could
> intercept the audio connection when I'm using the headset with a
> different VM.
If an attacker is within Bluetooth range he can probably use a
microphone and listen to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Jun 15, 2017 at 05:39:08PM -0600, Reg Tiangha wrote:
> On 06/15/2017 05:12 PM, pixel fairy wrote:
> > On Thursday, June 15, 2017 at 11:50:31 AM UTC-7, Reg Tiangha wrote:
> >
> >
> > We're still stuck with FC23 in dom0 though, although
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Jun 18, 2017 at 02:02:22AM -0700, stevenwinderl...@gmail.com wrote:
> https://www.debian.org/releases/stretch/releasenotes.en.html
>
> Will you update Debian Templates in QubesOS 3.2 to Debian 9 and also have
> this available in QubesOS 4?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Rusty Bird:
> Patrik Hagara:
> > Single-use key file code committed
>
> Whee, I finally get it... Seeing how it all fits together, it looks
> really cool!
>
> What do you think about making replay protection a self-contained
> secret? If we'd
I have a Bluetooth headset that I'd like to use with multiple VMs.
Assigning the Bluetooth controller to each VM (at either the PCI or USB
level) when I want to use that VM isn't an ideal solution because each
VM needs a pairing key to secure the Bluetooth connection to the
headset. If I copy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Patrik Hagara:
> Single-use key file code committed
Whee, I finally get it... Seeing how it all fits together, it looks
really cool!
What do you think about making replay protection a self-contained
secret? If we'd change it from a counter (shared
https://www.debian.org/releases/stretch/releasenotes.en.html
Will you update Debian Templates in QubesOS 3.2 to Debian 9 and also have
this available in QubesOS 4?
Also is there any ETA when you will support full GPU support and
passthrough for VMs in Qubes? This could especially be handy for
13 matches
Mail list logo
