[qubes-users] Re: Qubes Os4 very slowly comparing to Qubes 3.2

2018-04-30 Thread frkla1234
That could be a good idea John! 

I have only one problem. I can not disable Speedstep in the Bios- Uefi because 
there is no Speedstep configuration. 

Does anyone know how to disable speedstep outside of the Bios at qubes os? I 
didn't find any solution.

-- 
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/103785cc-fe6f-4aa5-a1a1-ae61ee96e979%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Qubes Os4 very slowly comparing to Qubes 3.2

2018-04-23 Thread frkla1234
Hi!

To start qubes os 4 takes a very long time comparing to Qubes os 3.2 (The 
double time or more) Is that normal? Also to start a new qube takes a lot of 
time. I realised also that the different qubes need more ram than before. 

Is this only a behavior of my computer or is this in general? 

I have an asus notebook i7 6500 u processor with 8gb ram and ssd

Thanks for the answers!

-- 
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/03adbeef-1890-4c37-8f4a-5264b952b9d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] User issues with Qubes 4.0

2018-04-07 Thread frkla1234
Yes it seems to be the same problem!

I tried also with debian 9. The same problem.

During watching Youtube Videos with 720p it's jerkying. 

For the moment I'm watching at 480p and I'm trying not moving the cursor. Than 
it's not jerkying a lot.



-- 
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/2b058e5c-7261-4d63-9000-68ffb653b0b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] User issues with Qubes 4.0

2018-04-05 Thread frkla1234
Hey guys,

I have also some of your problems. I have an Asus notebook i7 6500 U, 8GB ram, 
SSD Qubes os 4 is much slower than qubes os 3.2. 

I noticed also that the Qubes Manager has problems with refreshing. 

The biggest problem which I have at the moment are graphical issues. When I 
watch a video and I move with the cursor the video jerkys. If it is a fast 
Video (for example a car video) it jerkys also whitout moving the cursor. I 
didn't have this problem at os 3.2 - even when I was playing videos 
simultaneously.

I looked at the qubes os homepage for a solution:

https://www.qubes-os.org/doc/intel-igfx-troubleshooting/

The solution would be to add a line (iommu=no-igfx) to the 
/boot/efi/EFI/qubes/xen.cfg .

This line (iommu=no-igfx) was already in the .cfg file, so I had nothing to add.

Maybe someone has an other solution - feel free to help :-)


I'm still a big fan of qubes os and I'm thanksful for this os! 

I hope the issues will be fixed

Regards,

Mat


 

-- 
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/3b21be54-3815-4c0c-89a1-0f7fe0a84474%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] wifi problems- trying to install rtlwifi_new driver

2017-10-13 Thread frkla1234
Hi guys,

before qubes os I had ubuntu 17.04 and I had wifi problems until I installed 
the driver "rtlwifi_new" on github (https://github.com/lwfinger/rtlwifi_new). 
After the installation it worked.

With fedora 24 I didn`t have problems with the internet connection but with the 
netvm, which runs now at fedora 25, I have the same problems like I had on 
ubuntu. So I decided to download the "rtlwifi_new" at the fedora template 25. 
Than I copied to the netvm. 

I don`t know to install that driver and I need your 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 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/34675b26-d2af-4546-902e-c3e1b4085a4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] During upgrading to fedora 25 I saw some warnings

2017-08-10 Thread frkla1234
Hi everyone!

During the upgrading from fedora 24 to 25 I had some warings.

1) The terminal said:

Warning link /etc/pki/ca-trust/extracted/javacacerts where file 
/usr/lib/jvm/java-1.8.0-opendjdk-1.8.0.141-1.b16fc24.x86_64/jre/lib/security/cacertsexpected!

Is there anything to be worried?

2) The second it`s a little bit weird:
Udisks2.service changed on disk. Run 'systemctl daemon-reload' to reload units

Is that a sign that my system was compromised?

-- 
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/ff95066e-5289-4499-b6cd-2446e3d7aabd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Problems with the command sudo dnf remove qubes-template-fedora-24/ 23

2017-08-10 Thread frkla1234
Hi!

I typed into the dom0 terminal:

sudo dnf remove qubes-template-fedora-24

and it doesn`t worked. 

I have the same problem for the template 23.

Does anyone knows what could be 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 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/9406ef2e-aa27-4445-b3f0-f08e407bf6d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Upgrading fedora 23 to 25 Problem

2017-08-10 Thread frkla1234
Hi!

Thx for the answer!

I already installed fedora 24 and I upgraded than to 25. It worked :-)

