Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?

[Yuraeitha]

On Saturday, February 3, 2018 at 2:16:15 PM UTC+1, Elias Mårtenson wrote:
> On Saturday, 3 February 2018 12:06:20 UTC+8, Andrew David Wong  wrote:
> 
> > As far as I know, Qubes Windows Tools continues to remain on
> > indefinite hold. We welcome anyone from the community with the
> > requisite skills to take over development (or just pitch in here and
> > there).
> 
> I wanted to be that person, and I did take an initial look. However, being an 
> experienced Unix developer was not much help in figuring out the issues with 
> the Windows tools.
> 
> Is there some source of information that helps explain what the problem could 
> be, and where to start looking for it?
> 
> Regards,
> Elias

@Elias
It would be amazing if you can get the needed information and have a second 
look at it.
I'm only speculating here, but could it be possible that the code is more or 
less the way it's supposed to be, but has just not been tested, verified, and 
then distributed on Qubes 4? 

If the precedent for release requirements is the expectation of quality before 
release, then perhaps the hindrance is just testing and verifying if it works? 

Also it seems like some functions "might (maybe)" work as intended, for example 
I can copy files between VM's and Win7, on a Win7 that was installed on Qubes 
3.2., but backup restored on Qubes 4. Others seem like they can do this too. 
Also it seems it's a common problem not to be internet in the restored 
Q3.2-Win7, perhaps the code is different in regards to how it ties networking 
with Qubes 4? I have no idea about the rest of the mechanics from a users 
perspective though, and most certainly not as a developer as I unfortunately 
don't have such skills, I wish I could help more.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/fac5da5a-a17b-444d-bc6a-7e24956954be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?

[Yuraeitha]

On Saturday, February 3, 2018 at 5:06:20 AM UTC+1, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2018-02-02 17:19, Yuraeitha wrote:
> > 
> > It seems omeg who has been maintaining Qubes-Windows-Tools the last
> > few years, has gone inactive
> 
> He is instead working on other projects for ITL's corporate clients,
> so "inactive" is not quite accurate.
> 
> > https://github.com/QubesOS/qubes-installer-qubes-os-windows-tools 
> > and thus far, it looks like no one else has picked up the project.
> > 
> 
> Correct.
> 
> > If it is not planned to be done any time soon, then that's alright,
> > I can live with that. I'm already immensely grateful for everything
> > the Qubes team has done. But it's not so easy for everyone though,
> > some people are more heavily reliant on Windows than others for
> > certain applications.
> > 
> > This post is NOT a complaint or anything of the sorts, but instead
> >  a question to settle expectations on the correct path, instead of
> >  looking every day for a new update, which can be a lot of 
> > uncertainty or for some people even anxiety and frustrations, when
> >  on Qubes 4 without a means to get Windows 7 installed. Essentially
> >  people who need Windows and would love to get Qubes 4, are caught
> >  in-between without any idea when or even if Windows 7 will be 
> > supported anytime in the near-term future.
> > 
> > In other words, just knowing it won't be anytime soon is in a way 
> > also very good news, because it puts expectations in the right 
> > place instead of uncertainty. Any such news-update on what is going
> > on with it and what to expect, would be appreciated.
> > 
> 
> As far as I know, Qubes Windows Tools continues to remain on
> indefinite hold. We welcome anyone from the community with the
> requisite skills to take over development (or just pitch in here and
> there).
> 
> > Also, I'm not entirely sure regarding the code itself, but it 
> > should be somewhat close to Qubes 4 in the current 
> > Qubes-Windows-Tools? For example the Qubes 3.2. Win7 restored from
> >  backup in Qubes 4, seems to more or less work, somewhat smoothly,
> >  but not perfect. If so, maybe someone else can help with bringing
> >  Qubes-Windos-Tools to Qubes 4? Unfortunately I have no coding 
> > skills of this sort though, otherwise I'd give it a shot.
> > 
> 
> Sorry, I don't know.
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlp1NS0ACgkQ203TvDlQ
> MDCZYw//X/AlrUieQTF4ebMSab60xahi5erwpQc87Yzvb7WLLYBEnmY19d60M8IT
> oOr6p3zroDc+VvwBW4vIcp4S7RUNIDbIyppulW+6eiFunQK8kZGpks+RKfntxwEq
> Z8MCFeVNCedn43AGc6DCOLFrSsQVUR0LKVGIcI/Lhoe60zdvoMofnlF2hHRzWqvb
> 9UYuu/Kiqyy8RVyNq1LSNJ4/5jIIFDoxk12Wngc3s22OU5/u6I2vlnUHHwDC/X6n
> kbWSa8ltdKIOpglWxf34G7G60kdQVLfqw88mFzGUMk02EOeGkErMuG39wzCCGWyA
> 0Yp+KWeUaTH7mzUVTHR4G0uuWlFx7IaXUWOSJVmuSjItCQ4s7qbZ8A78ajN1aLYd
> JhhVnM8jzDF8zkrAd6Ez+zRVa9im/m1puck3uNb8Ou6VD0FnRWowl6iz0ijRhXsF
> A6qgr4jiGqqp3OSvxActu32KbW2ogxrDQThztcJgY1DuhDF/Y6YBHRI9I92udQ6r
> +A5OKoIKe3cskntkF5lrSawqVtyD+lxuT00gwwJrolj1ixdHt8ufyezvJxDYZJac
> UIu4y95w4H28YoxCY5bmoMIB5ncl4kskKs7qFpNbVHs4d8GsW1NcT2fxNzslGtsV
> D7muRf9n/gX3Ui5wNwwjP0gVMD6RrsY4wRdt4Jzk87VVdJIEiXM=
> =LLLN
> -END PGP SIGNATURE-

