Apr 11, 2024, 15:57 by qubes-devel@googlegroups.com: > On Thu, Apr 11, 2024 at 04:19:06AM -0700, Gerhard Weck wrote: > >> Currently, there does not seem to be a working way to run Windows VMs >> using Qubes Windows Tools under Qubes R4.2.1. So putting Qubes R4.1.2 to >> EOL forces installations with such qubes to select one of the following two >> alternatives: either discontinue the use of Qubes as a protective shield >> for Windows or use a deprecated version of Qubes. Both have to be regarded >> as a regression. >> >> Windows qubes imported from R4.1.2 to R4.2.1 should retain their complete >> functionality or, alternatively, EOL of R4.2.1 should be postponed until >> such functionality is available under Qubes R4.2.1. >> >> This problem may be solved if Qubes issue #1861 >> <https://github.com/QubesOS/qubes-issues/issues/1861> is completed before >> the scheduled EOL for R4.1. >> > > The problem is that the QWT are currently insecure. It seems > unreasonable to suggest that Qubes should allow users to work with such > software. > > In my view, if some software is deprecated or insecure, then it is > reasonable for it to be removed from a new release. This happens all the > time in other distributions, (and in Windows too.) > > Is it true that there is no working way to use QWT, or is this an issue > with some aspects of the QWT, or is it specific to importing from 4.1 > with some features enabled? > There are users of Windows in 4.2 > > -- > I never presume to speak for the Qubes team. > When I comment in the mailing lists I speak for myself. > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-devel/ZhgIcbJLIq7eIYUa%40thirdeyesecurity.org. >
> In my view, if some software is deprecated or insecure @unman, do you mean "QWT is deprecated"? Otherwise why do you mention deprecation at all? Is it an opinion shared by the Team, too? The current situation makes Qubes OS R4.2 the first version of Qubes OS that has such a bad Windows support on the release date. And it also makes Qubes OS probably the worse operation system to have Windows running virtualized, because Qubes OS is Xen-based and it limits other nice options like running VirtualBox or any other solution to make Windows running well with comfort of clipboard sharing and other things. It is unfortunate, because I love Qubes OS and back in the day Qubes OS was one of the best to run Windows virualized, because it had integrated clipboard transfer, seamless windows and other features of the system united in a similar over GNU/Linux and Windows. All this being considered, I completely support Gerhard Weck. EOL of R4.1 should be postponed until restoring qubes and the whole Windows functionality is available under Qubes R4.2 or later releases. Even more, I think that releasing R4.2 that is not able to run qubes created in the previous minor version R4.1 was not such a good idea. Almost all users won't be able to solve this situation themselves and they will have unusable backup of unbootable qube with their valuable data in it. From this point of view, R4.2, maybe, should not been released at all until packaging problems of QWT would be solved (as blocker?), to prevent users getting in such situations in the first place. Users are the most valuable part in the project, to my opinion. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/NvDGV6q--3-9%40tutanota.com.