But your way sounds more efficient ;-)

-- 
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/8e79db67-25d7-4898-a736-9a096eeb029b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Upgrading fedora 23 to 25 Problem

2017-08-10 Thread frkla1234
I checked now the folder where the key should be. I have only 
"RPM-GPG-KEY-fedora-24-x86_64" and not that one for fedora 25. Maybe this 
causes the problem. So I try now to install first the fedora 24 version and 
than the upgrade at 25.

-- 
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/2634b84b-5d26-4d66-80a7-750cf8d76715%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Upgrading fedora 23 to 25 Problem

2017-08-10 Thread frkla1234
Hi,

i installed now Qubes Os 3.2 and I began to upgrade now to fedora 25. I 
followed the steps at the qubes os homepage ( 
https://www.qubes-os.org/doc/template/fedora/upgrade-24-to-25/ ).

At step 3 I became following message after downloading the packages:

Total 1.3 GB
warning: 
/var/cache/dnf/fedora-310.../packages/python2-pygpgme-0.3-18.fc25.x86_64.rpm: 
Header V3 RSA/SHA256 Signature, key ID fdb19c98:NOKEY
Curl error (37): Couldn't read a file:// file for 
file:///etc/pki/rpm-gpg/RPM-GPG-Key-fedora-25-x86_64 [Couldn't open file 
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64]
The download packages were saved in cache until the next succesful transaction.
You can remove chached packages by executing 'dnf clean packages'

I don't know how to continue. This warning is not at the qubes homepage 
explained.

I`m not good in computer things and my English is not the best one, so please 
write clear :-)

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 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/8b96dd6b-92db-46ac-a076-fbbfbdfb58db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Verifying does not work with gpg

2017-08-03 Thread frkla1234
Hi Unman,

you are right! 

I tried the signing key against the .iso

I copied now the signature into 'gedit' and saved it as 
"Qubes-R3.2-x86_64.iso.asc"

After I verifyed the signature 'Qubes-R3.2-x86_64.iso.asc' against 
'Qubes-R3.2-x86_64.iso'
and it worked :-))

Thx a lot for your patient!

-- 
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/6d9baa62-70c5-4560-91f8-27185f68ea3f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Verifying does not work with gpg

2017-08-03 Thread frkla1234
Hi unman,

thx for the response!

I will do each step slowly and poste each problem separate ;-)

Let`s begin with the first step:


1. Download the "qubes-release-3-signing-key.asc" (PGP Key) from 
https://www.qubes-os.org/downloads/ and save in the directory Downloads where 
qubes .iso is

2. Command in terminal [Downloads]:
gpg -v --verify '/home/user/Downloads/qubes-release-3-signing-key.asc' 
'/home/user/Downloads/Qubes-R3.2-x86_64.iso'

Answer from terminal:
gpg: armor header: Version: GnuPG v1
gpg: verify signatures failed: unexpected data

3. Check permission of "qubes-release-3-signing-key.asc"

Owner: Me
Access: read and write

Group: user
Access: read and write

Others: 
Access: read- only

What else should I check?





-- 
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/09ddf071-9f3c-4a98-ac31-32737260ee32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Verifying does not work with gpg

