On Mon, Mar 19, 2018 at 12:12:13AM +0100, Marek Marczykowski-Górecki wrote:
> > > I wasn't aware of the NIST Randomness Beacon. Very interesting. Thanks
> > > for bringing it to my attention. As far as I can tell, this looks like a
> > > very good source for the Proof of Freshness. Would you like t
On Saturday, 17 March 2018 23:40:11 UTC+8, Marek Marczykowski-Górecki wrote:
> This should be at least partially fixed by
> https://github.com/QubesOS/qubes-desktop-linux-manager/pull/18.
> The issue happens when VM change state while widget's menu is visible.
> The above does not fix that comple
On Sunday, March 18, 2018 at 7:47:22 PM UTC-4, Andrew Clausen wrote:
> Hi Marek,
>
>
>
>
> On 18 March 2018 at 23:12, Marek Marczykowski-Górecki
> wrote:
>
> To be honest, I don't think we need more proofs of freshness there. We
>
> already have various news headlines (chosen from different
Hi Marek,
On 18 March 2018 at 23:12, Marek Marczykowski-Górecki <
marma...@invisiblethingslab.com> wrote:
> To be honest, I don't think we need more proofs of freshness there. We
> already have various news headlines (chosen from different countries),
> bitcoin blockchain and now NIST Randomness
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Mar 18, 2018 at 04:00:22PM -0700, Innovative Inventor wrote:
> On Sunday, March 18, 2018 at 12:31:13 AM UTC-4, Andrew David Wong wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > On 2018-03-17 16:34, Innovative Inventor
On Sunday, March 18, 2018 at 12:31:13 AM UTC-4, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2018-03-17 16:34, Innovative Inventor wrote:
> > On Friday, March 9, 2018 at 3:19:47 PM UTC-5, Innovative Inventor wrote:
> >> I was looking at the canaries, and I li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Mar 18, 2018 at 07:17:05PM +, axtpq4+b7cb093yafps8 via qubes-devel
wrote:
> Hi,
> there are some issues regarding the war the qubes-manager and the xl command
> line handles execution of arguments.
>
>
> xl destroy ID fails and leaves
Hi,
there are some issues regarding the war the qubes-manager and the xl command
line handles execution of arguments.
xl destroy ID fails and leaves the terminated machine hanging in an
intermediate state that prevents restart of the vm (with or without sudo).
Qubes needs to be re-booted in or