Hi all,
This is the first of many progress reports I will be writing up for my
time as a Qubes GSoC student.
For included screenshots, read it here:
https://blog.amorgan.xyz/gsoc-2017-weekly-progress-report-1.html
Otherwise, the text-only version is reproduced below.
---
The current goal for t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Qubes community,
Thank you to everyone who has donated [1] to the Qubes OS Project! As
many of you know, there are two ways to donate: through our Bitcoin
fund [2] and through Open Collective [3]. Some of you may have noticed
that we haven't sp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Jun 05, 2017 at 04:37:27PM -0700, Andrew Morgan wrote:
> On 06/05/2017 04:19 PM, Marek Marczykowski-Górecki wrote:
> > On Mon, Jun 05, 2017 at 03:40:09PM -0700, Andrew Morgan wrote:
> >> Is that new Operation Execution dialog intended to repl
On 06/05/2017 04:19 PM, Marek Marczykowski-Górecki wrote:
> On Mon, Jun 05, 2017 at 03:40:09PM -0700, Andrew Morgan wrote:
>> Is that new Operation Execution dialog intended to replace the existing
>> qvm-mru dialog with regards to AppVM<->AppVM file transfer?
>
> Yes.
So I suppose I should use Z
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Jun 05, 2017 at 03:40:09PM -0700, Andrew Morgan wrote:
> Is that new Operation Execution dialog intended to replace the existing
> qvm-mru dialog with regards to AppVM<->AppVM file transfer?
Yes.
> If so, then
> is there anything I should d
On 06/05/2017 03:30 PM, Marek Marczykowski-Górecki wrote:
> On Mon, Jun 05, 2017 at 02:57:10PM -0700, Andrew Morgan wrote:
>> Hey all,
>
>> Quick question that's directed to my mentor Marek, though anyone can
>> answer. I'm aware of the utility qvm-mru-entry that's currently used to
>> create a si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Jun 05, 2017 at 02:57:10PM -0700, Andrew Morgan wrote:
> Hey all,
>
> Quick question that's directed to my mentor Marek, though anyone can
> answer. I'm aware of the utility qvm-mru-entry that's currently used to
> create a simple GUI dialog
On Monday, June 5, 2017 at 9:54:03 PM UTC+2, Peter Todd wrote:
>
> On Mon, Jun 05, 2017 at 11:15:33AM -0700, Axel wrote:
> > > Bitcoin block hashes are a chain, so it doesn't make any sense to
> include
> > > more
> > > than one, unless you're worried about reorgs.
> > >
> >
> > Agree. reo
Hey all,
Quick question that's directed to my mentor Marek, though anyone can
answer. I'm aware of the utility qvm-mru-entry that's currently used to
create a simple GUI dialog for the qvm-move/copy scripts etc. that is
called from the context menus in Nautilus and Dolphin. However upon
checking t
On Monday, June 5, 2017 at 10:52:25 PM UTC+2, Chris Laprise wrote:
>
> Can OpenTimestamps be easily reconfigured to use a blockchain system
> other than Bitcoin?
>
> Chris
>
>From OpenTimestamps.org: "OpenTimestamps aims to be a standard format for
blockchain timestamping. The format is flex
Can OpenTimestamps be easily reconfigured to use a blockchain system
other than Bitcoin?
Chris
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-devel+unsub
On Mon, Jun 05, 2017 at 11:15:33AM -0700, Axel wrote:
> > Bitcoin block hashes are a chain, so it doesn't make any sense to include
> > more
> > than one, unless you're worried about reorgs.
> >
>
> Agree. reorgs are the only reason to include more than one, but 10 seems
> like overkill. Reorg
On Monday, June 5, 2017 at 1:34:01 PM UTC+2, Peter Todd wrote:
>
> On Sun, Jun 04, 2017 at 05:29:46AM -0700, 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
On Monday, June 5, 2017 at 1:36:07 PM UTC+2, Peter Todd wrote:
>
> On Sun, Jun 04, 2017 at 04:45:32PM -0500, Andrew David Wong wrote:
> > My next question was going to be whether you're aware of Peter Todd's
> > OpenTimestamps project, which Jean-Philippe mentioned. Also see:
> >
> > https://
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2017-06-05 08:42, Andrew David Wong wrote:
> Dear Qubes community,
>
> We have just published Qubes Canary #12. The text of this canary is
> reproduced below. This canary and its accompanying signatures will always be
> available in the Qubes Sec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Qubes community,
We have just published Qubes Canary #12. The text of this canary is
reproduced below. This canary and its accompanying signatures will always be
available in the Qubes Security Pack (qubes-secpack).
View Canary #12 in the qube
On Sun, Jun 04, 2017 at 04:45:32PM -0500, Andrew David Wong wrote:
> My next question was going to be whether you're aware of Peter Todd's
> OpenTimestamps project, which Jean-Philippe mentioned. Also see:
>
> https://petertodd.org/2016/opentimestamps-announcement
> https://github.com/opentimestam
On Sun, Jun 04, 2017 at 05:29:46AM -0700, 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 the
> opposite: make the bl
18 matches
Mail list logo
