Opening the source of Qubes Windows Tools
121 views
Skip to first unread message
Rafał Wojdyła
Jan 27, 2016, 10:13:00 AM1/27/16
to qubes...@googlegroups.com
Hi all,
I'm happy to announce that today we are opening the full source of Qubes
Windows Tools!
Detailed instructions for building are in the qubes-builder-windows
repo, which also includes an example builder config to use.
Following repositories are needed to build the installer:
* vmm-xen-windows-pvdrivers
* core-vchan-xen
* windows-utils
* core-qubesdb
* core-agent-windows
* gui-common
* gui-agent-windows
* installer-qubes-os-windows-tools
And here you can find the official blog post:
https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
--
Rafał Wojdyła
Qubes Tools for Windows developer
https://www.qubes-os.org/
I'm happy to announce that today we are opening the full source of Qubes
Windows Tools!
Detailed instructions for building are in the qubes-builder-windows
repo, which also includes an example builder config to use.
Following repositories are needed to build the installer:
* vmm-xen-windows-pvdrivers
* core-vchan-xen
* windows-utils
* core-qubesdb
* core-agent-windows
* gui-common
* gui-agent-windows
* installer-qubes-os-windows-tools
And here you can find the official blog post:
https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
--
Rafał Wojdyła
Qubes Tools for Windows developer
https://www.qubes-os.org/
Rafał Wojdyła
Jan 27, 2016, 10:20:48 AM1/27/16
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[And again, this time with inline signature...]
Hi all,
I'm happy to announce that today we are opening the full source of Qubes
Windows Tools!
Detailed instructions for building are in the qubes-builder-windows
repo, which also includes an example builder config to use.
Following repositories are needed to build the installer:
* vmm-xen-windows-pvdrivers
* core-vchan-xen
* windows-utils
* core-qubesdb
* core-agent-windows
* gui-common
* gui-agent-windows
* installer-qubes-os-windows-tools
And here you can find the official blog post:
https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
- --
-----BEGIN PGP SIGNATURE-----
iQEcBAEBAgAGBQJWqOBLAAoJEIWi9rB2GrW7B+gH/1JbQSRTq1igmRS2wAawAiqY
jWhSSudLvqkyrzy4Dk8Zkns4m8zcFdoh8yqdXYiYlz1I3812GXF146J28fQg1aXY
oHlhsID5Pfdo/eDKCc5pNNEBlqM0oSQzRePFlpCzdZ1/6fUHbqpnCyM3ES6eYy+X
BtOD9ErWcx0TknGUyx6DSNLM0vxB2Jx6Cj+IIRhQ9l2Y2Bg7mXoGsRRZm7pRp6CF
ykIzbPGE7dYJRTlhc/OV76uw8K/ZoIdcmqDWgKSxRh3BOS2hy3QCAjc05jNFmU60
dDZa+nljnM97LFg8GPfaD1VUV4grFZyUaNr381f30b6k6m6YiPk/R0aBMaOCMmg=
=GHvU
-----END PGP SIGNATURE-----
Hash: SHA1
[And again, this time with inline signature...]
Hi all,
I'm happy to announce that today we are opening the full source of Qubes
Windows Tools!
Detailed instructions for building are in the qubes-builder-windows
repo, which also includes an example builder config to use.
Following repositories are needed to build the installer:
* vmm-xen-windows-pvdrivers
* core-vchan-xen
* windows-utils
* core-qubesdb
* core-agent-windows
* gui-common
* gui-agent-windows
* installer-qubes-os-windows-tools
And here you can find the official blog post:
https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
-----BEGIN PGP SIGNATURE-----
iQEcBAEBAgAGBQJWqOBLAAoJEIWi9rB2GrW7B+gH/1JbQSRTq1igmRS2wAawAiqY
jWhSSudLvqkyrzy4Dk8Zkns4m8zcFdoh8yqdXYiYlz1I3812GXF146J28fQg1aXY
oHlhsID5Pfdo/eDKCc5pNNEBlqM0oSQzRePFlpCzdZ1/6fUHbqpnCyM3ES6eYy+X
BtOD9ErWcx0TknGUyx6DSNLM0vxB2Jx6Cj+IIRhQ9l2Y2Bg7mXoGsRRZm7pRp6CF
ykIzbPGE7dYJRTlhc/OV76uw8K/ZoIdcmqDWgKSxRh3BOS2hy3QCAjc05jNFmU60
dDZa+nljnM97LFg8GPfaD1VUV4grFZyUaNr381f30b6k6m6YiPk/R0aBMaOCMmg=
=GHvU
-----END PGP SIGNATURE-----
Holger Levsen
Jan 27, 2016, 10:25:03 AM1/27/16
to qubes...@googlegroups.com
Hi,
On Mittwoch, 27. Januar 2016, Rafał Wojdyła wrote:
> I'm happy to announce that today we are opening the full source of Qubes
> Windows Tools!
cool!
> And here you can find the official blog post:
> https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
somewhat nitpickingly, under which licence are these windows tools licenced?
(Because "open source" != "free software" for some licences…)
I couldnt find that info in that blog post.
cheers,
Holger
On Mittwoch, 27. Januar 2016, Rafał Wojdyła wrote:
> I'm happy to announce that today we are opening the full source of Qubes
> Windows Tools!
> And here you can find the official blog post:
> https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
(Because "open source" != "free software" for some licences…)
I couldnt find that info in that blog post.
cheers,
Holger
Rafał Wojdyła
Jan 27, 2016, 10:29:18 AM1/27/16
to Holger Levsen, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hash: SHA1
be in the post - I'll add that.
- --
Rafał Wojdyła
Qubes Tools for Windows developer
https://www.qubes-os.org/
-----BEGIN PGP SIGNATURE-----
AM1YLJAIGKhEDMBtYHWE6mup+CoVJpL71Tumgafsch0/2Nz/plGm3go2FVoFbQuR
yuC9TeGkWGFxVhuCoo9gX+UxaAKwg4W1NNPVulm5dAQVZIJnnNgavhum0odaPXUp
3Ubey3mDdPuD2+pxMcCryzx2Ew+yi6msUH0koOUHciUpc33sG5zTWvgax/IroLgM
AdJ0dyRrb27HPsyF8lldRLBicvnTWdr+Ql6A4uUDPhDQnYIAKXHjKkFH8Ikvkke5
7NlRUNxyMYUdCS7PjzSJWUfY5bc521F/H80WlP3EuLacoDfDCvID1pNHUUhoE88=
=zKCt
-----END PGP SIGNATURE-----
Andrew
Jan 27, 2016, 11:47:49 AM1/27/16
to qubes...@googlegroups.com
Rafał Wojdyła:
To my understanding, and as was alluded to in the post, this signals a
shift in business strategy. That is, that instead of having some sort
of paid "premium" Qubes distribution, the Qubes team now has a different
model for supporting itself.
Is this actually untrue? In either case, this brings up the question:
exactly how will ITL fund Qubes development? What is the long-term
plan? Is there a long-term plan?
On a related note, I know ITL has received a few recent grants. How
does the Qubes team envision such grants playing a part in the future
funding of the project? Are there guidelines for whose and what kind of
support to accept? For example, should ITL seek grant funding from
various arms of the US government?
Thanks,
Andrew
> [And again, this time with inline signature...]
>
> Hi all,
>
> I'm happy to announce that today we are opening the full source of Qubes
> Windows Tools!
>
> Detailed instructions for building are in the qubes-builder-windows
> repo, which also includes an example builder config to use.
>
> Following repositories are needed to build the installer:
>
> * vmm-xen-windows-pvdrivers
> * core-vchan-xen
> * windows-utils
> * core-qubesdb
> * core-agent-windows
> * gui-common
> * gui-agent-windows
> * installer-qubes-os-windows-tools
>
> And here you can find the official blog post:
> https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
>
>
Awesome! Great news.
>
> Hi all,
>
> I'm happy to announce that today we are opening the full source of Qubes
> Windows Tools!
>
> Detailed instructions for building are in the qubes-builder-windows
> repo, which also includes an example builder config to use.
>
> Following repositories are needed to build the installer:
>
> * vmm-xen-windows-pvdrivers
> * core-vchan-xen
> * windows-utils
> * core-qubesdb
> * core-agent-windows
> * gui-common
> * gui-agent-windows
> * installer-qubes-os-windows-tools
>
> And here you can find the official blog post:
> https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
>
>
To my understanding, and as was alluded to in the post, this signals a
shift in business strategy. That is, that instead of having some sort
of paid "premium" Qubes distribution, the Qubes team now has a different
model for supporting itself.
Is this actually untrue? In either case, this brings up the question:
exactly how will ITL fund Qubes development? What is the long-term
plan? Is there a long-term plan?
On a related note, I know ITL has received a few recent grants. How
does the Qubes team envision such grants playing a part in the future
funding of the project? Are there guidelines for whose and what kind of
support to accept? For example, should ITL seek grant funding from
various arms of the US government?
Thanks,
Andrew
Michael Carbone
Jan 31, 2016, 7:18:58 PM1/31/16
to Andrew, qubes...@googlegroups.com
Andrew:
more interested in supporting integrated Windows functionality. That
value proposition still exists I hope, incorporating the Windows Tools
(rather than treating it as a proprietary addon) is a way to enable
users to have the same trust in it as in the rest of Qubes.
There are obviously other communities besides businesses that also find
the Windows Tools valuable (really anyone trying to transition their
workflows from Windows into Qubes), so this should make using the
Windows Tools an easier decision and enable better adoption of Qubes
more generally.
> Is this actually untrue? In either case, this brings up the question:
> exactly how will ITL fund Qubes development?
> What is the long-term plan? Is there a long-term plan?
Ideally through a diverse mix of funding, both in terms of entities
providing funding and timelines of the funding.
The long-term plan is to continue to try to find ways of funding Qubes
development.
> On a related note, I know ITL has received a few recent grants. How
> does the Qubes team envision such grants playing a part in the future
> funding of the project? Are there guidelines for whose and what kind of
> support to accept? For example, should ITL seek grant funding from
> various arms of the US government?
We are always looking for more support for Qubes development. Grants (as
a style of funding) don't need to come from the US government, they can
also come from public or private foundations, non-US governments,
non-governmental organizations, etc.
Joanna discussed guidelines in the context of the OTF grant we received
last year:
http://blog.invisiblethings.org/2015/06/04/otf-funding-announcement.html
As Joanna mentioned in the blogpost, if you (or others reading) have
relevant knowledge, experience, leads, free time etc and would like to
help out in these efforts let us know.
Michael
--
Michael Carbone
Qubes OS | https://www.qubes-os.org
@QubesOS <https://www.twitter.com/QubesOS>
GPG fingerprint: 2DBE 2014 E7B0 0730 303D 7AAB 99AB 0624 6EEB F5A8
> Rafał Wojdyła:
>> [And again, this time with inline signature...]
>>
>> Hi all,
>>
>> I'm happy to announce that today we are opening the full source of Qubes
>> Windows Tools!
>>
>> Detailed instructions for building are in the qubes-builder-windows
>> repo, which also includes an example builder config to use.
>>
>> Following repositories are needed to build the installer:
>>
>> * vmm-xen-windows-pvdrivers
>> * core-vchan-xen
>> * windows-utils
>> * core-qubesdb
>> * core-agent-windows
>> * gui-common
>> * gui-agent-windows
>> * installer-qubes-os-windows-tools
>>
>> And here you can find the official blog post:
>> https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
>>
>>
>
> Awesome! Great news.
>
> To my understanding, and as was alluded to in the post, this signals a
> shift in business strategy. That is, that instead of having some sort
> of paid "premium" Qubes distribution, the Qubes team now has a different
> model for supporting itself.
The idea was not a "premium" distribution, just that businesses would be
>> [And again, this time with inline signature...]
>>
>> Hi all,
>>
>> I'm happy to announce that today we are opening the full source of Qubes
>> Windows Tools!
>>
>> Detailed instructions for building are in the qubes-builder-windows
>> repo, which also includes an example builder config to use.
>>
>> Following repositories are needed to build the installer:
>>
>> * vmm-xen-windows-pvdrivers
>> * core-vchan-xen
>> * windows-utils
>> * core-qubesdb
>> * core-agent-windows
>> * gui-common
>> * gui-agent-windows
>> * installer-qubes-os-windows-tools
>>
>> And here you can find the official blog post:
>> https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
>>
>>
>
> Awesome! Great news.
>
> To my understanding, and as was alluded to in the post, this signals a
> shift in business strategy. That is, that instead of having some sort
> of paid "premium" Qubes distribution, the Qubes team now has a different
> model for supporting itself.
more interested in supporting integrated Windows functionality. That
value proposition still exists I hope, incorporating the Windows Tools
(rather than treating it as a proprietary addon) is a way to enable
users to have the same trust in it as in the rest of Qubes.
There are obviously other communities besides businesses that also find
the Windows Tools valuable (really anyone trying to transition their
workflows from Windows into Qubes), so this should make using the
Windows Tools an easier decision and enable better adoption of Qubes
more generally.
> Is this actually untrue? In either case, this brings up the question:
> exactly how will ITL fund Qubes development?
> What is the long-term plan? Is there a long-term plan?
providing funding and timelines of the funding.
The long-term plan is to continue to try to find ways of funding Qubes
development.
> On a related note, I know ITL has received a few recent grants. How
> does the Qubes team envision such grants playing a part in the future
> funding of the project? Are there guidelines for whose and what kind of
> support to accept? For example, should ITL seek grant funding from
> various arms of the US government?
a style of funding) don't need to come from the US government, they can
also come from public or private foundations, non-US governments,
non-governmental organizations, etc.
Joanna discussed guidelines in the context of the OTF grant we received
last year:
http://blog.invisiblethings.org/2015/06/04/otf-funding-announcement.html
As Joanna mentioned in the blogpost, if you (or others reading) have
relevant knowledge, experience, leads, free time etc and would like to
help out in these efforts let us know.
Michael
--
Michael Carbone
Qubes OS | https://www.qubes-os.org
@QubesOS <https://www.twitter.com/QubesOS>
GPG fingerprint: 2DBE 2014 E7B0 0730 303D 7AAB 99AB 0624 6EEB F5A8
Robin Schneider
Feb 2, 2016, 3:38:24 PM2/2/16
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 27.01.2016 16:20, Rafał Wojdyła wrote:
> [And again, this time with inline signature...]
>
> Hi all,
>
> I'm happy to announce that today we are opening the full source of Qubes
> Windows Tools!
>
> Detailed instructions for building are in the qubes-builder-windows repo,
> which also includes an example builder config to use.
>
> Following repositories are needed to build the installer:
>
> * vmm-xen-windows-pvdrivers * core-vchan-xen * windows-utils *
> core-qubesdb * core-agent-windows * gui-common * gui-agent-windows *
> installer-qubes-os-windows-tools
>
> And here you can find the official blog post:
> https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
Thanks very much for your work and for releasing the sources +1
I just wanted to updated Wikipedia [0] when I noticed that [1] should probably
be updated before that. I guess that should be done by ITL people?
[0]: https://en.wikipedia.org/wiki/Qubes_OS
[1]: https://www.qubes-os.org/doc/license/
- --
Live long and prosper
Robin `ypid` Schneider
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWsROvAAoJEIb9mAu/GkD45M4P/AiKKC6JRnNXF7v9ba1NZTG7
0oSq5dHo8xy5Z+4BPbR9FDyoXvn3DdlnY5NO9DUvy/d3YxOghzCNNehBEltUm4V2
42xJCCfRA9NIHXNARq1wOmn548Cgez3b+0J/Lj91LtFaiMsMMdWKM1eylWDZ33c1
r6i0Gw0LsuyIB+Hl+ksUPsEftf8jTkLzTgBOUHcegO/UF5SzCcTe3fgXxyvPmhPE
Mt9DOd4jUOjw0ulV8G1HM7TgJdulPgBjGG/v6TvJUCAqB5D/mZMxDobJZXpJp15G
kgSfLqilEPsycTLk6HCh4kdb6jPsOKKbwOjYrgydWRv7OIS7YseuMWp7tGk4SxRh
beOrcDfVuvqwYbWTHJr4RtFkKRIbIPw/RenZ619Vu6qjF2KJkLrLvl87n97zBZkV
RG3tiOXvCjZXRN+oAK3YMcVul7Zd4wSjdi6CxFzoyuicMCTHp/0YOXWGTNSp5GVx
iDDg135CtxusnCjzRrdW22L7xDHBIUgwzbuurujeQnCKisu0zTxRsHVn9HCWaQcA
F9qMVHm03RP2auZwnRpA4C1sH+AJ5eMykFXkcNp06VPPnCdMbRvxq9w6Jmw+AlY2
fdrSLbPk9vURhaRe8HVjt+8eMEoYef7nw32Lm4K1nImm4Kj1dQpgRKHul1QCpAEM
qj2AoXxRrsfcH3CeGGCZ
=D+21
-----END PGP SIGNATURE-----
Hash: SHA256
On 27.01.2016 16:20, Rafał Wojdyła wrote:
> [And again, this time with inline signature...]
>
> Hi all,
>
> I'm happy to announce that today we are opening the full source of Qubes
> Windows Tools!
>
> Detailed instructions for building are in the qubes-builder-windows repo,
> which also includes an example builder config to use.
>
> Following repositories are needed to build the installer:
>
> * vmm-xen-windows-pvdrivers * core-vchan-xen * windows-utils *
> core-qubesdb * core-agent-windows * gui-common * gui-agent-windows *
> installer-qubes-os-windows-tools
>
> And here you can find the official blog post:
> https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
I just wanted to updated Wikipedia [0] when I noticed that [1] should probably
be updated before that. I guess that should be done by ITL people?
[0]: https://en.wikipedia.org/wiki/Qubes_OS
[1]: https://www.qubes-os.org/doc/license/
- --
Live long and prosper
Robin `ypid` Schneider
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWsROvAAoJEIb9mAu/GkD45M4P/AiKKC6JRnNXF7v9ba1NZTG7
0oSq5dHo8xy5Z+4BPbR9FDyoXvn3DdlnY5NO9DUvy/d3YxOghzCNNehBEltUm4V2
42xJCCfRA9NIHXNARq1wOmn548Cgez3b+0J/Lj91LtFaiMsMMdWKM1eylWDZ33c1
r6i0Gw0LsuyIB+Hl+ksUPsEftf8jTkLzTgBOUHcegO/UF5SzCcTe3fgXxyvPmhPE
Mt9DOd4jUOjw0ulV8G1HM7TgJdulPgBjGG/v6TvJUCAqB5D/mZMxDobJZXpJp15G
kgSfLqilEPsycTLk6HCh4kdb6jPsOKKbwOjYrgydWRv7OIS7YseuMWp7tGk4SxRh
beOrcDfVuvqwYbWTHJr4RtFkKRIbIPw/RenZ619Vu6qjF2KJkLrLvl87n97zBZkV
RG3tiOXvCjZXRN+oAK3YMcVul7Zd4wSjdi6CxFzoyuicMCTHp/0YOXWGTNSp5GVx
iDDg135CtxusnCjzRrdW22L7xDHBIUgwzbuurujeQnCKisu0zTxRsHVn9HCWaQcA
F9qMVHm03RP2auZwnRpA4C1sH+AJ5eMykFXkcNp06VPPnCdMbRvxq9w6Jmw+AlY2
fdrSLbPk9vURhaRe8HVjt+8eMEoYef7nw32Lm4K1nImm4Kj1dQpgRKHul1QCpAEM
qj2AoXxRrsfcH3CeGGCZ
=D+21
-----END PGP SIGNATURE-----
Marek Marczykowski-Górecki
Feb 2, 2016, 3:55:45 PM2/2/16
to Robin Schneider, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Tue, Feb 02, 2016 at 09:38:07PM +0100, Robin Schneider wrote:
> On 27.01.2016 16:20, Rafał Wojdyła wrote:
> > [And again, this time with inline signature...]
> >
> > Hi all,
> >
> > I'm happy to announce that today we are opening the full source of Qubes
> > Windows Tools!
> >
> > Detailed instructions for building are in the qubes-builder-windows repo,
> > which also includes an example builder config to use.
> >
> > Following repositories are needed to build the installer:
> >
> > * vmm-xen-windows-pvdrivers * core-vchan-xen * windows-utils *
> > core-qubesdb * core-agent-windows * gui-common * gui-agent-windows *
> > installer-qubes-os-windows-tools
> >
> > And here you can find the official blog post:
> > https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
>
> Thanks very much for your work and for releasing the sources +1
> I just wanted to updated Wikipedia [0] when I noticed that [1] should probably
> be updated before that. I guess that should be done by ITL people?
Indeed. Done.
> On 27.01.2016 16:20, Rafał Wojdyła wrote:
> > [And again, this time with inline signature...]
> >
> > Hi all,
> >
> > I'm happy to announce that today we are opening the full source of Qubes
> > Windows Tools!
> >
> > Detailed instructions for building are in the qubes-builder-windows repo,
> > which also includes an example builder config to use.
> >
> > Following repositories are needed to build the installer:
> >
> > * vmm-xen-windows-pvdrivers * core-vchan-xen * windows-utils *
> > core-qubesdb * core-agent-windows * gui-common * gui-agent-windows *
> > installer-qubes-os-windows-tools
> >
> > And here you can find the official blog post:
> > https://www.qubes-os.org/news/2016/01/27/windows-tools-open-source/
>
> Thanks very much for your work and for releasing the sources +1
> I just wanted to updated Wikipedia [0] when I noticed that [1] should probably
> be updated before that. I guess that should be done by ITL people?
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWsRfJAAoJENuP0xzK19cszqMH/RXpoe4Apo+ZxKe6Ssbzu4C2
Version: GnuPG v2
FXYJo8IBokpw41wy2GCfJj0oY6hBMc7MNHt6x9zpxrA6aYJxl8lQUwe4xd5lffwX
8rJZAxVoP3E1tZmnrQ0FZPB1HOQDZb+VPcDZxzLjQrskiKgoMfEBcEimhvFMX6Wt
W0VUnd8eIL936CF6LJ3GDR3BM4WYnleBEBoJSFeYXPRUS/hIvb+oRMjKUSfHAuaq
JunXd9Lgc1bPP+EThnr3Gik0dX82Wq92M0kke9QTeh4KjfEwOqTIhv75SqVvkbiX
XLg1HnALhMRg9pRlJlfwKlNe3YY3QofLzIh0rxAhcCHTNKhFKwD/41vHydLBFrU=
=WkIT
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages