Re: [qubes-users] HCL-Medion-S6445_MD61489

2021-03-07 Thread Sven Semmler

On 3/7/21 9:51 AM, Lothar Zießau wrote:

Qubes could be installed on the HDD without probleme (I am
beginner 2 days).


Welcome to qubes-users and thank you for your HCL report submission!

In case you are not yet aware there is also a very active Qubes OS Forum 
here: https://qubes-os.discourse.group/


Your report is now a pull request to the website maintainer: 
https://github.com/QubesOS/qubes-hcl/pull/50


/Sven

--
 public key: https://www.svensemmler.org/0x8F541FB6.asc
fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6

--
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/20a9ed9f-ae63-e30a-1498-ca6c5ee4dd61%40SvenSemmler.org.


OpenPGP_signature
Description: OpenPGP digital signature


Re: [qubes-users] each dom0 update check redownload old template

2021-03-07 Thread evado...@gmail.com
I reinstalled the template and then removed it again. Looks like issue 
fixed now. Also I reboot the system and saw the message about converting 
database from qdb (or something like this) to sqlite after I run dom0 
update again.

-- 
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/1892159d-837c-4d9e-afcd-ecedc3976424n%40googlegroups.com.


[qubes-users] HCL-Medion-S6445_MD61489

2021-03-07 Thread Lothar Zießau

I have retrofitted a 1TB HDD to the Medion S6445 MSN30026588 because the
1TB SSD consists of 4 areas with control program and is not recognized
by Qubes. Qubes could be installed on the HDD without probleme (I am
beginner 2 days). The settings in UEFI described in DuckDuckGo had to be
changed. I now use Windows10 on the SSD and Qubes (for internet) on the
HDD. Since Qubes encrypts the HDD, WIN10 does not use it. Otherwise, all
components of the PC are recognized. Bluetooth works, but I don't use it
anymore. USB and Microsoft Mouse work fine. I did not test the webcam.
Autostart of the programs in the VM works.  I did not run the fedora-30
update because then the error ACPI BIOS Error (bug): Could not sesolve
symbol [^^^RP05.PEGP1], AE_NOT_FOUND (20190816/psargs-330) and ACPI
Error: Aborting method \_SB.PCI0.LPCB.EC0._QDF due to previous error
(AE_NOT_FOUND) (20190816/psparse-531) occurs.
Since Qubes is starting VM slowly I will extend the 8 GB RAM to 16 GB.

--
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/6b494938-c803-0e6a-2438-96f1311ca2ec%40gmx.de.


Qubes-HCL-MEDION-S6445_MD61489-20210307-135644.yml
Description: application/yaml


[qubes-users] Here is some graphical documentation - with commands - for the Qubes boot and decrypt process

2021-03-07 Thread Ranjeet Shetye
Hi,

I've graphically documented (with commands) the Qubes boot and decrypt
process to the best of my knowledge in QUBES-BOOTUP.svg @
https://github.com/rshetye/good-karma/

I had run into some problems while testing Qubes, and found the
documentation lacking (or my understanding lacking). So I documented it
myself for my better understanding and would like to share it with the
general Qubes community. Thanks for making Qubes such for a great product !

Regards,
Ranjeet

-- 
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/CALvHdtYm-d2nFP0nY0sinZ8b_h-jY9BrsWRKzwWGWuLMRKwf5g%40mail.gmail.com.


Re: [qubes-users] each dom0 update check redownload old template

2021-03-07 Thread Ludovic Bellier

Le 07/03/2021 à 11:45, evado...@gmail.com a écrit :


First command "no such domain" as result for first command. I tried 
with qubes- template-fedora-32 and with fedora-32. "no such domain"


sudo qubes-dom0-update still trying to upgrade qubes-template-fedora-32...


