[qubes-users] Cannot use bluetooth headset with Fedora-30 + Bluez
Hi All, I've installed Bluez and Pulse Audio on a Fedora-30 based VM. When I attach my Bluetooth USB dongle to the VM I see the Bluetooth icon in the upper right corner. If I click on the icon it opens Bluetooth Manager and I can scan and find my headset. Then I "trust" it and successfully pair it. To my surprise, when I open the browser and play any sound it comes out of the embedded speakers in my computer (Dell Latitude 5590 Core i5 8th gen). When I open Pulse Audio Control to configure the audio I see only "Qubes vChan Output/Input" and not the Bluez device. Any ideas? Thanks -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7f1ffdd8-9911-496b-9a54-b409f06aedd2%40googlegroups.com.
Re: [qubes-users] I am experiencing various problems with my OS
'Rock Francis' via qubes-users: > I've always had trouble with any Linux Beast OS from my original PC to my > original laptop. > > But the biggest problem that I'm facing right now is unlocking my ability to > connect through my ethernet cable, I keep running into the problem know as > "libexlight" or something. > This is not near enough information to enable someone on this list to help troubleshoot your issue. Please provide the following, and perhaps someone will be able to respond: * details of the hardware you're running * details of the OS you're running * specific error message * context of the error message (what you're doing when it appears) ~abel -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a2e14866-48eb-8f00-21be-35f16c7cbe2b%40guardianproject.info.
[qubes-users] Re: qvm-create-windows-qube 2.0
mandag den 13. januar 2020 kl. 10.49.12 UTC+1 skrev Elliot Killick: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hello, all! > > Not too long ago I released qvm-create-windows-qube but quit pushing > changes for a while because I realized there was still a of work to be > done and I wanted to get it out of the dev/beta phase before releasing a > new version. This looks promising. Looking forward to testing it, thank you. > Well, it's over 200 commits later and I would say it's well out of > beta now. > I actually believe that the general adoption of Qubes in the world would be larger if the windows guest support was better, you might actaully be able to get funding for your efforts (https://opencollective.com/qubes-os/expenses/). You might ask a QubesOS representative for that possibility(Andrew, maybe?) That might push the adoption to be broader and the sponsors to be more and helping Qubes to be even more widespread than it is now. Sincerely Max -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e0e8dea5-ddac-47da-8421-834417a7b3e1%40googlegroups.com.
[qubes-users] Re: Qubes Kali / Parrot vm guide
torsdag den 16. januar 2020 kl. 00.15.29 UTC+1 skrev Rafael Reis: > > Sources: > > https://www.qubes-os.org/doc/pentesting/kali/#qubes-40 > > https://docs.parrotlinux.org/getting-started/install-qubes/ > > > Hey guys. > > I'm following the instructions above to install Kali / Parrot to Qubes. > > Both guides require a debian dist-upgrade to the testing release. Both > guides mention the following: > > > *Note:* During execution of a dist-upgrade command read carefully list of >> packages to be removed. If it contains qubes-* packages, terminate >> operation and try to resolve qubes-* packages missing dependencies first. >> > > This is exactly what happened. I have: > > qubes-core-agent-dom0-updates qubes-core-agent-passwordless-root > qubes-gpg-split qubes-img-converter qubes-input-proxy-sender > qubes-mgmt-salt-vm-connector qubes-pdf-converter qubes-thunderbird > qubes-usb-proxy > > > for removal. > > I'm not advanced enough to know what to do to "resolve qubes-* packages > missing dependencies first." > > Could anybody help? > I had success with entering a command like this just before doing the dist-upgrade(don't remember all the packages): sudo apt install qubes-core-agent-dom0-updates qubes-core-agent-passwordless -qubes-gpg-split qubes-img-converter qubes-input-proxy-sender qubes-mgmt- salt-vm-connector qubes-pdf-converter qubes-thunderbird qubes-usb-proxy That, I seem to recall, removed the need for package removal and made my first easily installed kali based on debian-10. Sincerely Max -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b4adb67a-1ec0-4d6c-9f19-3cfbae1b6c70%40googlegroups.com.
Re: [qubes-users] Xen doesn't recognize that a VM has finished starting
On Wed, Jan 15, 2020 at 11:22:12PM +, Claudia wrote: When I try to start another VM which has been set to use the new-sys-net VM as its NetVM, the startup times out and I get the error "libxenlight has failed to create new domain NEWVM"... /var/log/xen/console/guest-NEWSYSNET-dm.log doesn't show anything obviously wrong, apart from some call traces of unclear origin. Not sure, but it sounds like maybe the guest's qrexec isn't connecting to the host. Make sure it's installed and running properly in the guest. Check `systemctl status qubes-qrexec-agent.service` in the guest, and /var/log/qubes/qrexec..log on dom0. That's very possible. The guest is OpenBSD so no systemctl :) Here is the other discussion about this, I have not yet gotten a chance to try the suggested fix, but I anticipate that it will work: https://github.com/QubesOS/qubes-issues/issues/5294#issuecomment-574225742 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200116022739.GA1043%40danwin1210.me.
[qubes-users] I am experiencing various problems with my OS
I've always had trouble with any Linux Beast OS from my original PC to my original laptop. But the biggest problem that I'm facing right now is unlocking my ability to connect through my ethernet cable, I keep running into the problem know as "libexlight" or something. Regards, Rock Francis Sent from ProtonMail mobile -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0WkJhyNTGXSQ5oi92ZeyRY5ZQhu4-FC5PDcJqQtaeuhWQvyf1sLid9tzDMBpjF8iaaYeq0A-2rx6aVbuQgWPw5d0MSL5VBUEdZK_fCRjEF0%3D%40protonmail.ch.
Re: [qubes-users] Xen doesn't recognize that a VM has finished starting
January 14, 2020 12:29 PM, "tetrahedra via qubes-users" wrote: > I have a HVM VM that I'm trying to set up as a new sys-net. > > However, when I boot it, Xen / Qubes doesn't seem to recognize that the > domain has finished > starting. > > The Qubes menu at the top right shows the red circling progress logo, even > though the domain has > booted already. > > When I try to start another VM which has been set to use the new-sys-net VM > as its NetVM, the > startup times out and I get the error "libxenlight has > failed to create new domain NEWVM"... > > /var/log/xen/console/guest-NEWSYSNET-dm.log doesn't show anything obviously > wrong, apart from some > call traces of unclear origin. Not sure, but it sounds like maybe the guest's qrexec isn't connecting to the host. Make sure it's installed and running properly in the guest. Check `systemctl status qubes-qrexec-agent.service` in the guest, and /var/log/qubes/qrexec..log on dom0. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/57ab4930a68179b8a74859b7c59df401%40disroot.org.
[qubes-users] Qubes Kali / Parrot vm guide
Sources: https://www.qubes-os.org/doc/pentesting/kali/#qubes-40 https://docs.parrotlinux.org/getting-started/install-qubes/ Hey guys. I'm following the instructions above to install Kali / Parrot to Qubes. Both guides require a debian dist-upgrade to the testing release. Both guides mention the following: *Note:* During execution of a dist-upgrade command read carefully list of > packages to be removed. If it contains qubes-* packages, terminate > operation and try to resolve qubes-* packages missing dependencies first. > This is exactly what happened. I have: qubes-core-agent-dom0-updates qubes-core-agent-passwordless-root qubes-gpg-split qubes-img-converter qubes-input-proxy-sender qubes-mgmt-salt-vm-connector qubes-pdf-converter qubes-thunderbird qubes-usb-proxy for removal. I'm not advanced enough to know what to do to "resolve qubes-* packages missing dependencies first." Could anybody help? Thanks! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/82b8dd63-ec19-479e-8407-ffbe5e8acc9b%40googlegroups.com.
[qubes-users] Qubes OS Network installation - Possible to Mirror dom0 iso contents?
I was trying to put together a network installer for QubesOS for
netboot.xyz.
You are already leveraging Dracut with the full network stack and livenet
hooks so booting something like this example below in IPXE loads the
installer interface: (if you rip isolinux/initrd.img isolinux/vmlinuz,
and LiveOS/squashfs.img out of a Live CD)
:CUSTOM
imgfree
set url http://192.168.10.13:8080/
kernel ${url}vmlinuz root=live:${url}squashfs.img
repo=https://ftp.qubes-os.org/repo/yum/r4.0/current/dom0/fc25/
ro rd.live.image rd.lvm=0 rd.luks=0 rd.md=0 rd.dm=0 initrd=initrd
initrd ${url}initrd
boot
The problem is that the hosted repo does not contain the base packages in
the ISO repo (bash among others).
Would it be possible to mirror the ISO repo contents to
"/repo/yum/r4.0/current/dom0/fc25/" to support network based installs
without a local repo?
Let me know if you need anymore information.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/ee3ec477-aa3f-4384-9c45-b1e6d588fad2%40googlegroups.com.
Re: [qubes-users] PCI passthrough issues
Hi awokd, I tried both combinations beforehand, neither of them helped. I'm not really sure whether I've added xen-pciback.hide to the right place, but I added it to the */etc/default/grub under *GRUB_CMDLINE_XEN_DEFAULT and commit the change. If that's the thing I should've done, sadly, it still doesn't work. Dana srijeda, 15. siječnja 2020. u 19:36:28 UTC, korisnik awokd napisao je: > > Ana Z: > > Hi, > > > > I tried to passthrough my old PCI USB controller (chipset NEC > 0720100AGM) > > to Windows 7 HVM but I ran into some problems. > > > dom0:01_05.0 USB controller: NEC Corporation OHCI USB > > Controller > > win7-z (permissive=true, no-strict-reset=true) > > dom0:01_05.1 USB controller: NEC Corporation OHCI USB > > Controller > > win7-z (permissive=true, no-strict-reset=true) > > dom0:01_05.2 USB controller: NEC Corporation uPD72010x USB 2.0 > > Controller win7-z > > (permissive=true, no-strict-reset=true) > > If you haven't, try attaching these with one or both options set to > false. If it still doesn't help, see if > xen-pciback.hide=(01:05.0)(01:05.1)(01:05.2) in xen.cfg helps. > > -- > - don't top post > Mailing list etiquette: > - trim quoted reply to only relevant portions > - when possible, copy and paste text instead of screenshots > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/291f5e41-0b03-4a6a-bfec-92a461796991%40googlegroups.com.
Re: [qubes-users] PCI passthrough issues
Ana Z: > Hi, > > I tried to passthrough my old PCI USB controller (chipset NEC 0720100AGM) > to Windows 7 HVM but I ran into some problems. > dom0:01_05.0 USB controller: NEC Corporation OHCI USB > Controller > win7-z (permissive=true, no-strict-reset=true) > dom0:01_05.1 USB controller: NEC Corporation OHCI USB > Controller > win7-z (permissive=true, no-strict-reset=true) > dom0:01_05.2 USB controller: NEC Corporation uPD72010x USB 2.0 > Controller win7-z > (permissive=true, no-strict-reset=true) If you haven't, try attaching these with one or both options set to false. If it still doesn't help, see if xen-pciback.hide=(01:05.0)(01:05.1)(01:05.2) in xen.cfg helps. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0203b550-3966-52f2-9286-1fcc480a2ae2%40danwin1210.me.
[qubes-users] PCI passthrough issues
Hi, I tried to passthrough my old PCI USB controller (chipset NEC 0720100AGM) to Windows 7 HVM but I ran into some problems. I first found the controller in dom0 with *qvm-pci*: dom0:01_05.0 USB controller: NEC Corporation OHCI USB Controller dom0:01_05.1 USB controller: NEC Corporation OHCI USB Controller dom0:01_05.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller I then attached those three with *qvm-pci attach --persistent --option permissive=true --option no-strict-reset=true *and I got: dom0:01_05.0 USB controller: NEC Corporation OHCI USB Controller win7-z (permissive=true, no-strict-reset=true) dom0:01_05.1 USB controller: NEC Corporation OHCI USB Controller win7-z (permissive=true, no-strict-reset=true) dom0:01_05.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller win7-z (permissive=true, no-strict-reset=true) I tried running the Windows 7 HVM and the PCI USB controller was recognized, alongside USB Root Hubs, but whenever I physically attach an USB device (3 different sticks and 1 WLAN stick) I always get "USB Device Not Recognized" and "Unknown USB Device" in one of the used ports. Before I attached the controller to Windows HVM, dom0 recognized any device attached to the controller, and I tried booting up my spare disk with the same Windows 7 installation I used for HVM and the PCI controller works there, with recognized USB devices when attached. My question is, what is the next step I should make in troubleshooting the problem? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7587670e-d33a-4d30-a7cb-0709091de4c1%40googlegroups.com.
[qubes-users] Qubes OS 4.0.3-rc1 has been released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Qubes Community, Shortly after the announcement of 4.0.2 [1], a bug [2] was discovered in the dom0 kernel included in that release. Since the bug would have presented installation problems for the majority of users. That bug has now been fixed, along with a few installer fixes, resulting in 4.0.3-rc1. In keeping with standard semantic versioning [3], we've incremented the patch version number to reflect this latest fix, so 4.0.2 has become 4.0.3. This is the first release candidate (rc1) for 4.0.3, because we'd like to give the community an opportunity to test it before declaring it to be the stable release. However, the changes from 4.0.2 are minimal, and 4.0.2 itself was preceded by three release candidates, so we plan to keep the 4.0.3-rc1 testing period brief. As with 4.0.2, 4.0.3-rc1 includes many updates over the initial 4.0 release, in particular: - All 4.0 dom0 updates to date - Fedora 30 TemplateVM - Debian 10 TemplateVM - Whonix 15 Gateway and Workstation TemplateVMs - Linux kernel 4.19 by default Qubes 4.0.3-rc1 is available on the Downloads page: https://www.qubes-os.org/downloads/ What is a point release? A point release does not designate a separate, new version of Qubes OS. Rather, it designates its respective major or minor release (in this case, 4.0) inclusive of all updates up to a certain point. Installing Qubes 4.0 and fully updating it results in the same system as installing Qubes 4.0.3. What should I do? = If you installed Qubes 4.0, 4.0.1, or 4.0.2 and have fully updated [4], then your system is already equivalent to a Qubes 4.0.3 installation. No further action is required. Regardless of your current OS, if you wish to install (or reinstall) Qubes 4.0 for any reason, then the 4.0.3 ISO makes this more convenient and secure, since it bundles all Qubes 4.0 updates to date. *Note:* The Qubes 4.0.3 ISO will not fit on a single-layer DVD (for the technical details underlying this, please see issue #5367 [5]). Instead, we recommend copying the ISO onto a sufficiently large USB drive. [6] However, if you would prefer to use optical media, we suggest selecting a dual-layer DVD or Blu-ray disc. Release candidate planning == If no major issues are discovered in 4.0.3-rc1, we expect the stable release of 4.0.3 to follow sometime next week. As usual, you can help by reporting any bugs you encounter. [7] [1] https://www.qubes-os.org/news/2020/01/02/qubes-4-0-2/ [2] https://github.com/QubesOS/qubes-issues/issues/5553 [3] https://semver.org [4] https://www.qubes-os.org/doc/updating-qubes-os/ [5] https://github.com/QubesOS/qubes-issues/issues/5367 [6] https://www.qubes-os.org/doc/installation-guide/#copying-the-iso-onto-the-installation-medium [7] https://www.qubes-os.org/doc/reporting-bugs/ This announcement is also available on the Qubes website: https://www.qubes-os.org/news/2020/01/15/qubes-4-0-3-rc1/ - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl4e/oMACgkQ203TvDlQ MDCqPw//ddfW08ObnL76ed87v0fkDLvViiC1S72udxlettb7pvhkIBv8emKE7YTR Sm4Wl9AkV+PumCNNofuHgoRJ0GPQBI0xrtICwLlNXAbFW9+1s7JeMxedGAtf8nsR nn02rCyh7Qj1Xn5N30e6COvnXRcTIhBPvoraCs85rA5wDTnM2wgXoILU7cu/vx9T jRdLbMGuD/trNRL0fhRpfion8Sv9leyWsVohgrly7NNKu8QiMST2bKL8UoVKp4AY hqI2VlALZ+4aPtyQu5CAzIErBPNGhF4k/1bjC0lHUei280cj9mTUM1kuHV41l6Wp g6FBKL/ECflJ9F/3l/HadhS1om4Xqss6SJH4Fk9bowJAM0A5UEVQkrs4aJId6gQL 1swAZL/HSN+QY0GQu54eSpgvjCT8OIcvuQ5Yhz7ojR5r34Dapo+uoWugI1U7nwHn lllzxH5mGUG/h7Cl00wiCUgwDHdQRczhEPiJEqmnRmqWksu2G++8Oiaccu0PBqz/ 7Mf8FV9janvbnuUry7C2IoIEFVmoyYHj6RHwT2Vxtjd2/6bsXOVC2Rs9l/HlE0hg 9rxXTIhcyzjH8ahpvUzp/IG7GizRblIe6fD5vFw/BxkCuCQyLOviPT5EgzZ+D9+C mPFAQa7oKbPoUjYgEvlzwGImMQ/0t1fGV5UqRWomiq16kzBzb74= =fh9z -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/289adab2-a0b9-1d27-b861-0aeab285e801%40qubes-os.org.
[qubes-users] Qubes Canary #22
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Qubes Community, We have published Qubes Canary #22. 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 Qubes Canary #22 in the qubes-secpack: https://github.com/QubesOS/qubes-secpack/blob/master/canaries/canary-022-2020.txt Learn about the qubes-secpack, including how to obtain, verify, and read it: https://www.qubes-os.org/security/pack/ View all past canaries: https://www.qubes-os.org/security/canaries/ ``` ---===[ Qubes Canary #22 ]===--- Statements - --- The Qubes core developers who have digitally signed this file [1] state the following: 1. The date of issue of this canary is January 13, 2020. 2. There have been 56 Qubes Security Bulletins published so far. 3. The Qubes Master Signing Key fingerprint is: 427F 11FD 0FAA 4B08 0123 F01C DDFA 1A3E 3687 9494 4. No warrants have ever been served to us with regard to the Qubes OS Project (e.g. to hand out the private signing keys or to introduce backdoors). 5. We plan to publish the next of these canary statements in the first two weeks of April 2020. Special note should be taken if no new canary is published by that time or if the list of statements changes without plausible explanation. Special announcements - -- None. Disclaimers and notes - -- We would like to remind you that Qubes OS has been designed under the assumption that all relevant infrastructure is permanently compromised. This means that we assume NO trust in any of the servers or services which host or provide any Qubes-related data, in particular, software updates, source code repositories, and Qubes ISO downloads. This canary scheme is not infallible. Although signing the declaration makes it very difficult for a third party to produce arbitrary declarations, it does not prevent them from using force or other means, like blackmail or compromising the signers' laptops, to coerce us to produce false declarations. The news feeds quoted below (Proof of freshness) serves to demonstrate that this canary could not have been created prior to the date stated. It shows that a series of canaries was not created in advance. This declaration is merely a best effort and is provided without any guarantee or warranty. It is not legally binding in any way to anybody. None of the signers should be ever held legally responsible for any of the statements made here. Proof of freshness - --- Mon, 13 Jan 2020 11:12:28 + Source: DER SPIEGEL - International (https://www.spiegel.de/international/index.rss) The U.S. Versus Iran: A Dangerous New Era in the Middle East Germany Plans to Repatriate Ebola Patients Can Nuclear Power Offer a Way Out of the Climate Crisis? Killing of Iran General Soleimani Akin to War Declaration Dissendent Describes 'Cultural Genocide' Against Uighurs Source: NYT > World News (https://rss.nytimes.com/services/xml/rss/nyt/World.xml) Seven Days in January: How Trump Pushed U.S. and Iran to the Brink of War Desperate Residents Ignore Dangers of Philippine Volcano and Return Home A New Home for French Socialists, on Paris’s Periphery A Growing U.S. Base Made This Afghan Town. Now It’s Dying. Iran Cracks Down as Protests Over Downing of Airliner Grow Source: BBC News - World (https://feeds.bbci.co.uk/news/world/rss.xml) Taal volcano: Lava spews as 'hazardous eruption' feared Iran plane downing: Canadian PM promises 'justice' at memorial Hevrin Khalaf: Death of a peacemaker Retired Pope Benedict warns Francis against relaxing priestly celibacy rules Egypt-Ethiopia row: The trouble over a giant Nile dam Source: Reuters: World News (http://feeds.reuters.com/reuters/worldnews) 'Oust Uncle': Thailand's jog for dissent signals new breed of activists Britain's royal showdown: queen hosts Meghan-Harry crisis talks Iran protesters take to the streets in third day of demos over plane Australian prime minister's approval rating goes up in flames Thai elephants march in silence for Australian bushfires Source: Blockchain.info 000444803ca23cffb65ea59fb0afef4065b2ea897a03e120 Footnotes - -- [1] This file should be signed in two ways: (1) via detached PGP signatures by each of the signers, distributed together with this canary in the qubes-secpack.git repo, and (2) via digital signatures on the corresponding qubes-secpack.git repo tags. [2] [2] Don't just trust the contents of this file blindly! Verify the digital signatures! ``` This announcement is also available on the Qubes website: https://www.qubes-os.org/news/2020/01/15/canary-22/ - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl4e9QYACgkQ203TvDlQ MDAG7hAAgbHQ9xMSJUiv/lrc0G4o+5guA1AYHP9vpOVDSIZna9l0YS26Ahv1rjgn go8DdIjkgB