2017-08-03 Thread frkla1234
On Wednesday, August 2, 2017 at 11:24:35 PM UTC+2, Unman wrote:
> On Wed, Aug 02, 2017 at 01:40:23PM -0700, frkla1...@gmail.com wrote:
> > Hey guys I installed the Qubes-Os and I`m very happy with it :-) The best 
> > OS in my opinion- everything it`s working fine on my computer. Thanks for 
> > the project!!
> > 
> > But I installed without verifying anything. So since two weeks I try to 
> > check the .iso file because I wanna reinstall Qubes-OS with the verified 
> > .iso. 
> > 
> > Sorry for my English- it`s not the best and I`m also a noob with informatic 
> > things. So please write simple.
> > 
> > 1. I downloaded the  Qubes Master Signing Key with:
> > 
> > $ gpg --fetch-keys 
> > https://keys.qubes-os.org/keys/qubes-master-signing-key.asc
> > 
> > 2. I checked the fingerprint with:
> > 
> > gpg --fingerprint
> > 
> > 3. I decided to trust the qubes-master-signing-key
> > 
> > 3.1 $ gpg --edit-key 36879494 (at the qubes-os site it`s written 0x36879494 
> > - i don`t understand why to put "0x" in front of the 
> > qubes-master-signing-key. So i let it away- it worked)
> > 
> > i made all the steps and it worked- i had the same terminal output as in 
> > the description (https://www.qubes-os.org/security/verifying-signatures/)
> > 
> > 4. After that I downloaded the "qubes-release-3-signing-key.asc" because I 
> > would like to install Qubes-R3.2-x86_64.iso.
> > 
> > - I tried a lot of things.
> > 1) Download it from the download page with right click and than "Save File"
> > 2) Download with gpg --recv-keys 0xCB11CA1D03FA5082 (number on the 
> > qubes-os.org page)
> > ...
> > 
> > PROBLEM I can't verify the iso image.
> > 
> > 1) I tried with gpg -v --verify Qubes-R3.2-x86_64.iso.asc 
> > Qubes-R3.2-x86_64.iso
> > Answer from the terminal:
> > 
> > gpg: can't open 'Qubes-R3.2-x86_64.iso.asc'
> > gpg: verify signatures failed: file open error
> > 
> > 2) Than I decided to put the files inside with drag&drop.
> > Answer from the terminal:
> > gpg: armor header: Version: GnuPG v1
> > gpg: verify signatures failed: unexpected data
> > 
> > SO I DECIDED to check the DIGESTS but it does not work:
> > 
> > I put into the terminal: $ md5sum -c 
> > '/home/user/Downloads/Qubes/-R3.2-x86_64.iso'
> > Answer from terminal: no properly formatted MD5 checksum lines found
> > 
> > I tried also $ md5sum -c 
> > '/home/user/Downloads/Qubes/-R3.2-x86_64.iso.DIGESTS'
> > Answer from terminal: no such file or directory
> > 
> > I renamed than the .iso in iso.DIGESTS
> > Answer from the terminal: no properly formatted MD5 checksum lines found
> > 
> > I renamed than the .iso.DIGESTS again in .iso and I wrote into the terminal:
> > md5sum -t '/home/user/Downloads/Qubes/-R3.2-x86_64.iso' 
> > 
> > After writing the 't' instead of 'c' I received following answer:
> > 3c951138b8b9867d8657f173c1b58b82 /home/user/Downloads/Qubes/-R3.2-x86_64.iso
> > 
> > I did this for all types (md5sum sha1sum sha256sum sha512sum)
> > 
> > After that I compared with the openssl dgst types and it worked perfect.
> > 
> > But in the file on the website from qubes os is written: 
> > 
> > `However, it is possible that an attacker replaced Qubes-R3.2-x86_64.iso 
> > with a malicious ISO, computed the hash values for that ISO, and replaced 
> > the values in Qubes-R3.2-x86_64.iso.DIGESTS with his own set of values. 
> > Therefore, ideally, we should also verify the authenticity of the listed 
> > hash values. Since Qubes-R3.2-x86_64.iso.DIGESTS is a clearsigned PGP file, 
> > we can use gpg to verify it from the command line:`
> > 
> > I decided to check now the last step:
> > 
> > $ gpg -v --verify '/home/user/Downloads/Qubes/-R3.2-x86_64.iso'
> > Answer from the terminal: 
> > gpg: no valid OpenPGP data found.
> > gpg: the signature could not be verified
> > Please remember that the signature file (sig. or asc.) 
> > should be the first file given on the command line.
> > 
> > I tried the same step with the renamed the file .iso.DIGESTS
> > 
> > $ gpg -v --verify '/home/user/Downloads/Qubes/-R3.2-x86_64.iso.DISGESTS'
> > 
> > The answer was the same: 
> > gpg: no valid OpenPGP data found.
> > gpg: the signature could not be verified
> > Please remember that the signature file (sig. or asc.) 
> > should be the first file given on the command line.
> > 
> > The terminal suggest to compare the files like I described above:
> > 
> > But that command does not work in my terminal:
> > 
> > gpg -v --verify Qubes-R3.2-x86_64.iso.asc Qubes-R3.2-x86_64.iso
> > Answer: 
> > 
> > gpg: armor header: Version: GnuPG v1
> > gpg: verify signatures failed: unexpected data
> > 
> > I tried now all the options and I have no Idea what I should try to solve 
> > the verification problem. That's why I need help.
> > 
> > I checked the ~/.gnupg (Maybe it's helpful for you)
> > Supported algorithms:
> > Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
> > Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA 
> > 128, CAMELLIA192, CAMELLIA256
> > Hash: MD5, 

[qubes-users] Verifying does not work with gpg

2017-08-02 Thread frkla1234
Hey guys I installed the Qubes-Os and I`m very happy with it :-) The best OS in 
my opinion- everything it`s working fine on my computer. Thanks for the 
project!!

But I installed without verifying anything. So since two weeks I try to check 
the .iso file because I wanna reinstall Qubes-OS with the verified .iso. 

Sorry for my English- it`s not the best and I`m also a noob with informatic 
things. So please write simple.

1. I downloaded the  Qubes Master Signing Key with:

$ gpg --fetch-keys https://keys.qubes-os.org/keys/qubes-master-signing-key.asc

2. I checked the fingerprint with:

gpg --fingerprint

3. I decided to trust the qubes-master-signing-key

3.1 $ gpg --edit-key 36879494 (at the qubes-os site it`s written 0x36879494 - i 
don`t understand why to put "0x" in front of the qubes-master-signing-key. So i 
let it away- it worked)

i made all the steps and it worked- i had the same terminal output as in the 
description (https://www.qubes-os.org/security/verifying-signatures/)

4. After that I downloaded the "qubes-release-3-signing-key.asc" because I 
would like to install Qubes-R3.2-x86_64.iso.

- I tried a lot of things.
1) Download it from the download page with right click and than "Save File"
2) Download with gpg --recv-keys 0xCB11CA1D03FA5082 (number on the qubes-os.org 
page)
...