I searched for reverse dependency for this package with the help of the 
ArchLinux rosetta (https://wiki.archlinux.org/index.php/Pacman/Rosetta), 
but the `dnf repoquery --alldeps --whatrequires 
qubes-template-fedora-32` command don't give me the wanted result. I'm 
more fluent with debian than fedora... But I think this is the way to 
go, find the reverse dependency for this package.


--

Ludovic

--
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/f97998e9-0945-baca-a970-3c32460b5efb%40zyrianes.net.


Re: [qubes-users] maybe is root issue?

2021-03-07 Thread unman
On Sun, Mar 07, 2021 at 04:41:54AM -0800, unun wong wrote:
> hi ervery, 
> when I try to run qvm in dom0 terminal, command is not find, and I try to 
> creat new file in the /etc/NetworkManager/conf.d/ , access also denied. I 
> wonder is my user do not have the authority?
> 

There are *many* qvm- commands in dom0 - type qvm and then TAB to see
them.
The one you will use most often is qvm-run
To edit config files you will want to use `sudo` or`sudo su -` to get root.

-- 
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/20210307142746.GD14041%40thirdeyesecurity.org.


Re: [qubes-users] Re: [QubesOS/qubes-issues] Improve Clipboard Experience (#5778)

2021-03-07 Thread unman
On Sat, Mar 06, 2021 at 01:16:45AM +0100, donoban wrote:
> Well, since the issue was finally closed I will reply here.
> 
> On 3/6/21 1:39 AM, unman wrote:
> > I don't understand this example - if the destination is compromised, then
> > why would there be a need to modify the clipboard? They just capture the
> > data as is and exfiltrate it - you are hosed, and the Qubes clipboard is
> > the least of your problems.
> 
> At destination there is nothing useful to steal (at least not bitcoins)
> the bitcoin address is not useful for the attacker, it is a public
> address and private keys are in other uncompromised offline vm.
> 
> What the attacker tries to do is replace your address in the clipboard
> to other address (controlled by him), in the hope that you paste it to
> someone who wants to send funds for you.
> 
> I'm agree that the attacker could do a lot of additional things but many
> of them are more difficult, prone to fail, prone to cause detection. So
> I don't think it is a justification for not having a more secure
> clipboard and also easier to use which was the main objective.
> 

Again, I don't understand your example. You say, "At destination there is
nothing useful to steal", and then you exactly indicate what is useful
to steal, i.e the bitcoin address.

In any case, this is where we disagree.
Most of those "additional things" seem to me to be far easier to
implement, and have far wider application, than an attack on the Qubes
clipboard.
I haven't seen anything in the discussion on GitHub which would provide 
"a more secure clipboard", and which would be "easier to use". I think
what is needed are some concrete proposals, and perhaps poc -then
we'd actually have something to consider. Until I see that I'm bowing
out.

-- 
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/20210307141431.GA14041%40thirdeyesecurity.org.


[qubes-users] maybe is root issue?

2021-03-07 Thread unun wong
hi ervery, 
when I try to run qvm in dom0 terminal, command is not find, and I try to 
creat new file in the /etc/NetworkManager/conf.d/ , access also denied. I 
wonder is my user do not have the authority?

-- 
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/995340b9-2475-4a6d-8959-4a84084084ben%40googlegroups.com.


Re: [qubes-users] each dom0 update check redownload old template

2021-03-07 Thread evado...@gmail.com


> Is your template used by another AppVM? 
>
No,  it show as removed. 

[user dom0 ~]$ sudo dnf remove qubes-template-fedora-32 
No match for argument: qubes-template-fedora-32
Error: No packages marked for removal.


> suggests also `dnf remove`, but if it failed, suggest a [manual 
> uninstall](
> https://www.qubes-os.org/doc/vm-troubleshooting/#can-not-uninstall-a-vm--error-vm-installed-by-package-manager-template-vm-name).
>  
>
>

First command "no such domain" as result for first command. I tried with 
qubes- template-fedora-32 and with fedora-32. "no such domain"

sudo qubes-dom0-update still trying to upgrade qubes-template-fedora-32...


 

-- 
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/667c1c73-b97e-4735-a0e2-e0df7d50885dn%40googlegroups.com.


Re: [qubes-users] Re: Fullscreen Multiple Monitors not possible?

2021-03-07 Thread Vít Šesták 'v6ak'
Well, in order to use the back from my first post, don't use the actual
fullscreen.

Regards,
Vít Šesták 'v6ak'

-- 
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/CAOgcfy9ZWW_sieWYrqHz1zE%2B5LchwxjxaDtREN-t0di7W9f2sg%40mail.gmail.com.


Re: [qubes-users] Re: Fullscreen Multiple Monitors not possible?

2021-03-07 Thread Vít Šesták 'v6ak'
I have forgotten to send the mail to qubes-users…

On Sun, Mar 7, 2021, 08:43 Prof. Dr. Michael Schefczyk  wrote:

> Dear Vít Šesták,
>
>
>
> Thank you very much! Indeed, fullscreen is possible with and without the
> allow_fullscreen setting. Unfortunately, there seems to be no way out of
> the problem that this does work only in a single monitor mode (literally
> full monitor instead of full screen).
>
>
>
> Regards,
>
>
>
> Michael Schefczyk
>
>
>
> *Von:* Vít Šesták <>
> *Gesendet:* Sonntag, 7. März 2021 08:38
> *An:* Prof. Dr. Michael Schefczyk
>
> *Betreff:* Re: [qubes-users] Re: Fullscreen Multiple Monitors not
> possible?
>
>
>
> Taskbar: that's why I wrote this:
>
>
>
> > If needed, make the window always-on-top by Alt+Space and selecting
> Always on Top.
>
>
>
> BTW, you can enter fullscreen in a similar way, even without
> allow_fullscreen. And you can probably configure shortcuts…
>
>
>
> Regards,
>
> Vít Šesták 'v6ak'
>

-- 
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/CAOgcfy_YNP4h%3DoQXo%2BMxWDdUXefbutskbgG_kvUcxcOdezrvYA%40mail.gmail.com.