Thanks Andrew, this was exactly what I was looking for, much appreciated. 

I'm gonna settle in for a plan B as listed below, although it looks really 
interesting if Elias will be looking into it. Maybe Marek or someone else with 
insight into the code can help a little bit to get started?

But for the time being, I might try install Qubes 3.2. as a plan B to create 
some temporary unlicensed clean Win7 Qubes backup's, and see if I can transfer 
them to various of other Qubes 4 systems. This is mostly needed for my friends 
though, and I still need to figure out if this is allowed within the use-cases 
of the Windows 7 license or not, they will use their own licenses. 

This method is a bit cumberstone if the code inside the Win7 installed on Qubes 
3.2. is buggy and creates unreliable issues, like unreliable transfer of data 
integrity. Hopefully nothing bad will happen.

Also need different types of Windows 7 copies for different types of licenses, 
which is a bit problematic, but not impossible.

For now this temporary plan B, this might be a work around to get a new clean 
Win7 on multiple of different Qubes 4 systems, although a bit cumberstone, and 
uncertain possibility of data integrity risk.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 

Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-02-03 07:16, Elias Mårtenson wrote:
> On Saturday, 3 February 2018 12:06:20 UTC+8, Andrew David Wong
> wrote:
> 
>> As far as I know, Qubes Windows Tools continues to remain on 
>> indefinite hold. We welcome anyone from the community with the 
>> requisite skills to take over development (or just pitch in here
>> and there).
> 
> I wanted to be that person, and I did take an initial look.
> However, being an experienced Unix developer was not much help in
> figuring out the issues with the Windows tools.
> 
> Is there some source of information that helps explain what the
> problem could be, and where to start looking for it?
> 
> Regards, Elias
> 

Here's all the relevant documentation I'm aware of:

https://www.qubes-os.org/doc/windows-tools-3/
https://www.qubes-os.org/doc/windows-debugging/

Omeg and Marek (CCed) may be able to provide better direction.

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlp1/ZkACgkQ203TvDlQ
MDDnow/9HqNYHCfzwXfRh54thay67YuY6Hf6pMUmomY5i5/ctrHEqsnxrFOA8v5s
h6celuDds/IYhs9/E6j9aDi6Xrfa4hTn/YpmcZc8Cijw1hUrmrTHsOeMNqfG2mcW
3TmUhrJ55Ds7GN47MK1haYf630EfzoolCowGs5FHN+YWWnHkdxQlH7szpqb33KiY
VGBKJcPM7FI7av6g8Y8Qn7GehIei9CoHDm7N3YLq98pFcfKrQLASrpU4O5S+eLkB
MXIMG6FYRqnxwiGPuJ02uLdtM9X421tWX2ViPt+3S+aKfd05mubkh2oPYZBRhB+W
ZiQPlK9l2VEL8TtW7YrYrJYZmcJt5Gy/QoZa10IBICwu37NcphixQ2PiO8U0bPz6
0GxuGbQT6hUZnZuquG9kwXHDK4oD2AltFoFj6/W8aslS5B0RjgcQQBcgHWoHVsv4
fgoRVasgFCMgm7lCgrChBszqS223sbbshCMCu6tyUJCfxcfRpak77uVGvQyJ3xQv
1auT7deeSkxyEEdDHNiEl8pD7MhC+0rc2H+2nOgaq3ZGL3OlOx13omaaC9Vhi2hx
7Dr62HPxz64X8nLbuaacAGDLAam4AWK0WtmDFSll7cDz6Sm78HCoNwIHgXh9x3Sj
9aF2XCB7Yr00sDj+wEreb5YB8meNl3R4aBlVNBpZ2ar64OKst30=
=uBDG
-END PGP SIGNATURE-


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/97e78590-fbca-36c3-5b0d-9a3dae0f102d%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-devel] qubes-url-redirector v2.1 released!