PROBLEM I can't verify the iso image.

1) I tried with gpg -v --verify Qubes-R3.2-x86_64.iso.asc Qubes-R3.2-x86_64.iso
Answer from the terminal:

gpg: can't open 'Qubes-R3.2-x86_64.iso.asc'
gpg: verify signatures failed: file open error

2) Than I decided to put the files inside with drag&drop.
Answer from the terminal:
gpg: armor header: Version: GnuPG v1
gpg: verify signatures failed: unexpected data

SO I DECIDED to check the DIGESTS but it does not work:

I put into the terminal: $ md5sum -c 
'/home/user/Downloads/Qubes/-R3.2-x86_64.iso'
Answer from terminal: no properly formatted MD5 checksum lines found

I tried also $ md5sum -c '/home/user/Downloads/Qubes/-R3.2-x86_64.iso.DIGESTS'
Answer from terminal: no such file or directory

I renamed than the .iso in iso.DIGESTS
Answer from the terminal: no properly formatted MD5 checksum lines found

I renamed than the .iso.DIGESTS again in .iso and I wrote into the terminal:
md5sum -t '/home/user/Downloads/Qubes/-R3.2-x86_64.iso' 

After writing the 't' instead of 'c' I received following answer:
3c951138b8b9867d8657f173c1b58b82 /home/user/Downloads/Qubes/-R3.2-x86_64.iso

I did this for all types (md5sum sha1sum sha256sum sha512sum)

After that I compared with the openssl dgst types and it worked perfect.

But in the file on the website from qubes os is written: 

`However, it is possible that an attacker replaced Qubes-R3.2-x86_64.iso with a 
malicious ISO, computed the hash values for that ISO, and replaced the values 
in Qubes-R3.2-x86_64.iso.DIGESTS with his own set of values. Therefore, 
ideally, we should also verify the authenticity of the listed hash values. 
Since Qubes-R3.2-x86_64.iso.DIGESTS is a clearsigned PGP file, we can use gpg 
to verify it from the command line:`

I decided to check now the last step:

$ gpg -v --verify '/home/user/Downloads/Qubes/-R3.2-x86_64.iso'
Answer from the terminal: 
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified
Please remember that the signature file (sig. or asc.) 
should be the first file given on the command line.

I tried the same step with the renamed the file .iso.DIGESTS

$ gpg -v --verify '/home/user/Downloads/Qubes/-R3.2-x86_64.iso.DISGESTS'

The answer was the same: 
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified
Please remember that the signature file (sig. or asc.) 
should be the first file given on the command line.

The terminal suggest to compare the files like I described above:

But that command does not work in my terminal:

gpg -v --verify Qubes-R3.2-x86_64.iso.asc Qubes-R3.2-x86_64.iso
Answer: 

gpg: armor header: Version: GnuPG v1
gpg: verify signatures failed: unexpected data

I tried now all the options and I have no Idea what I should try to solve the 
verification problem. That's why I need help.

I checked the ~/.gnupg (Maybe it's helpful for you)
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA 
128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPMED160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

Syntax: gpg [options] [files]
Sign, check, encrypt or decrypt
Default operation depends on the input data

I WOULD BE VERY HAPPY IF SOMEONE HAS A SOLUTION!

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 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