Re: [qubes-devel] Future-proofing qubes-secpack

2017-06-04 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-06-04 16:45, Axel wrote: > Excellent, and it's even free of charge. Following links from > opentimestamps.org, I found https://stamp.io/ which claims to also > be free of charge, and using both Bitcoin and Ethereum > blockchains. > Looks

Re: [qubes-devel] Future-proofing qubes-secpack

2017-06-04 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-06-04 07:29, Axel wrote: > I did not see that pull request. Note however that the pull request > makes qubes-secpack depend on the blockchain in order to prove > information creation *after* a certain point in time, while my > suggestion was

Re: [qubes-devel] Future-proofing qubes-secpack

2017-06-04 Thread Axel
Excellent, and it's even free of charge. Following links from opentimestamps.org, I found https://stamp.io/ which claims to also be free of charge, and using both Bitcoin and Ethereum blockchains. On Sunday, June 4, 2017 at 7:04:55 PM UTC+2, Jean-Philippe Ouellet wrote: > > On Sat, Jun 3, 2017 a

Re: [qubes-devel] Distinct inter/intra vm clipboard shortcuts

2017-06-04 Thread Jean-Philippe Ouellet
On Sat, Jun 3, 2017 at 3:10 PM, Vít Šesták wrote: > There are defined keyboard scancodes for copy&paste: > > 0x7BKeyboard Cut > 0x7CKeyboard Copy > 0x7DKeyboard Paste > > Source: http://www.freebsddiary.org/APC/usb_hid_usages.php > i am not sure how much they ar

Re: [qubes-devel] Future-proofing qubes-secpack

2017-06-04 Thread Jean-Philippe Ouellet
On Sat, Jun 3, 2017 at 11:24 AM, Axel wrote: > As Joanna has already noted, qubes-secpack is not advertised as solving all > problems related to distribution security, but "the best we can do" > currently. > > I'd like to suggest a practical improvement of qubes-secpack that I believe > can protec

Re: [qubes-devel] Future-proofing qubes-secpack

2017-06-04 Thread Axel
I did not see that pull request. Note however that the pull request makes qubes-secpack depend on the blockchain in order to prove information creation *after* a certain point in time, while my suggestion was the opposite: make the blockchain depend on qubes-secpack in order to prove informatio