[qubes-users] Trouble updating templates

2018-03-03 Thread sevas 
I cant seem to update my templates. 

In the debian-9 TVM I type:

sudo apt-get update
Ign:1 http://.
Ign:2 http://.
Ign:3 http://.
Err:4
Err:5
Err:6 Connection Failed

E: The repo "http://...; does no longer have a Release File.
N: Updating from such a repo cant be done securely, and is therefore disabled 
by default.
N: See apt-secure man page.

The Fedora template doesnt seem to connect at all. 

My sys-firewall is using the debian-9 template.
Type: AppVM
Rules: Allow all outgoing
Devices: none
services: n/a

The sys-net (debian-9)
Type: AppVM
Rules: n/a
Devices: Network Controller
services: clocksync

-- 
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/6aca20f4-1a95-496a-8959-9fa8cbb1e616%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Building Centos template conflict error?

2018-03-03 Thread Tim W 
On Sunday, March 4, 2018 at 12:45:21 AM UTC-5, Tim W wrote:
> On Friday, March 2, 2018 at 10:14:51 PM UTC-5, Tim W wrote:
> > On Friday, March 2, 2018 at 4:05:30 AM UTC-5, Unman wrote:
> > > On Fri, Mar 02, 2018 at 12:41:29AM -0800, Tim W wrote:
> > > > On Tuesday, February 27, 2018 at 2:37:46 AM UTC-5, Frédéric Pierret 
> > > > (fepitre) wrote:
> > > > > Le mardi 27 février 2018 00:30:10 UTC+1, Tim W a écrit :
> > > > > > Great that was failing basically on all non standard templates i.e. 
> > > > > > not fedora, debain, or whonix.   They would all fail but it seems 
> > > > > > each had issues ubuntu, centos, arch.  Seems they are each getting 
> > > > > > fixed for 3.2 and getting updated for 4.0 now.  I was just testing 
> > > > > > to ensure things were still working for building as I know many 
> > > > > > prefer to build their own iso and templates vs binary.  I am one.  
> > > > > > Figured if docs had to be updated I would do that but it seems at 
> > > > > > most just a tweak or two in docs is all thats needed.
> > > > > 
> > > > > Indeed, it was just an adjustment with respect to the rpm spec of the 
> > > > > conflicting package. CentOS is shipping a file in their own dconf but 
> > > > > not Fedora. Recently a file /etc/dconf/profile/user has been used and 
> > > > > provided by Qubes and that is why there was a recent conflict. The 
> > > > > template for R4.0 is on the road! I finished last week to do all the 
> > > > > necessary and Marek is currently implementing it.
> > > > >  
> > > > > > Thanks again for you and Marek getting it working
> > > > > 
> > > > > You're welcome.
> > > >  
> > > > Just tried to build the standard template only under 3.2 and got this 
> > > > conflict
> > > > 
> > > > Transaction check error:
> > > >   file /etc/dconf/profile/user from install of 
> > > > qubes-core-vm-3.2.25-1.el7.centos.x86_64 conflicts with file from 
> > > > package dconf-0.26.0-2.el7.x86_64
> > > > 
> > > > It fails on $make template
> > > > 
> > > 
> > > It's the same conflict - I guess you need to wait for the change to be
> > > merged to 3.2
> > 
> > Yes sorry about that it was very late and I was a bit punchy.
> 
> Since Marek updated the qubes builder to address the security bulletin issue 
> the tag for centos is no longer valid so it fails the update after choosing 
> the centos template with a invalid / no valid tag found error but does 
> proceed to allow choosing of the templates to build.



[user@Build-Qubes qubes-builder]$ make get-sources
-> Updating sources for builder-centos...
--> Fetching from https://github.com/QubesOS/qubes-builder-centos.git master...
--> Verifying tags...
No valid signed tag found!
---> One of invalid tag:
object cfc7d315cfdfe493a86f103a0825ba630339ab8f
type commit
tag mm_cfc7d315
tagger Marek Marczykowski-Górecki  1519612572 
+0100