['Raffaele Florio' via qubes-devel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Andrew,
Thanks for the comments!
1) I partially agree. Can you explain better please?
2) I don't consider this case an issue. This extension is designed to block and 
redirect non whitelisted URLs, that is opened through the browser (e.g. with 
the shell, interactively, etc..). Evidently you restored non whitelisted URLs. 
So qubes-url-redirector did its job.
3) In the plan there is a quick settings feature (there is a GitHub issue) to 
handle such type of scenario.
4) This option adds a lot of complexity and "DispVM" automatically become a 
sort of "SessionVM". Furthermore this option increase, greatly, the complexity 
and there is the need to communicate with Dom0. It only knows about which VM is 
alive.
4.1) Nonetheless I can add an option (in quick settings) to define a handler VM 
associated with the current tab. However you can already open in specific VM 
(also DispVM,) a link, through context menu entries. I don't consider this a 
vital and very useful feature. I consider the currently granularity, 
sufficient. However I'll wait for other opinions and Qubes 4.0, because in the 
old post [0] I was warned about substantial change regarding the privilege that 
permits a VM to choose which VM should handle an action.

[0] = https://groups.google.com/forum/#!topic/qubes-devel/fsIAQO1xFkU

Best Regards,
Raffaele.
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE9bU8N8AgwMcjiC1xjTxG+6f1ce4FAlp17MsACgkQjTxG+6f1
ce4hxg//SROBl5uwyxhSVZo4A8f6rvphS0DyEkIqbfrsuWXgWxpO+hAWbyDkkqVJ
0lgbRP9rQHO65vz8Egveklsa6cBJtYIYf6UBvNv5A16b66jBz370VIq/1eVJDbuQ
/EmJ/1fuX4TUrA5EKVpv/+YJU9+4J23micGCmP8+AckoApw2emtwHw2FI//2VtMF
kNv7Ur00sig2lR9jC0N/RnShOdv/0Z7SQ7pnxQk40RJ62gs3zHzJ6APT8Cs7/HFH
tiVw0XnQAWiBgvbjyAGcliIEYzhvE+lYJfFRu5bLT8fAlNJb1uHhY+LoTRt5YQLP
0kk/WLiAQz/TUGfiIanzV43XKFLzaeXUVZv/qpOULQ5w6J9k5+HRn2LfRBh/3F5c
kxeYQJXRigO5D8r7PNVmeeS5D3j6EWho+AFE4TyP0F6TGcImZhHQEEoefnWXbPDF
Tiy3zDKeudP24ZDm1UrT43pz8RwQ2fnsCO0tkaZKEbHDCVpJhEfSu0mq6SJSeMOz
4n2NGStWwv/uJGORDMmGgmudQgiEceWLVvzSdgzm3z6RT0ZmzHicoiQQrsZJrIB+
jOJVALF/QuQRatZV3JLTNad3htg5rmKQNLbICAm9vsokOW3VV14lYz7FyDgrX/VD
XPEWOcvNvVyuyQrryBE0LzuHlUYg6YkuoaAhRNMKb8c6kV4LWLA=
=YTal
-END PGP SIGNATURE-

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/d_Nzv35xxqjrIZCeHtxu7nUjxR7v18v3TMvwhHxlwHdscXkmoW8X4Qro46k1IiOll0wuC84E8DH_jZuDszKsTLfXb0rx_QWFTwLEBBoijz4%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-devel] Are there currently anyone assigned to update Qubes-Windows-Tools?

[Elias Mårtenson]

On Saturday, 3 February 2018 12:06:20 UTC+8, Andrew David Wong  wrote:

> As far as I know, Qubes Windows Tools continues to remain on
> indefinite hold. We welcome anyone from the community with the
> requisite skills to take over development (or just pitch in here and
> there).

