Re: [qubes-users] Where is qubes-dom0-update getting $releasevar from
On Mon, Dec 10, 2018 at 12:39:29AM +0100, Achim Patzner wrote: > Hi! > > I just noticed that I'm not getting anything from qubes-do0-current- > testing with the very helpful message "Failed to synchronize cache > for...". Taking a look at qubes-dom0-update -v showed me that the > r$releasevar component came out as "r25-5" instead of r4.0. > > I can get it to behave by adding --releasevar=4.0 to the command but I > would really know what has been messed up... > > > Achim If you're using fedora 29 as updateVM this is a known bug, and fix is in testing. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181210014200.ck5ciqxpew6phxvq%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Hardware Compatibility List
I'm new to Qubes, so I will preface this by saying that there may be something I'm missing. What struck me was how many systems lacked a specification for SLAT and TPM. If you want people to take you seriously, you need to know these things. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a6173911-b01b-4999-bfb4-708f57951134%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Setup NextCloud in Qubes
Hello pr0xy, On Sun, 25 Nov 2018 at 23:44, pr0xy wrote: > On 2018-11-25 13:35, 799 wrote: > [...] > > I was also interesting in sharing be specific files between AppVMs > > without the need to use qvm-copy. > > I am currently using a combination of sshfs and encfs or cryfs. This > > allows me to mount specific folders from one AppVM. This data is > > encrypted in the "Storage-"AppVM and can only be decrypted in the > > AppVM which mounts the data. > [...] > That Storage AppVM idea sounds quite interesting. I'll be interested to > take a look at those docs when it's ready. > I have uploaded the script here: https://github.com/one7two99/my-qubes/blob/master/docs/qubes-datastore.md I haven't add lots of documentation here, this is something that need's to be done. What the script does: It will setup a storage-template from which two AppVMs will be created: my-storage-datastore -> will store the data my-storage-access -> used to access the data (you can of course add more AppVMs, even when you need to do so manually and not via the script. but the script contains all commands) The idea is that you can encrypt the data within the storage AppVM with encfs or cryfs and decrypt it in the access AppVM. Therefor you can have multiple access VMs which use different subfolders in the datastore AppVM with different encryption keys. If you have any questions regarding this script do not hesitate to contact me. - O -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAJ3yz2v6uWevGkLKAZy5V7ugUtwovdB-s_a_0%3D1A%2BNfeNLwE%2BA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Where is qubes-dom0-update getting $releasevar from
Hi! I just noticed that I'm not getting anything from qubes-do0-current- testing with the very helpful message "Failed to synchronize cache for...". Taking a look at qubes-dom0-update -v showed me that the r$releasevar component came out as "r25-5" instead of r4.0. I can get it to behave by adding --releasevar=4.0 to the command but I would really know what has been messed up... Achim -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/360c5d31429237df199bb9b9e2a1e92a4132b279.camel%40noses.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [R4.0] CPU Freq Scaling, or "Why am I stuck at 2.1 Ghz?"
On Sun, 9 Dec 2018 17:13:54 + Mike Keehan wrote: >On Thu, 6 Dec 2018 15:54:17 -0800 (PST) >Eric Duncan wrote: > >> Finally received my new Thinkpad X1 Yoga 3rd gen. >> >> i7-8650U up to 4.2 Ghz Turbo >> >> How can I debug/check that my CPU governor/frequency is scaling >> correcting under Qubes R4? >> >> So far, the only thing I've found is xentop/xl top that lists the CPU >> - as a never-changing 2.1 Ghz. Maybe this isn't the best way to >> measure CPU freq under dom0? All other tools seemed to want to use >> xfce4 tools, which seemed to only be specific to that fedora VM - and >> not the xen host. >> >> /TL;DR >> >> >> I let Windows 10 register itself before wiping the disk and >> installing Qubes R4. Under Windows, Google Chrome benchmarked around >> 5300 pts with the online tool I was using. As a test, I also >> installed Arch Linux briefly to test Chrome performance, and it came >> in around 4500 pts. I chalk that up to not optimizing anything on >> the system - just a raw install and no tweaks. >> >> Now, under Qubes R4.0, I'm still noticing a lot of >> sluggishness/slowdowns just like my older Thinkpad Helix has always >> had under Qubes R3.2 (and one of the reasons why I waited for this >> quad core CPU to upgrade my Qubes install). I could never benchmark >> Chrome under that Helix dual-core low-powered device. >> >> I loaded up Chrome on a new debian-9 VM and... Almost the same >> extremely sluggish performance. Google Chrome can't even get >> partially through the benchmarks without timing out, much less finish >> them. >> >> I've tried assigning 4 and even 8 vcpus to try to max things out. >> >> I am wondering where to start to debug this. >> >> Is it a dom0 cpu scaling thing? >> >> Does Qubes impose some artificial throttling? >> >> Is it a lag in iGPU rendering through the DisplayVM? (this DisplayVM >> is a new concept to me, still trying to figure it out) >> >> I've spent about 3 days on this device with various other issues to >> get to this point (no S3 sleep yet, pixel-perfect scaling of the HDR >> 1440p 14" display, etc). I few duckduckgo searches hasn't turned >> anything up yet; so, i'll continue when I have some time. >> >> Thanks! >> -E >> > >Hi Eric, > >If your Chrome benchmarks involve 3D acceleration using the GPU, then >they won't work under Qubes. > >Each Qube VM renders it's windows in software, which is then copied to >dom0 for display on the Xwindow system. Only dom0 has access to the >GPU, and you are not supposed to run applications on dom0 for security >reasons. (And of course, dom0 has no internet connection anyway.) > >Mike. > Qubes is a "security oriended" OS. If you want to game, use a different physical system. Gaming by its very nature is best done NOT in a VM. Stuart -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181209141257.1656323c%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [R4.0] CPU Freq Scaling, or "Why am I stuck at 2.1 Ghz?"
On Thu, 6 Dec 2018 15:54:17 -0800 (PST) Eric Duncan wrote: > Finally received my new Thinkpad X1 Yoga 3rd gen. > > i7-8650U up to 4.2 Ghz Turbo > > How can I debug/check that my CPU governor/frequency is scaling > correcting under Qubes R4? > > So far, the only thing I've found is xentop/xl top that lists the CPU > - as a never-changing 2.1 Ghz. Maybe this isn't the best way to > measure CPU freq under dom0? All other tools seemed to want to use > xfce4 tools, which seemed to only be specific to that fedora VM - and > not the xen host. > > /TL;DR > > > I let Windows 10 register itself before wiping the disk and > installing Qubes R4. Under Windows, Google Chrome benchmarked around > 5300 pts with the online tool I was using. As a test, I also > installed Arch Linux briefly to test Chrome performance, and it came > in around 4500 pts. I chalk that up to not optimizing anything on > the system - just a raw install and no tweaks. > > Now, under Qubes R4.0, I'm still noticing a lot of > sluggishness/slowdowns just like my older Thinkpad Helix has always > had under Qubes R3.2 (and one of the reasons why I waited for this > quad core CPU to upgrade my Qubes install). I could never benchmark > Chrome under that Helix dual-core low-powered device. > > I loaded up Chrome on a new debian-9 VM and... Almost the same > extremely sluggish performance. Google Chrome can't even get > partially through the benchmarks without timing out, much less finish > them. > > I've tried assigning 4 and even 8 vcpus to try to max things out. > > I am wondering where to start to debug this. > > Is it a dom0 cpu scaling thing? > > Does Qubes impose some artificial throttling? > > Is it a lag in iGPU rendering through the DisplayVM? (this DisplayVM > is a new concept to me, still trying to figure it out) > > I've spent about 3 days on this device with various other issues to > get to this point (no S3 sleep yet, pixel-perfect scaling of the HDR > 1440p 14" display, etc). I few duckduckgo searches hasn't turned > anything up yet; so, i'll continue when I have some time. > > Thanks! > -E > Hi Eric, If your Chrome benchmarks involve 3D acceleration using the GPU, then they won't work under Qubes. Each Qube VM renders it's windows in software, which is then copied to dom0 for display on the Xwindow system. Only dom0 has access to the GPU, and you are not supposed to run applications on dom0 for security reasons. (And of course, dom0 has no internet connection anyway.) Mike. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181209171354.226b77a3.mike%40keehan.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes4.0 on gen3 X1 looses disk on resume from suspend
Hi, having the same ACPI error on a non Lenovo machine. I'm getting these errors on varying OS. Not just Qubes. Niav Daniel Moerner: > Hi Jon, > > This is very strange. Not very helpful for you, I just want to confirm that I > have run Qubes 4.0 on a gen 3 X1 without having ever run into this bug. The > ACPI errors are present on almost all these Lenovo machines and don't mean > anything. > > Daniel > -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ee92109e-0c90-18e2-82ed-3eec7ced397c%40web.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] Re: Qubes4.0 on gen3 X1 looses disk on resume from suspend
Hi Jon, This is very strange. Not very helpful for you, I just want to confirm that I have run Qubes 4.0 on a gen 3 X1 without having ever run into this bug. The ACPI errors are present on almost all these Lenovo machines and don't mean anything. Daniel -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/dbc171d4-6ca1-4318-9489-179109803e6d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Fwd: [qubes-users] unproven APT for Qubes 3.x
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 12/9/18 4:04 AM, Oleg Artemiev wrote: > -- Forwarded message - > From: Oleg Artemiev > Date: Sun, Dec 9, 2018 at 12:56 PM > Subject: Re: [qubes-users] unproven APT for Qubes 3.x > To: Alex > Cc: > > > In other words: please someone update Qubes 3.x FAQ . > Be the change you want to see in the documentation: https://www.qubes-os.org/doc/doc-guidelines/ > On Sun, Dec 9, 2018 at 12:54 PM Oleg Artemiev wrote: > >> I'm in progress of key revocation. I cannot be alive w/o terminal. >> >> On Sun, Dec 9, 2018 at 12:46 PM Alex wrote: >> >>> On 12/9/18 8:38 AM, Oleg Artemiev wrote: A friend of mine told me a story: She had unproven APT like when insecure hardware being in use. Sorry, my English is not well enough (proven upper intermediate). I will continue in Russian: --- quote - - Прикинь - словил апт в третьих кубиках - держи меня в курсе - ну ты же знаешь, что это было на unsupported hardware без usb filter --- quote - BCC: 0x90h может пора понять, что использование третих кубиков стало опасно после того как была опубликована работа по автоматизации их из ансибла (не упомянутая в Qubes 3 FAQ? Всегда найдуться любители отстрелить себе гениталии.. >>> From what I can gather from your story, it seems that you claim that >>> Qubes R3.x is to be considered insecure, as far as USB hardware is >>> concerned... >>> >>> I'm not sure about this, but the warning to update is implicit in the >>> fact that R4 is out and the last version is typically the best supported >>> one. >>> >>> -- >>> Alex >>> >> >> -- >> Bye.Olli. >> gpg --search-keys grey_olli , use key w/ fingerprint below: >> Key fingerprint = 9901 6808 768C 8B89 544C 9BE0 49F9 5A46 2B98 147E >> Blog keys (the blog is mostly in Russian): >> http://grey-olli.livejournal.com/tag/ >> - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlwM7PMACgkQ203TvDlQ MDBTYQ/8D2o7SqM+fTvRC1jKdfWXj5Rj45Y28SEl9Fdsy/hlc0YhVSPbbsa4pU3C qFO559aM6MOEk0wQ+sNHGUoG4hgu0z6Mf3IJPwEoAIRRXrA28xPL1hcPQYKvFq/P /TuuWOZvL7wKNG+DpAwVov+kVebgV+ZySTMpJFRZPURlei6ii4gW/chFo8zD5Jdv 8TbxDERX+0f0HxZttvrtZaZprJCemZBLpWWat50iPMvodwCfaag7Xh3wpSpFYZqN 60x5cLDaefPnOeRqAYzPkwB43bMbepf8JESJFQUwvg6v3TIhVg6yg+G8oVHGGxoF mLqeDMsxEfpBLcXO7WBePD4hRIuBl/Y/WJpb/AguR0Wz9+U33BbjM4Z8nOmjJVU5 /BpgSAqMncfpyJfgw+45kwawtfomE/csFgx6YSg1QSnXH2XDpPIWu2A4UkC6CXpe 0ytxUs7kbUMP/LYoRSpiDXJbE4h1Qz+tlvUw94EC5NCEglRcclQLEsWZxhK3rEFw rUszeUn56ecmwdaJ7jsfkcVYBGfeaC4oAHRI6gqC865artkaygS8LdNc7jmMecUa A7rRHVZ1+uu9SuNb4AZSljV5OxoDu8+/RRJmYMH261SkJx6aZ7QHnf90K3w4Fys5 GToCuR1EtvavH4SmoDsVyCfWKOjDKmVQduzrBk8I8vAt9vqaFYw= =RBr2 -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2a007834-d890-1520-8d48-04112526381e%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] bind-dirs qubes 4.0
On Saturday, 8 December 2018 07:22:59 UTC-5, unman wrote: > On Sat, Dec 08, 2018 at 01:12:08AM -0800, Roy Bernat wrote: > > On Friday, 7 December 2018 21:07:31 UTC-5, unman wrote: > > > On Fri, Dec 07, 2018 at 08:44:20AM -0800, Roy Bernat wrote: > > > > On Monday, 3 December 2018 19:07:56 UTC-5, unman wrote: > > > > > On Mon, Dec 03, 2018 at 07:03:47AM -0800, Roy Bernat wrote: > > > > > > On Monday, 3 December 2018 08:01:12 UTC-5, unman wrote: > > > > > > > On Sun, Dec 02, 2018 at 07:07:28AM -0800, Roy Bernat wrote: > > > > > > > > Hi > > > > > > > > > > > > > > > > > > > > > > > > I use this article to create bind-dirs > > > > > > > > > > > > > > > > i created this file 50_user.conf under > > > > > > > > /rw/config/qubes-bind-dirs.d > > > > > > > > > > > > > > > > with the following > > > > > > > > > > > > > > > > > > > > > > > > binds+=( '/var/lib/docker' ) > > > > > > > > binds+=( '/etc/docker' ) > > > > > > > > > > > > > > > > > > > > > > > > for testing i created a folder inside /var/lib/docker called > > > > > > > > test and after > > > > > > > > > > > > > > > > reboot the folder removed . > > > > > > > > > > > > > > > > what is the mistake ? > > > > > > > > > > > > > > > > 10x all > > > > > > > > Roy > > > > > > > > > > > > > > > > > > > > > > No mistake - you need to reboot and then create the folder. > > > > > > > If you look in the "How does it work?" section, you'll see this > > > > > > > explained. > > > > > > > > > > > > in the templateVM ? or in machine i created ? > > > > > > > > > > > > > > > > bind-dirs is used in TemplateBasedVMs to make files/folders that would > > > > > otherwise come from the template specific to that qube. > > > > > So if you put that conf file in the qube, restart it and then make > > > > > changes in /var/lib/docker, and you will see that the changes remain > > > > > after rebooting the qube. > > > > Thank you for your answer . > > > > > > > > how can i make persistent in the appvm ? > > > > > > > > for example i created a appvm for docker . > > > > > > > > i am downloading images and after reboot the images are not exist > > > > because > > > > > > > > it saved in the /var/lib/docker > > > > > > > > > > > > Thanks > > > > > > Create that file in the appvm as you have described. > > > Reboot the appVM. > > > That will make /var/lib/docker persistent in the appVM > > > (Test this by inspecting /rw/bind-dirs and confirming that > > > var/lib/docker is there.) > > > THEN download images and store them in /var/lib/docker. > > > Reboot appVM. > > > Confirm that images still exist in /var/lib/docker after restart. > > > > > > not working > > > > i checked again in the template vm > > > > 50_user.conf > > > > binds+=( '/var/lib/docker' ) > > > > in the template vm it is working as you said > > > > in the appvm it is not working and i cant see the folder > > > > in /rw/bind-dirs > > > > thank you foryou help > > > > Why are you doing this in the template vm? There is nothing in the > documentation to suggest that you should put the files in the template. > > bind-dirs is intended to run in templatebasedVMs to make files that > would otherwise disappear on reboot (because they are derived from the > template) be permanent. It makes no sense to set it in the template - > those files will automatically be permanent across reboots in the > appVM. Remove the nind-dirs files from the template, and set them up in > the apppVM. > > Please check that you have followed the instructions exactly and set > configuration in the appVM. > > unman working :) 10x -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8533399b-86a0-45b3-986d-9b67724872cd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Fwd: [qubes-users] unproven APT for Qubes 3.x
-- Forwarded message - From: Oleg Artemiev Date: Sun, Dec 9, 2018 at 12:56 PM Subject: Re: [qubes-users] unproven APT for Qubes 3.x To: Alex Cc: In other words: please someone update Qubes 3.x FAQ . On Sun, Dec 9, 2018 at 12:54 PM Oleg Artemiev wrote: > I'm in progress of key revocation. I cannot be alive w/o terminal. > > On Sun, Dec 9, 2018 at 12:46 PM Alex wrote: > >> On 12/9/18 8:38 AM, Oleg Artemiev wrote: >> > A friend of mine told me a story: >> > >> > She had unproven APT like when insecure hardware being in use. >> > >> > Sorry, my English is not well enough (proven upper intermediate). >> > I will continue in Russian: >> > --- quote - >> > - Прикинь - словил апт в третьих кубиках >> > - держи меня в курсе >> > - ну ты же знаешь, что это было на unsupported hardware без usb filter >> > --- quote - >> > >> > BCC: 0x90h >> > >> > может пора понять, что использование третих кубиков стало опасно после >> > того как была опубликована работа по автоматизации их из ансибла (не >> > упомянутая в Qubes 3 FAQ? Всегда найдуться любители отстрелить себе >> > гениталии.. >> From what I can gather from your story, it seems that you claim that >> Qubes R3.x is to be considered insecure, as far as USB hardware is >> concerned... >> >> I'm not sure about this, but the warning to update is implicit in the >> fact that R4 is out and the last version is typically the best supported >> one. >> >> -- >> Alex >> >> -- >> 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 post to this group, send email to qubes-users@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/qubes-users/a0c2db52-25ea-3881-ea9e-b41b87eb6d24%40gmx.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Bye.Olli. > gpg --search-keys grey_olli , use key w/ fingerprint below: > Key fingerprint = 9901 6808 768C 8B89 544C 9BE0 49F9 5A46 2B98 147E > Blog keys (the blog is mostly in Russian): > http://grey-olli.livejournal.com/tag/ > -- Bye.Olli. gpg --search-keys grey_olli , use key w/ fingerprint below: Key fingerprint = 9901 6808 768C 8B89 544C 9BE0 49F9 5A46 2B98 147E Blog keys (the blog is mostly in Russian): http://grey-olli.livejournal.com/tag/ -- Bye.Olli. gpg --search-keys grey_olli , use key w/ fingerprint below: Key fingerprint = 9901 6808 768C 8B89 544C 9BE0 49F9 5A46 2B98 147E Blog keys (the blog is mostly in Russian): http://grey-olli.livejournal.com/tag/ Please take care. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CABunX6PxbsieXkyn50WP-sz0KTJfguZNkvnf0qstfBw8NzPkFA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] unproven APT for Qubes 3.x
On Sun, Dec 9, 2018 at 12:46 PM Alex wrote: > On 12/9/18 8:38 AM, Oleg Artemiev wrote: > > A friend of mine told me a story: > > > > She had unproven APT like when insecure hardware being in use. > > > > Sorry, my English is not well enough (proven upper intermediate). > > I will continue in Russian: > > --- quote - > > - Прикинь - словил апт в третьих кубиках > > - держи меня в курсе > > - ну ты же знаешь, что это было на unsupported hardware без usb filter > > --- quote - > > > > BCC: 0x90h > > > > может пора понять, что использование третих кубиков стало опасно после > > того как была опубликована работа по автоматизации их из ансибла (не > > упомянутая в Qubes 3 FAQ? Всегда найдуться любители отстрелить себе > > гениталии.. > From what I can gather from your story, it seems that you claim that > Qubes R3.x is to be considered insecure, as far as USB hardware is > concerned... > > I'm not sure about this, but the warning to update is implicit in the > fact that R4 is out and the last version is typically the best supported > one. > > -- > Alex > > -- > 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 post to this group, send email to qubes-users@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/a0c2db52-25ea-3881-ea9e-b41b87eb6d24%40gmx.com > . > For more options, visit https://groups.google.com/d/optout. > квота для Шнайера: ---cut--- Oleg Artemiev 11:22 AM (1 hour ago) my key is potentially stolen ) It is NOT actually. I'll send you email. Happy new year. Я брал автограф у Вас на Positive Hack Days. Книга к сожалению утеряна ---cut--- -- Bye.Olli. gpg --search-keys grey_olli , use key w/ fingerprint below: Key fingerprint = 9901 6808 768C 8B89 544C 9BE0 49F9 5A46 2B98 147E Blog keys (the blog is mostly in Russian): http://grey-olli.livejournal.com/tag/ -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CABunX6OVhTXpXCdfNgYQkNa-0bfYpJrtH3icuciwbN%3DBnR5tcA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] unproven APT for Qubes 3.x
In other words: please someone update Qubes 3.x FAQ . On Sun, Dec 9, 2018 at 12:54 PM Oleg Artemiev wrote: > I'm in progress of key revocation. I cannot be alive w/o terminal. > > On Sun, Dec 9, 2018 at 12:46 PM Alex wrote: > >> On 12/9/18 8:38 AM, Oleg Artemiev wrote: >> > A friend of mine told me a story: >> > >> > She had unproven APT like when insecure hardware being in use. >> > >> > Sorry, my English is not well enough (proven upper intermediate). >> > I will continue in Russian: >> > --- quote - >> > - Прикинь - словил апт в третьих кубиках >> > - держи меня в курсе >> > - ну ты же знаешь, что это было на unsupported hardware без usb filter >> > --- quote - >> > >> > BCC: 0x90h >> > >> > может пора понять, что использование третих кубиков стало опасно после >> > того как была опубликована работа по автоматизации их из ансибла (не >> > упомянутая в Qubes 3 FAQ? Всегда найдуться любители отстрелить себе >> > гениталии.. >> From what I can gather from your story, it seems that you claim that >> Qubes R3.x is to be considered insecure, as far as USB hardware is >> concerned... >> >> I'm not sure about this, but the warning to update is implicit in the >> fact that R4 is out and the last version is typically the best supported >> one. >> >> -- >> Alex >> >> -- >> 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 post to this group, send email to qubes-users@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/qubes-users/a0c2db52-25ea-3881-ea9e-b41b87eb6d24%40gmx.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Bye.Olli. > gpg --search-keys grey_olli , use key w/ fingerprint below: > Key fingerprint = 9901 6808 768C 8B89 544C 9BE0 49F9 5A46 2B98 147E > Blog keys (the blog is mostly in Russian): > http://grey-olli.livejournal.com/tag/ > -- Bye.Olli. gpg --search-keys grey_olli , use key w/ fingerprint below: Key fingerprint = 9901 6808 768C 8B89 544C 9BE0 49F9 5A46 2B98 147E Blog keys (the blog is mostly in Russian): http://grey-olli.livejournal.com/tag/ -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CABunX6OWz%3DTeUMYa7eF0pkQBJXA6HotJohk%2BoWis1cRYx2YFxw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] unproven APT for Qubes 3.x
I'm in progress of key revocation. I cannot be alive w/o terminal. On Sun, Dec 9, 2018 at 12:46 PM Alex wrote: > On 12/9/18 8:38 AM, Oleg Artemiev wrote: > > A friend of mine told me a story: > > > > She had unproven APT like when insecure hardware being in use. > > > > Sorry, my English is not well enough (proven upper intermediate). > > I will continue in Russian: > > --- quote - > > - Прикинь - словил апт в третьих кубиках > > - держи меня в курсе > > - ну ты же знаешь, что это было на unsupported hardware без usb filter > > --- quote - > > > > BCC: 0x90h > > > > может пора понять, что использование третих кубиков стало опасно после > > того как была опубликована работа по автоматизации их из ансибла (не > > упомянутая в Qubes 3 FAQ? Всегда найдуться любители отстрелить себе > > гениталии.. > From what I can gather from your story, it seems that you claim that > Qubes R3.x is to be considered insecure, as far as USB hardware is > concerned... > > I'm not sure about this, but the warning to update is implicit in the > fact that R4 is out and the last version is typically the best supported > one. > > -- > Alex > > -- > 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 post to this group, send email to qubes-users@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/a0c2db52-25ea-3881-ea9e-b41b87eb6d24%40gmx.com > . > For more options, visit https://groups.google.com/d/optout. > -- Bye.Olli. gpg --search-keys grey_olli , use key w/ fingerprint below: Key fingerprint = 9901 6808 768C 8B89 544C 9BE0 49F9 5A46 2B98 147E Blog keys (the blog is mostly in Russian): http://grey-olli.livejournal.com/tag/ -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CABunX6O7aH_rQXA-q_qXKZExQx3bDVE_fG1z%2BBJe%3DcTgPnF9Lg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] unproven APT for Qubes 3.x
On 12/9/18 8:38 AM, Oleg Artemiev wrote: > A friend of mine told me a story: > > She had unproven APT like when insecure hardware being in use. > > Sorry, my English is not well enough (proven upper intermediate). > I will continue in Russian: > --- quote - > - Прикинь - словил апт в третьих кубиках > - держи меня в курсе > - ну ты же знаешь, что это было на unsupported hardware без usb filter > --- quote - > > BCC: 0x90h > > может пора понять, что использование третих кубиков стало опасно после > того как была опубликована работа по автоматизации их из ансибла (не > упомянутая в Qubes 3 FAQ? Всегда найдуться любители отстрелить себе > гениталии.. From what I can gather from your story, it seems that you claim that Qubes R3.x is to be considered insecure, as far as USB hardware is concerned... I'm not sure about this, but the warning to update is implicit in the fact that R4 is out and the last version is typically the best supported one. -- Alex -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a0c2db52-25ea-3881-ea9e-b41b87eb6d24%40gmx.com. For more options, visit https://groups.google.com/d/optout.