Tag for commit cfc7d315cfdfe493a86f103a0825ba630339ab8f
gpg: WARNING: unsafe permissions on homedir 
`/home/user/qubes-builder/keyrings/git'
gpg: Signature made Sun 25 Feb 2018 09:36:12 PM EST using RSA key ID 42CFA724
gpg: Good signature from "Marek Marczykowski-Górecki (Qubes OS signing key) 
"
Makefile:190: recipe for target 'builder-centos.get-sources' failed
make: *** [builder-centos.get-sources] Error 1

-- 
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/f96c34a7-c302-4e9e-be59-7b1ee988437e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Building Centos template conflict error?

2018-03-03 Thread Tim W 
On Friday, March 2, 2018 at 10:14:51 PM UTC-5, Tim W wrote:
> On Friday, March 2, 2018 at 4:05:30 AM UTC-5, Unman wrote:
> > On Fri, Mar 02, 2018 at 12:41:29AM -0800, Tim W wrote:
> > > On Tuesday, February 27, 2018 at 2:37:46 AM UTC-5, Frédéric Pierret 
> > > (fepitre) wrote:
> > > > Le mardi 27 février 2018 00:30:10 UTC+1, Tim W a écrit :
> > > > > Great that was failing basically on all non standard templates i.e. 
> > > > > not fedora, debain, or whonix.   They would all fail but it seems 
> > > > > each had issues ubuntu, centos, arch.  Seems they are each getting 
> > > > > fixed for 3.2 and getting updated for 4.0 now.  I was just testing to 
> > > > > ensure things were still working for building as I know many prefer 
> > > > > to build their own iso and templates vs binary.  I am one.  Figured 
> > > > > if docs had to be updated I would do that but it seems at most just a 
> > > > > tweak or two in docs is all thats needed.
> > > > 
> > > > Indeed, it was just an adjustment with respect to the rpm spec of the 
> > > > conflicting package. CentOS is shipping a file in their own dconf but 
> > > > not Fedora. Recently a file /etc/dconf/profile/user has been used and 
> > > > provided by Qubes and that is why there was a recent conflict. The 
> > > > template for R4.0 is on the road! I finished last week to do all the 
> > > > necessary and Marek is currently implementing it.
> > > >  
> > > > > Thanks again for you and Marek getting it working
> > > > 
> > > > You're welcome.
> > >  
> > > Just tried to build the standard template only under 3.2 and got this 
> > > conflict
> > > 
> > > Transaction check error:
> > >   file /etc/dconf/profile/user from install of 
> > > qubes-core-vm-3.2.25-1.el7.centos.x86_64 conflicts with file from package 
> > > dconf-0.26.0-2.el7.x86_64
> > > 
> > > It fails on $make template
> > > 
> > 
> > It's the same conflict - I guess you need to wait for the change to be
> > merged to 3.2
> 
> Yes sorry about that it was very late and I was a bit punchy.

Since Marek updated the qubes builder to address the security bulletin issue 
the tag for centos is no longer valid so it fails the update after choosing the 
centos template with a invalid / no valid tag found error but does proceed to 
allow choosing of the templates to build.

-- 
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/76b8b492-9410-4850-96cf-8acf48da95d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: non qubes

2018-03-03 Thread Tim W 
On Saturday, March 3, 2018 at 6:33:27 AM UTC-5, awokd wrote:
> On Thu, March 1, 2018 11:13 am, Yuraeitha wrote:
> > On Thursday, March 1, 2018 at 9:30:52 AM UTC+1, jer...@disroot.org wrote:
> >
> >> where do i find support for security, privacy? (some place where i can
> >> post with anonimity too, reddit privacy requires java script i think,
> >> doesn't it compromise anonimity? also i would like to ask how things
> >> are recommended in doing, like a guide, etc...
> >>
> >> for example i need to know if enabling java script to watch youtube in
> >> tor will compromise anonimity or anything like that, or enabling java
> >> script in other websites, if it's a risk.. and how i should tell where
> >> i can enable java script, etc.. also if it's recommended to buy stuff
> >> through tor, and how, etc and what its benefits, etc...
> 
> General usage questions about Tor might be best asked over on the
> tor-users mailing list. Enabling Javascript anywhere is a risk because it
> opens up attack vectors to your computer, but by itself it will not
> automatically compromise anonymity. Someone would have to be using an
> exploit delivered over Javascript to do that. This is pretty unlikely in
> the case of large sites such as Youtube or Reddit, unless state agencies
> are targeting you specifically (which Tor makes more difficult).
> 
> Qubes is designed to contain exploits to a single VM. If you use it with a
> disposable VM for browsing, even if you do get compromised in a browsing
> session such as by a Javascript virus in Google ads on Youtube, closing
> that Tor Browser and opening a new one will result in it using a fresh,
> non-compromised disposable VM.
> 
> Buying items through Tor means using your real identity through Tor. Some
> people use Tor for everything including banking. Some use Tor for all
> browsing except anything involving their real identity. Others just use
> Tor occasionally for some sites. Try searching tor-users mailing list for
> questions similar to yours; you'll need to develop your own answer.

That is how 99.9% of those caught using tor are found.  Its from bad opsec not 
actually breaking of tor itself.Tech even the way silk road was brought 
down was via a spoof more than 100% of breaking tor.  but like anything layers. 
 Whats great about qubes is it helps in numerous ways from being resistant to 
the spread of malware its easy integration oh whonix.  It ability to string 
numerous network tunneling chains together to creating multiple layers if done 
correctly have the effect of indecent cells working to a common goal with only 
the end user knowing all parts.  Qubes is but one part but its configuration 
allows for numerous ways and layer for security and or if done with proper 
opsec anonymity

-- 
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/5b7e0c16-0c5a-4c6e-a357-54d9a44800bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Mac Spoofing preinstalled? - Qubes 4 rc4

2018-03-03 Thread Yuraeitha 
On Saturday, March 3, 2018 at 8:21:28 AM UTC+1, Tristan Fleming wrote:
> Has mac spoofing been preinstalled in Q4 rc4? I cant find any documentation 
> on it, but the cmd: ip link show wls1 
> 
> changes every 10 minutes or so. I actually want to stop it and I cant seem to 
> make it static. Lil help!!
> 
> Ive tried everything I can think of. Im not entirely understanding the 
> network topology. 
> 
> I have figured out that Macchanger is installed on the Debian Template. Im 
> otherwise at a loss.

In addition to what Chris said which I agree with, be careful if you're relying 
on this type of privacy. If it fails, even for a brief moment, then your real 
identity has been exposed. And this is very likely to happen.

If your goal is just general increase of privacy, and not absolute privacy with 
risks carrying in it (i.e. avoiding dictators, or police state, and who knows 
what other baddies), then you should probably think of something else, than 
take huge risks or risking your life. If you don't have any big risks on the 
line though, then yes, maybe it can be worth it even if it sometimes fail. I'm 
not an expert though, but all you need to know is that it can fail, and the 
above is the implications if it does indeed fail. 

Even if the risk is, say, less than 1% every time its used, or even less than 
0,01%, over time as time goes on, that risk will increase slowly, until it will 
eventually happen to you, the risks will keep going up. You won't even have to 
be extraordinary unlucky or lucky, it can happen at any time as it moves from 
almost 0% risk to almost certain 100% risk.

As will anything which has a low risk, if used many times, that risk will grow, 
until you almost certainly will hit you. So too is the same logic for why 
immortality is impossible, because even if you don't age anymore and is 
eternally young and healthy, the odds that something unnatural will kill you, 
like say getting run over by a car, increases as time goes on. Of course it 
probably won't be a car, it could be anything that eternal youth is not 
protecting you from, like getting shot or falling down from a high place, who 
knows, you get the picture. That's why, as I understand it, macspoofing is 
discouraged. Of course it could be useful, if you don't mind it failing once in 
a while, and only want mostly better privacy, and not fully protected privacy, 
i.e. if you only want to detour dodgy marketing and companies making profits of 
knowing everything about you, then this might be a valid strategy to reduce it.

So until that feature becomes 100% reliable, all the time, then it will always 
carry risk. The question is better asked, is it a risk you can survive getting 
run over by?

-- 
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/bd1336a7-4fa1-4fe2-b494-34f48b88d84c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AW: Re: [qubes-users] For community by community - A way to preserve/focus everyones work going into Qubes, bottom-up

2018-03-03 Thread Yuraeitha 
On Sunday, March 4, 2018 at 2:01:40 AM UTC+1, Yuraeitha wrote:
> @[799]
> Maybe we can do both and increase the overall value altogether? I'll 
> understand if you don't think that is a good idea, but lets for a moment try 
> see if a merged forum/github-wiki concept can work. We could make a sub-forum 
> or even a whole forum section for GitHub account activity. Make a sticky post 
> which is kept updated, with overview and introducing every GitHub content 
> developers who are making unofficial work to Qubes. Then below that, everyone 
> can post a detailed post for their GitHub page, listing and giving brief or 
> detailed explanations of what it brings of value. Essentially it's possible 
> to promote ones work here, so that others can find it. 
> 
> So overall, for example one forum section for guides on how to use and get 
> into Qubes (i.e. new people to Qubes, and how to get started). Another 
> section for work on scripts and guides with sub-forums, moving the 
> scripts/guides over as they develop. And a final forum section to polish the 
> scripts/guides to finish them. Then we can have a forum section for GitHub 
> pages as described above, this way, people can choose the degree they want 
> others to meddle in their work. For example GitHub while cooperative, doesn't 
> tend to have others come in unless there is an open invitation there, or if 
> the other party is rude. But on the forum here, it's an open invitation to 
> come and work together on a project. This way one can preserve a form of 
> individuality too, and invite others in naturally through the forum as a 
> framework, if that is what is desired. The forum will then focus on both 
> approaches, whether it's promoting/sharing work done on, or inviting on 
> projects for work to-do.
> 
> As such people can choose the style they like. Also in addition to that, not 
> everyone enjoys working in groups, but some enjoys working alone (and that 
> should be respected, imo). For example it may fuel energy and be relaxing to 
> work alone (it can even be a way of relaxing after a long day at 
> work/similar), while in contrast it would be exhausting to work with others. 
> Essentially the embodiment of being introvert and extrovert, both I think is 
> completely normal and none is better than the other. People who gain energy 
> working with others prefer a different work-style. Nothing wrong with it 
> either, it's just how people gain energy, there is nothing bad about either 
> of the two.
> 
> I think if we mix the approaches together, we can add value to both 
> suggestions. It's also easier to have discussions for both groups, for 
> example a forum for the copyright/law discussions on using other people work, 
> so that we can be better informed on such matters. We can also highlight some 
> kinds of works in various of different forums, wherever there is people 
> willing to discuss or read, and all this can be closely tied to GitHub and 
> GitHub Wiki's. What do you think of a merged approach?
> 
> 
> 
> 
> 
>   
> @Andrew
> On Saturday, March 3, 2018 at 6:25:08 AM UTC+1, Andrew David Wong wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> > 
> > On 2018-03-02 23:16, Andrew David Wong wrote:
> > > On 2018-03-02 15:05, Yuraeitha wrote:
> > >> Some of the issues/questions addressed seems like they could be 
> > >> solved quite effectively and efficiently on a highly
> > >> customize-able forum?
> > > 
> > >> [...]
> > > 
> > >> Thoughts about using a forum?
> > > 
> > > FYI, in case you haven't seen this thread:
> > > 
> > > https://groups.google.com/d/topic/qubes-users/2rqas38ncFA/discussion
> > >
> >  
> > While at it, here are some other old threads where similar ideas have
> > been suggested:
> > 
> > https://groups.google.com/d/topic/qubes-users/D0YuoXMe_vE/discussion
> > 
> > https://groups.google.com/d/topic/qubes-users/es4q40dt1EE/discussion
> > 
> > Approximately every 6-12 months since the beginning of the project, a
> > new person (including me, at one point, IIRC) suggests that there
> > should be a Qubes wiki or forum, so you'll find many more threads like
> > these if you search through the archives. :)
> > 
> > - -- 
> > Andrew David Wong (Axon)
> > Community Manager, Qubes OS
> > https://www.qubes-os.org
> > 
> > -BEGIN PGP SIGNATURE-
> > 
> > iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqaMZcACgkQ203TvDlQ
> > MDDD4xAAwbajnwJ/PZxzrVnmzKECGkYVQQDs90LieN1s/ewuqilNx9Cdxk8Fy9La
> > jokevIemgSB/QjqRD1zl2L0ksn/XhsOgQyWyK+RCSNWdKsvDhJtsVvh0B5SA5t4N
> > FrMzig0uUHLodl9ZOT9ltvy/nOnMBj8YcfQ2i+3yEaOFSN6hc7DkyXnPRhLbEdrK
> > pwJJxbdAkvocSu6tEL1xE86cZ1CZrBIHvrVt1oCy1QPCr5EBNUukg4JMGOygZNi2
> > 62TF+/vv1Fe9IeJ7tu+WaZLIJQ1guLesYMISMHAvsUaAwB+vbMFUFuRhHqhiB7Ir
> > qEyrf5S24aulX/F9w8043088Wd+RA/lWG2lyXZk3w9H+Gqn2UOKnKnJRCFxBmkbE
> > O+TS3/U4pB5t/4K9oezKc9dSODEt4RZO4LSN9U0i5Ksp4q1WDJyJC7eyRnQTpDc6
> > sQHHCi3d0kFTxDozcjCJPFTLhE3OYqBfCClMmCXlLhL1j2/N0XS9nOYWRL2foA1R
> >

Re: AW: Re: [qubes-users] For community by community - A way to preserve/focus everyones work going into Qubes, bottom-up

2018-03-03 Thread Yuraeitha 
@[799]
Maybe we can do both and increase the overall value altogether? I'll understand 
if you don't think that is a good idea, but lets for a moment try see if a 
merged forum/github-wiki concept can work. We could make a sub-forum or even a 
whole forum section for GitHub account activity. Make a sticky post which is 
kept updated, with overview and introducing every GitHub content developers who 
are making unofficial work to Qubes. Then below that, everyone can post a 
detailed post for their GitHub page, listing and giving brief or detailed 
explanations of what it brings of value. Essentially it's possible to promote 
ones work here, so that others can find it. 

So overall, for example one forum section for guides on how to use and get into 
Qubes (i.e. new people to Qubes, and how to get started). Another section for 
work on scripts and guides with sub-forums, moving the scripts/guides over as 
they develop. And a final forum section to polish the scripts/guides to finish 
them. Then we can have a forum section for GitHub pages as described above, 
this way, people can choose the degree they want others to meddle in their 
work. For example GitHub while cooperative, doesn't tend to have others come in 
unless there is an open invitation there, or if the other party is rude. But on 
the forum here, it's an open invitation to come and work together on a project. 
This way one can preserve a form of individuality too, and invite others in 
naturally through the forum as a framework, if that is what is desired. The 
forum will then focus on both approaches, whether it's promoting/sharing work 
done on, or inviting on projects for work to-do.

As such people can choose the style they like. Also in addition to that, not 
everyone enjoys working in groups, but some enjoys working alone (and that 
should be respected, imo). For example it may fuel energy and be relaxing to 
work alone (it can even be a way of relaxing after a long day at work/similar), 
while in contrast it would be exhausting to work with others. Essentially the 
embodiment of being introvert and extrovert, both I think is completely normal 
and none is better than the other. People who gain energy working with others 
prefer a different work-style. Nothing wrong with it either, it's just how 
people gain energy, there is nothing bad about either of the two.

I think if we mix the approaches together, we can add value to both 
suggestions. It's also easier to have discussions for both groups, for example 
a forum for the copyright/law discussions on using other people work, so that 
we can be better informed on such matters. We can also highlight some kinds of 
works in various of different forums, wherever there is people willing to 
discuss or read, and all this can be closely tied to GitHub and GitHub Wiki's. 
What do you think of a merged approach?





  
@Andrew
On Saturday, March 3, 2018 at 6:25:08 AM UTC+1, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2018-03-02 23:16, Andrew David Wong wrote:
> > On 2018-03-02 15:05, Yuraeitha wrote:
> >> Some of the issues/questions addressed seems like they could be 
> >> solved quite effectively and efficiently on a highly
> >> customize-able forum?
> > 
> >> [...]
> > 
> >> Thoughts about using a forum?
> > 
> > FYI, in case you haven't seen this thread:
> > 
> > https://groups.google.com/d/topic/qubes-users/2rqas38ncFA/discussion
> >
>  
> While at it, here are some other old threads where similar ideas have
> been suggested:
> 
> https://groups.google.com/d/topic/qubes-users/D0YuoXMe_vE/discussion
> 
> https://groups.google.com/d/topic/qubes-users/es4q40dt1EE/discussion
> 
> Approximately every 6-12 months since the beginning of the project, a
> new person (including me, at one point, IIRC) suggests that there
> should be a Qubes wiki or forum, so you'll find many more threads like
> these if you search through the archives. :)
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqaMZcACgkQ203TvDlQ
> MDDD4xAAwbajnwJ/PZxzrVnmzKECGkYVQQDs90LieN1s/ewuqilNx9Cdxk8Fy9La
> jokevIemgSB/QjqRD1zl2L0ksn/XhsOgQyWyK+RCSNWdKsvDhJtsVvh0B5SA5t4N
> FrMzig0uUHLodl9ZOT9ltvy/nOnMBj8YcfQ2i+3yEaOFSN6hc7DkyXnPRhLbEdrK
> pwJJxbdAkvocSu6tEL1xE86cZ1CZrBIHvrVt1oCy1QPCr5EBNUukg4JMGOygZNi2
> 62TF+/vv1Fe9IeJ7tu+WaZLIJQ1guLesYMISMHAvsUaAwB+vbMFUFuRhHqhiB7Ir
> qEyrf5S24aulX/F9w8043088Wd+RA/lWG2lyXZk3w9H+Gqn2UOKnKnJRCFxBmkbE
> O+TS3/U4pB5t/4K9oezKc9dSODEt4RZO4LSN9U0i5Ksp4q1WDJyJC7eyRnQTpDc6
> sQHHCi3d0kFTxDozcjCJPFTLhE3OYqBfCClMmCXlLhL1j2/N0XS9nOYWRL2foA1R
> FLaE4lOBuoNcAQO/XTXMEd3F2XUlCKOiLCLdNCVIYyhZJSFwHqpwt8pRLRk6n2hs
> EdiyVGQh4uyOt1rWEniPEyyb2Bx/MLSYT4iafU/3ltY7uKbzDpmaUSP+oVZd6+gj
> 6eEpVFlDzp4kfTCFRj3a/Gx8Ail4P9/KmHp+tBVfxrWQrFi+bWs=
> =I6G3
> -END PGP SIGNATURE-

Those are interesting older threads indeed, it gives some good new insight. I

AW: Re: AW: Re: [qubes-users] For community by community - A way to preserve/focus everyones work going into Qubes, bottom-up

2018-03-03 Thread '[799]' via qubes-users 
Hello yuraeitha,

 Original-Nachricht 
An 2. März 2018, 22:05, Yuraeitha schrieb:

> Thoughts about using a forum? Possibly with
> a frontpage blog? If we indeed go with
> something like this, forum or some other
> platform, as you also questioned Ivan

I don't know what the right platform looks like to share scripts and howtos 
which didn't make it to Qubes docs yet.
But what I know is that I would like to have something available as soon as 
possible.
I would call my self still a Qubes newbie which is a great opportunity to write 
documentation because I try to implement my existing workflows on Qubes and as 
soon as I find out that it will not work I am trying to work around it: either 
by changing my workflow or by enhancing Qubes so that it fits better.
This "knowledge" is interesting to be shared for other newbie users or people 
who are interested in Qubes, mainly because...

1) people might be interested in Qubes, but are looking for information if 
their current workflow could be done on Qubes

2) if they need to change their workflow, they might be interested what would 
be a good approach

3) an active community is a very good advertisement.

Thereof I think having a place at GitHub, where we can consolidate information 
is a good thing.
Two reasons:

1) we know how to use GitHub
2) transfer of "qualified documentation" to the Qubes docs will be easy.

Neverless it could make sense to present some of the more interesting subjects 
which have reached a certain quality level on the Qubes Blog or another blog.

Please keep in mind that Qubes is and should be very interesting for user which 
are not that experienced with Mailinglists and GitHub, they also have the right 
to be reasonable secure and thereof the access to the documentation should be 
easy in the end.

> who is interested in being a moderator? I'm
> okay with helping out with it, but I probably
> will need help to cover everything, especially
> when I have exams and so on.

I could also help out, but I don't think that there is much need to do so. If 
we are using Github as repository (soemthing maybe named 
"qubes-community-playground") we can start to use it.
Honestly I expect to see much more people take a very short look there to scan 
if there is something that is useful for them, instead of actually contributing 
documentation themselves. But this is totally fine.

I am currently writing a how-to to access Microsoft Exchange under Qubes which 
could be interesting to others, of they want to decide if they try it all.
While I could add it to my own GitHub repository it would make more sense to 
share it and to improve it step by step.

Maybe also a page like: "I wish Qubes would allow me to ..." where users leave 
their wishes and maybe others have a quick idea how to solve this. This could 
become something like a backlog to improve Qubes even further.

[799]

-- 
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/3mL8yqgzX82vXT0M2YQTfqtokZoNBaVgopo61t_IrBWJOu23qV2xMPREH9VLQdthorQIdTRoh_e_XqIJIGbZBHbKknThRCzmF0RhJXJZH2g%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] kernel panic after upgrade

2018-03-03 Thread Qubed One 
mai...@maiski.net:
> Hello,
> 
> Unfortunately after the last update of Qubes 4.0 I have a kernel panic:
> "unable to mount root fa on unknown block" and would appreciate if
> somebody here could give me a tip.
> 
> I installed Qubes 4.0-RC1 and since then been only updating.


That could be the problem. A reinstall was required between 4.0-RC1 and
4.0-RC2. See here:

https://www.qubes-os.org/news/2017/10/23/qubes-40-rc2/


> After the next-to-last update I was not able to boot xen 4.8.3 and linux
> 4.14.13-3.
> With the following configuration: xen 4.8 and linux 4.9.56-21 there is
> no problem.
> My machine is Lenovo T470S.
> 
> Does anyone have an idea?
> 
> m

-- 
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/bf5d1c10-e2ab-0e06-1f8b-7cd2645cc94f%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Adding AppMenus in Qubes 4

2018-03-03 Thread Glen H 
On Saturday, March 3, 2018 at 12:02:15 PM UTC-5, awokd wrote:
> On Sat, March 3, 2018 4:23 pm, Glen H wrote:
> 
> >
> > I created a pull request to update the docs:
> >
> >
> > https://github.com/QubesOS/qubes-doc/pull/612
> 
> Haha I did too: https://github.com/QubesOS/qubes-doc/pull/611
> 
> Wanted to see how it worked out for you before publicizing.
> 
> Thank you too, will check yours out as well.

I like your better.  I added a comment to yours.

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/2d69805b-fc39-4329-971d-356b47ffe6a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes R3.2 Failed to Load Kernel Modules

2018-03-03 Thread 'awokd' via qubes-users 
On Sat, March 3, 2018 3:54 pm, alternateg...@gmail.com wrote:
> Yeah.  I appreciate your feedback.  It took me a lot to finally post.  I
> saw everything.  I tried everything.  Disabled hyperthreading etc.  Every
> time I got to the configuration part it would crash at Setting up
> Network.  I searched every Linux forum.  I tried repairing my install six
> or seven times (this was in fact the second machine I attempted Qubes
> on).  journalctl -xe, didn't seem to list a lot.
> Systemd-modules-load.service (that one wouldn't work at all), I didn't
> find much else to try and troubleshoot.  I tried to boot in UEFI mode -
> that didn't work either.  I ordered a third machine, a Lenovo to try.  My
> advice to Qubes as a tech savvy user is to meet their users half-way.
> This is apparently only an OS for rocket scientists or extreme Linux
> hackers.  The HCL doesn't make it very simple to even know what to buy.

I believe that systemd-modules-load.service failure is a false alarm; I
get it too and it doesn't seem to hurt anything. I had another laptop that
would crash on setting up sys-net (Network). My workaround was to
temporarily pull the wifi card for the install. Qubes could then set up
sys-net with just the onboard ethernet and complete the install. Then I
added the wifi card back and could troubleshoot getting it added to a VM.
Once I had that resolved, I added it back to sys-net.


-- 
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/f33111e3fc54319a300c78ea3dbd610a.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Adding AppMenus in Qubes 4

2018-03-03 Thread Glen H 
On Saturday, March 3, 2018 at 7:43:02 AM UTC-5, awokd wrote:
> On Sat, March 3, 2018 5:55 am, Glen H wrote:
> > Hi,
> >
> >
> > I'm trying to follow the instructions here for adding app menus:
> >
> >
> > https://www.qubes-os.org/doc/managing-appvm-shortcuts/
> >
> >
> > But I can't get it to work. I noticed that only templateVMs have an
> > "apps.templates" directory so I added a new vuescan.desktop file to my
> > template's dir from Dom0
> > (~/.local/share/qubes-appmenus/fedora-26/apps.templates/vuescan.desktop)
> 
> Can you try creating the shortcut in
> ~/.local/share/qubes-appmenus/vmname/apps instead? See
> https://www.qubes-os.org/doc/dispvm-customization/#adding-arbitrary-programs-to-disposable-vm-application-menu
> .

This doesn't work for me.  I did:

```
cp vuescan.desktop 
~/.local/share/qubes-appmenus/vmname/apps/vmname-vuescan.desktop
qvm-sync-appmenus fedora-26
# also updated apps in Qubes Manager for vmname
```

> The "behind the scenes" section is just explaining how qvm-sync-appmenus
> works. It's not instructions on how to create a shortcut, but I can see
> why you might think them to be! Let me think on how to reword this or make
> it more clear.

I guess the difference with that page and what I'm trying to do is the page is 
written for someone who installed software via the package manager.  I'm 
installing software myself.  It make me think I need to put the .desktop file 
where the OS usually stores them and then it might be picked up.

Glen

-- 
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/b182940e-e55b-4134-978b-4367eb0485e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes R3.2 Failed to Load Kernel Modules

2018-03-03 Thread alternategems 
And I actually know my way around a Linux command line, but the resources do 
not exist to help users like me.  I returned the Latitude.  

-- 
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/37f1a9bf-d92f-425c-944f-efd033059c7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes R3.2 Failed to Load Kernel Modules

2018-03-03 Thread alternategems 
Yeah.  I appreciate your feedback.  It took me a lot to finally post.  I saw 
everything.  I tried everything.  Disabled hyperthreading etc.  Every time I 
got to the configuration part it would crash at Setting up Network.  I searched 
every Linux forum.  I tried repairing my install six or seven times (this was 
in fact the second machine I attempted Qubes on).  journalctl -xe, didn't seem 
to list a lot. Systemd-modules-load.service (that one wouldn't work at all), I 
didn't find much else to try and troubleshoot.  I tried to boot in UEFI mode - 
that didn't work either.  I ordered a third machine, a Lenovo to try.  My 
advice to Qubes as a tech savvy user is to meet their users half-way.  This is 
apparently only an OS for rocket scientists or extreme Linux hackers.  The HCL 
doesn't make it very simple to even know what to buy.

-- 
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/0bae554f-4f6e-4be2-b89b-1d25efba2777%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Solved/Progress [Re: Cannot assign USB controller to App VM anymore (Qubes 3.2)]

2018-03-03 Thread sboresch 
Thank you for looking into this!

Am Samstag, 3. März 2018 13:28:24 UTC+1 schrieb awokd:
> On Fri, March 2, 2018 2:27 pm, Stefan wrote:
> 
> > https://www.qubes-os.org/doc/assigning-devices/
> >
> >
> > and tried enabling 'permissive' mode as described for R3.2 in the above
> > documentation. However, this per se doesn't work, as the target file
> > (/sys/bus/pci/drivers/pciback/permissive)
> > is not writeable, even for root and even when triggered through systemd.
> 
> Just tested again on R3.2 and the procedure in the doc works, but only for
> re-assignable devices (ones using the pciback driver in lspci). Are you
> sure you were trying to write the correct :? When I tried with an
> un-assignable device, I got:
> 
> bash: echo: write error: No such device
> 

This sounds like the error I got; don't really know what the properties
of this USB hub are. I did not follow up as this isn't necessary

> 
> >
> >>
> >> And xl dmesg shows:
> >>
> >>
> >> XEN) [VT-D] It's disallowed to assign :00:1a.0 with shared RMRR at
> >> da8d5000 for Dom5. (XEN) XEN_DOMCTL_assign_device: assign :00:1a.0
> >> to dom5 failed (-1)
> >>
> >
> > For the record, xl dmesg is now telling me that
> > [VT-D] It's risky to assign .. with shared RMRR at .. for Dom4
> 
> Setting pci_strictreset to false is what changed this message from
> "disallowed" to "risky".
> 
> > what ever that means.
> >
> > I don't know which of the options / changes did the trick, but one or
> > more of the above seems to enable the camera in 'untrusted'.
> 
> Setting pci_strictreset to false.

It indeed looks like it. I reset everything (to the best of my recollection) and
played again with the various options to pass through the USB hub to 
'untrusted'. And indeed, this time around, setting pci_strictreset to false
was enough. I was a 100% positive that I tried that before and it seemed not
to work. However, this time, after qvm-reset -s .. I rebooted before trying
whether this changed anything.

Anyways, thanks again for your help!

Stefan

-- 
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/0682b44e-f24f-4a9d-8663-98c82d3b9a0c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Adding AppMenus in Qubes 4

2018-03-03 Thread 'awokd' via qubes-users 
On Sat, March 3, 2018 12:42 pm, awokd wrote:
> On Sat, March 3, 2018 5:55 am, Glen H wrote:
>
>> Hi,
>>
>>
>>
>> I'm trying to follow the instructions here for adding app menus:
>>
>>
>>
>> https://www.qubes-os.org/doc/managing-appvm-shortcuts/
>>
>>
>>
>> But I can't get it to work. I noticed that only templateVMs have an
>> "apps.templates" directory so I added a new vuescan.desktop file to my
>> template's dir from Dom0
>> (~/.local/share/qubes-appmenus/fedora-26/apps.templates/vuescan.desktop
>> )
>>
>
> Can you try creating the shortcut in
> ~/.local/share/qubes-appmenus/vmname/apps instead? See
> https://www.qubes-os.org/doc/dispvm-customization/#adding-arbitrary-progra
> ms-to-disposable-vm-application-menu .

Looks like another option is to create the .desktop file inside the
TemplateVM itself, under /usr/local/share/application and then run
qvm-sync-appmenus against that template.

https://www.mail-archive.com/qubes-users@googlegroups.com/msg17553.html


-- 
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/df790c18acdd49a80fc4f2ab6edaa824.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] kernel panic after upgrade

2018-03-03 Thread 'awokd' via qubes-users 
On Fri, March 2, 2018 8:22 am, mai...@maiski.net wrote:
> Hello,
>
>
> Unfortunately after the last update of Qubes 4.0 I have a kernel
> panic: "unable to mount root fa on unknown block" and would appreciate
> if somebody here could give me a tip.

I think there is a typo here, try searching on "unable to mount root fs on
unknown block" instead. Looks like there are several possible causes,
especially if you are dual/multi-booting.


-- 
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/9c9002d7bf498042059782bde81fd7b4.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Adding AppMenus in Qubes 4

2018-03-03 Thread 'awokd' via qubes-users 
On Sat, March 3, 2018 5:55 am, Glen H wrote:
> Hi,
>
>
> I'm trying to follow the instructions here for adding app menus:
>
>
> https://www.qubes-os.org/doc/managing-appvm-shortcuts/
>
>
> But I can't get it to work. I noticed that only templateVMs have an
> "apps.templates" directory so I added a new vuescan.desktop file to my
> template's dir from Dom0
> (~/.local/share/qubes-appmenus/fedora-26/apps.templates/vuescan.desktop)

Can you try creating the shortcut in
~/.local/share/qubes-appmenus/vmname/apps instead? See
https://www.qubes-os.org/doc/dispvm-customization/#adding-arbitrary-programs-to-disposable-vm-application-menu
.

The "behind the scenes" section is just explaining how qvm-sync-appmenus
works. It's not instructions on how to create a shortcut, but I can see
why you might think them to be! Let me think on how to reword this or make
it more clear.


-- 
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/fdeff695a9fd3d65e26d77925d463878.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Solved/Progress [Re: Cannot assign USB controller to App VM anymore (Qubes 3.2)]

2018-03-03 Thread 'awokd' via qubes-users 
On Fri, March 2, 2018 2:27 pm, sbore...@gmail.com wrote:

> https://www.qubes-os.org/doc/assigning-devices/
>
>
> and tried enabling 'permissive' mode as described for R3.2 in the above
> documentation. However, this per se doesn't work, as the target file
> (/sys/bus/pci/drivers/pciback/permissive)
> is not writeable, even for root and even when triggered through systemd.

Just tested again on R3.2 and the procedure in the doc works, but only for
re-assignable devices (ones using the pciback driver in lspci). Are you
sure you were trying to write the correct :? When I tried with an
un-assignable device, I got:

bash: echo: write error: No such device


>
>>
>> And xl dmesg shows:
>>
>>
>> XEN) [VT-D] It's disallowed to assign :00:1a.0 with shared RMRR at
>> da8d5000 for Dom5. (XEN) XEN_DOMCTL_assign_device: assign :00:1a.0
>> to dom5 failed (-1)
>>
>
> For the record, xl dmesg is now telling me that
> [VT-D] It's risky to assign .. with shared RMRR at .. for Dom4

Setting pci_strictreset to false is what changed this message from
"disallowed" to "risky".

> what ever that means.
>
> I don't know which of the options / changes did the trick, but one or
> more of the above seems to enable the camera in 'untrusted'.

Setting pci_strictreset to false.

-- 
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/bc6c4fe2cd0600f39143797d52ddfef1.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: qrexec demon fails to load any VM when I attach any device

2018-03-03 Thread 'awokd' via qubes-users 
On Fri, March 2, 2018 4:00 am, Allen Larocque wrote:

> I checked the qvm-pci lists and the audio driver isn't assigned to any
> VMs. This is a fresh install with the sys-USB VM on.

You wrote "driver" here- you meant "device", right? Double check your VM
settings > Devices and make sure it's not assigned to any VM. If that
results in unassigning it from one or more, reboot afterwards.

> As far as I can summarize the problem now:
> 1. lspci shows the audio device.
> 2. aplay-l shows 'no audio device'

It should, if dom0 recognizes it. Look through "sudo journalctl -b" for
errors related to your audio device.

> 3. Pulseaudio output and config tabs show no audio devices (except the
> virtual one 'simultaneous output').
>
> I've been interpreting this as a driver issue? But unsure how to fix/ get
> the appropriate drivers

Journalctl should give you more information to review.


-- 
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/8db587b36629138ee28e771ab6ec18c9.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] error opening sys-net & dom0 flashing yellow triangle

2018-03-03 Thread 'awokd' via qubes-users 
On Thu, March 1, 2018 12:12 am, yreb...@riseup.net wrote:
> Today opening sys-net  I get these errors in the terminal , though
> sys-net continues  on and  seems OK ,  I suppose by now, it is expected
> behavior that sys-net takes a long time and sometimes never shutsdown ??
>
> File "/usr/bin/qvm-start", line 136, in 
> main() File "/usr/bin/qvm-start", line 120, in main
> xid = vm.start(verbose=options.verbose,
> preparing_dvm=options.preparing_dvm, start_guid=not options.noguid,
> notify_function=tray_notify_generic if options.tray else None) File
> "/usr/lib64/python2.7/site-packages/qubes/modules/005QubesNetVm.py",
> line 143, in start vm.attach_network(wait=False) File
> "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py",
> line 1738, in attach_network self._format_net_dev(self.ip, self.mac,
> self.netvm.name)) File "/usr/lib64/python2.7/site-packages/libvirt.py",
> line 530, in attachDevice if ret == -1: raise libvirtError
> ('virDomainAttachDevice() failed',
> dom=self) libvirt.libvirtError: invalid argument: network device with mac
> 00:16:3e:5e:6c:06 already exists
>
>
>
>
> I cont'd on after  sys-net  started  via CLI  above  but occasionally I
> see a dom0 flashing triangle  FWIW, maybe not related to below ??
>
> (XEN) [VT-D]DMAR:[DMA Write] Request device [:04:00.0] fault addr
> fff0, iommu reg = 82c0009f4000 (XEN) [VT-D]DMAR: reason 05 - PTE
> Write access is not set
> (XEN) [VT-D]DMAR:[DMA Write] Request device [:04:00.0] fault addr
> fff0, iommu reg = 82c0009f4000 (XEN) [VT-D]DMAR: reason 05 - PTE
> Write access is not set
> (XEN) [VT-D]DMAR:[DMA Write] Request device [:04:00.0] fault addr
> fff0, iommu reg = 82c0009f4000 (XEN) [VT-D]DMAR: reason 05 - PTE
> Write access is not set
>
>
>
>
> THIRDLY,
> of late qvm-shutdown --all   has been hanging and I must do a hard reboot ,
> or  do  qvm-shutdown VM1 VM2 VM3  etc ,  which is kind of a pain ...
>
>
> I'm not really geeky enough to know if any of these might be related or
> fix themselves,  Lastly,  I am running  the security update repo  , but
> don't recall if any of these started before or after installing the
> security patch  for  the intel  issues.
>
>
> any suggestions to do something or nothing appreciated

These are probably related. If you don't use the device on 04:00.0 (check
with lspci), remove it from sys-net and see if it helps. See
https://github.com/QubesOS/qubes-issues/issues/1710 too.

-- 
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/a669cb876630ae99e26ecd09009004b6.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: non qubes

2018-03-03 Thread 'awokd' via qubes-users 
On Thu, March 1, 2018 11:13 am, Yuraeitha wrote:
> On Thursday, March 1, 2018 at 9:30:52 AM UTC+1, jer...@disroot.org wrote:
>
>> where do i find support for security, privacy? (some place where i can
>> post with anonimity too, reddit privacy requires java script i think,
>> doesn't it compromise anonimity? also i would like to ask how things
>> are recommended in doing, like a guide, etc...
>>
>> for example i need to know if enabling java script to watch youtube in
>> tor will compromise anonimity or anything like that, or enabling java
>> script in other websites, if it's a risk.. and how i should tell where
>> i can enable java script, etc.. also if it's recommended to buy stuff
>> through tor, and how, etc and what its benefits, etc...

General usage questions about Tor might be best asked over on the
tor-users mailing list. Enabling Javascript anywhere is a risk because it
opens up attack vectors to your computer, but by itself it will not
automatically compromise anonymity. Someone would have to be using an
exploit delivered over Javascript to do that. This is pretty unlikely in
the case of large sites such as Youtube or Reddit, unless state agencies
are targeting you specifically (which Tor makes more difficult).

Qubes is designed to contain exploits to a single VM. If you use it with a
disposable VM for browsing, even if you do get compromised in a browsing
session such as by a Javascript virus in Google ads on Youtube, closing
that Tor Browser and opening a new one will result in it using a fresh,
non-compromised disposable VM.

Buying items through Tor means using your real identity through Tor. Some
people use Tor for everything including banking. Some use Tor for all
browsing except anything involving their real identity. Others just use
Tor occasionally for some sites. Try searching tor-users mailing list for
questions similar to yours; you'll need to develop your own answer.


-- 
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/b292931916dfcf1b30f1eff3d6524640.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Mac Spoofing preinstalled? - Qubes 4 rc4

2018-03-03 Thread Chris Laprise 

On 03/03/2018 02:21 AM, Tristan Fleming wrote:

Has mac spoofing been preinstalled in Q4 rc4? I cant find any documentation on 
it, but the cmd: ip link show wls1

changes every 10 minutes or so. I actually want to stop it and I cant seem to 
make it static. Lil help!!

Ive tried everything I can think of. Im not entirely understanding the network 
topology.

I have figured out that Macchanger is installed on the Debian Template. Im 
otherwise at a loss.



Its not a Qubes feature. When wifi is not connected to an AP, its now 
the Network Manager and wpa_supplicant default to randomize the mac 
address. The mac address shouldn't change while you're connected though.


Here are a couple links:

https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/

https://www.qubes-os.org/doc/anonymizing-your-mac-address/

If you haven't tried already, it sounds like you want to change the 
wifi.scan-rand-mac-address setting.



--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
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/35a718d0-92d8-5134-8de9-9fbfe77cc3a1%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes R3.2 Failed to Load Kernel Modules

2018-03-03 Thread 'awokd' via qubes-users 
On Fri, March 2, 2018 3:44 am, alternateg...@gmail.com wrote:
> I have the same issue, except Qubes fails to install on my Dell Latitude
> E6410.  This was the second machine I was unable to install Qubes on, and
> this one I purchased specifically because I saw it on the Hardware
> Compatibility List.  My system also presumably met the core requirements
> on site.  I get stuck at sys-net in the latter part of installation
> process post-GRUB.  systemd-modules-load.service will not load in
> recovery mode.  Machine is a Dell Latitude E6410, Core i5 2.4ghz, 4 GB
> DDR3 ram.  If Qubes worked I would love to join the community, right now
> seems it's still in alpha stages.  Help would surely be appreciated.

Did you see the notes by the entries for that laptop on the HCL? For
example, one says you need to disable hyperthreading on i5. Have you tried
that?


-- 
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/e2eef7b070f9a57dff7ae2053791245f.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: how to use email securely in qubes? thunderbird doesn't send messages

2018-03-03 Thread ThierryIT 
Le vendredi 2 mars 2018 14:00:18 UTC+2, jer...@disroot.org a écrit :
> 1 email or multiple emails.
> says sending message when clicking send (stuck) in thunderbird.

I am using thunderbird and enigmail on a StandaloneVM.
What OS are you using ? Have you check your FW rules if you have any ?

-- 
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/5ac1dd1e-d1fe-4b58-b4ce-36618b4a830d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Migrating to second hard drive

2018-03-03 Thread ThierryIT 
Le vendredi 2 mars 2018 11:26:03 UTC+2, Unman a écrit :
> On Fri, Mar 02, 2018 at 04:10:24AM -, 'awokd' via qubes-users wrote:
> > On Fri, March 2, 2018 3:38 am, Glen H wrote:
> > > On Thursday, March 1, 2018 at 10:37:26 PM UTC-5, Glen H wrote:
> > >
> > >> Hi,
> > >>
> > >>
> > >> My primary SSD is out of space and I have a second hard drive.  I've
> > >> formatted it but not sure how to migrate my cubes to it.  Does anyone
> > >> have any instructions for doing this?
> > >>
> > >> Ideally, I'd boot from my new hard drive and use original one to store
> > >> my backups of my qubes.
> > >>
> > >> Thanks,
> > >>
> > >>
> > >> Glen
> > >>
> > >
> > > I forgot to mention that I'm on Qubes 4 and I'm pretty knowledgeable
> > > about Linux.
> > 
> > Make sure you do a backup first. You might be able to "cheat" and DD the
> > small drive to the larger then expand, as long as you're comfortable with
> > LVM. On the other hand, pulling the small drive, installing Qubes on the
> > new, and restoring from backup wouldn't take that much longer.
> 
> If you cheat you'll have to fix grub if you're using it. I suspect it'll
> be cleaner to take the second option and install 4.0 on the new drive
> when it comes out.

What about doing a backup of all your VMs / template first.
Doing a fresh install of Qubes on your new HDD.
Restored your backuped VMs 

?

-- 
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/06a0bb91-54c6-41e2-8a4f-e2de6ab886a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.