I wanted to be that person, and I did take an initial look. However, being an 
experienced Unix developer was not much help in figuring out the issues with 
the Windows tools.

Is there some source of information that helps explain what the problem could 
be, and where to start looking for it?

Regards,
Elias

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/982dc0b2-f912-40b0-ab6d-523b788069dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-devel] qubes-url-redirector v2.1 released!

[Andrew Clausen]

Hi Raffaele,

I just tried it.  A few comments:

(1) I'm not thrilled about using wget to install things.  (I don't trust
https very much.)  What's wrong with using the locally distributed copies
of files from git?

(2) It wreaks havoc!  When I restarted Firefox, and did "restore old tabs",
it tried to open them all in disposable VMs.  Please start with a
non-disruptive default, or issue big warnings.

(3) Suggestion: have a "paranoid" mode that can be enabled easily on the
toolbar to switch the default to disposable VMs.

(4) Suggestion: you could perhaps re-use disposable VMs, since they are
quite costly to create.  There could be a button to create a fresh
disposable VM.

Kind regards,
Andrew

On 2 February 2018 at 18:38, 'Raffaele Florio' via qubes-devel <
qubes-devel@googlegroups.com> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi all :),
> I've just released the qubes-url-redirector extension. The GitHub repo is
> at [0] and the issue on QubesOS's repo is at [2].
> The extension is based on the gsoc idea [1]. Soon I'll work on the
> Thunderbird one :).
>
>
> Here a brief description:
> qubes-url-redirector permits to manage which VM is responsible to open
> links, obviously redirection happens before any TCP connection is made.
> Furthermore, through context menu entries, you can open a specific link in
> a custom way. Currently you can open links in: DVM, a default-VM, a
> specific VM and in this VM.
> Before this release, the installation process was a pain, now it's very
> simplified. I hope that you enjoy it! :D
>
>
> [0] = https://github.com/raffaeleflorio/qubes-url-redirector
> [1] = https://www.qubes-os.org/gsoc/#thunderbird-firefox-and-
> chrome-extensions
> [2] = https://github.com/QubesOS/qubes-issues/issues/3152
>
>
> Best Regards,
> Raffaele.
>
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEE9bU8N8AgwMcjiC1xjTxG+6f1ce4FAlp0sCMACgkQjTxG+6f1
> ce4eKxAAkSxYKxp8e1gvTmiG2douRvicYm+U5HSeRQ/ORikjVf796TDmWhAAplYB
> WNC8y6Hyy9PfRMS/ySY5qs1IguK6XlLa/+2zCZv5UGl7R8n0GeLmnxVRgSMStIRz
> rZk68tAxOpConrvLx5JJPL2og2ZKPfjVjXRWGmHwhPkCOM/Bn6drAgJm2W3NLjhZ
> Cp8Hwqzi3Kd8+K7y/nvkBcA/FUJe/y8Ctdf8KDRtKcO83fQKQDDGLjoeQAb89zTj
> w4BEvMa2UTfEtY1POugAL73UDf/mRj8Y4K0IMlPRC8G619OminnyIIAdVaVcc4cg
> Jzg0qmYMJ+ZSNGZXqVmaminoLQzf9ds2w+VTh9AlkrXCVckAagcSXCwsh/X7XYAc
> TsK5rAqzuvTb79uj+h9a3RAwtpwnawY0famhLCL/YDZaKPcF/saGkwZefDksAI4R
> S0fKsJZkXT9SkwpQOeV9wSlIwm7p1IkSsGCKDm6HOtolOO0AUEejFg4af8hVWAl2
> gHTvjN4+qZbFgstbNbTaJ7Bh6WKlDa3HcrJk11x/S29QeQ08W1qeTuasYl/Yr+Zi
> fKAwfhqjFa/N8qBtInogoyzqxk5BPeikOFnedz1P+Afxe/jfuUnrleChqwKvSc89
> jSLmqKi+lrT97EgMVrQm6dXJaLZGZNhMF4GooRSYd3gZPKzXgTE=
> =Bco5
> -END PGP SIGNATURE-
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to qubes-devel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/qubes-devel/PhffsPxhxd-8U28yQLW4CBpOqiZwqOmno2DyWNftwMIxzyKowatO2K_
> 8qluvPyhkt1kBBNKIc2XqD_60Ur-qm5QKvTjaC0qba7OKEORAles%3D%40protonmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/CAAXZBWJBNrM9ffbg6yDgFCN0eGQa6RsMFPOFR%3D_Gh0qJFe5J4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.