Re: [qubes-users] Re: FYI: Kernel Hardening; a discussion (2018)

[sevas]

I looked at that. Its a pretty cool direction. I had read some article that
said they were teaming up with a provider that offered end-to-end encryption
so you get the whole kit and caboodle. I wanted to install something less 
offensive on my galaxy, but it turns out Verizon phones are trash and cant even 
unlock the bootloader. 

Purism is also doing cool phone stuff. A phone run on linux. So you can install 
whatever OS you want. And a screen handling program to resize everything. They
also are working on the end-to-end angle. 

I was unaware of the narrow options for kernel hardening and the drama. Just 
part of my research and 

-- 
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/1f6fec55-0f31-45f7-9fa5-3b86b8cbe581%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: FYI: Kernel Hardening; a discussion (2018)

[Tim W]

On Sunday, March 11, 2018 at 8:11:57 PM UTC-4, awokd wrote:
> On Sun, March 11, 2018 5:49 pm, sevas wrote:
> > I did not mean to go so far south with the above statements. So heres my
> > additions for alternatives...
> >
> > CopperheadOS is doing a project still early in the making on reawakening
> > the open source kernel hardening. The GitHub page can be found here:
> > https://github.com/copperhead/linux-hardened/issues
> >
> >
> > ...which are limited.
> 
> I agree, it's disappointing grsecurity couldn't figure out a better way to
> handle that.
> 
> You might find this interesting, though:
> http://roscidus.com/blog/blog/2016/01/01/a-unikernel-firewall-for-qubesos/

Yeh I recall when it was all coming to a head over on their forum.   They tried 
IIRC legal action and pressure and costs were going to be debilitating thus I 
think that  is why they did what they did.  In fact I think in the end all they 
were looking for was recognition it was their code being used.  It was some 
time ago and I might not be recollecting it all.  But it was a big deal.


I really like the guys that make up copperhead.  They also did what they had to 
keep the doors open and viable for their android os version.  I paid the fee 
for the pixel to have them load to give my support to them.  Soon they should 
have pixel 2 all done and I will pay them again to have it on a pixel 2.  They 
strike a great balance for me between secure and usable.  They do good work IMO.

Cheers,

Tim

-- 
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/ff804a13-9b03-49a6-8d0f-e64966f6ffa6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: trouble with qubes-builder

[Tim W]

On Saturday, March 10, 2018 at 6:01:25 PM UTC-5, Tim W wrote:
> When I try to build anything with qubes-builder I keep getting an error when 
> its verifying tags.  Specifically this error below:
> 
> -> Updating sources for builder...
>│  
> │ --> Fetching from https://github.com/QubesOS/qubes-builder.git 
> master... │  
> │ --> Verifying tags...   
>  │  
> │ No valid signed tag found!  
>  │  
> │ ---> One of invalid tag:
>  │  
> │ object 9674c1991deef45b1a1b1c71fddfab14ba50dccf 
>  │  
> │ type commit 
>  │  
> │ tag mm_9674c199 
>  │  
> │ tagger Marek Marczykowski-Górecki 
>  1520035393 +0100
>  │  
> │ 
>  │  
> │ Tag for commit 9674c1991deef45b1a1b1c71fddfab14ba50dccf 
>  │  
> │ Makefile:194: recipe for target 'builder.get-sources' failed 
> 
> 
> None of this happened until Marek posted: 
> Announcement/warning: verification of git tag signatures in qubes-builder
> https://groups.google.com/forum/#!topic/qubes-devel/UyjsvvPzApI 
> 
> I first followed the directions to verify the sigs but after the error.  I 
> deleted qubes-builder and all the gpg sig keys.  Redownloaded the keys  and 
> installed qubes-builder and copied the keys over to it.
> 
> Now everytime I run any build when it gets-sources I get this error.  If I 
> continue to picking templates now the whonix template options are gone.
> 
> What is the reason for the missing tag? 
> 
> I am running this from a FC23 template.  It has worked fine for months 
> building 3.2 4.0 ISO as well as a number of templates.  This only happened 
> recently.
> 
> Marek commented but I do not really understand his comment as I followed the 
> directions in the thread and it all showed correctly.
> 
> Cheers,
> 
> Tim

Wow no one?

Can anyone check and see if they try to use qubes-builder after downloading all 
the sign keys.

-- 
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/1006aacc-c4bf-4d16-95c0-c5a125ae1f6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Custom resolutions-xrandr

[Yuraeitha]

On Monday, March 12, 2018 at 5:30:29 AM UTC+1, randal...@gmail.com wrote:
> Did that solve the black bar issue? Also I'm the so called average user so I 
> would need a small step by step guide cause this looks super confusing.
> Thanks an advance

Google hates me tonight, but I'll try again. For some reason google kept 
deleting my messages some hours back, but my last message got through, so maybe 
this one will too. Seemingly my situation isn't an isolated case either. But 
anyway, lets get on-topic (and hope this successfully posts this time).

Use this command "xrandr" in dom0 terminal to find the supported resolutions on 
your machine, as well as the screens exact name. The exat name is important. 
For example my screens name is eDP1, but you put eDP-1 in your command. Is your 
screen really named that and not eDP1? It might explain partly why it doesn't 
work. Run "xrandr" in dom0 terminal, nothing else, just that one command. It'll 
give you a print out of all connected screens, supported resolutions and screen 
names.

Also, this is a working command, I use it my self daily. 
xrandr --output eDP1 --mode 1920x1080 

Remember to only put a resolution that your setup supports. Even supported 
resolutions can look bad though, so try aim for one with proper proportions. 
Most normal setups support 1920x1080, if you can see it in the list, then yours 
also support it, in that case give that one a try to begin with. Remember to 
double check your screen's name, even a single letter difference can make it 
stop working.

First test the command in dom0 terminal, if it works, and you found your ideal 
settings, then you can turn it into a script, which afterwards can be either 
keybinded, autostarted, or turned into a shortcut (whichever you prefer most).

in a clean dom0, type this (no sudo here!) 
nano screen-resolution-script.sh 

Terminal becomes an editor, now just write this exact command into your window, 
modified with the values (resolution and screen name) that fits your system. 

The Nano editor can be saved by "ctrl+x", keep eyes on window as you do this, 
ans you'll notice the message at bottom. Something like 2Do you want to save?" 
Press Y for yes, and accept the name you gave it earlier with enter. 

Now your script is located in dom0 at 
/home/your-user-name/screen-resolution-script.sh 

In order to make it executeable, write this in dom0 terminal 
chmod +x screen-resolution-script.sh 

Now, for example keybind it, type this in dom0 again
xfce4-keyboard-settings 

a window will popup, go to the "Application Shortcuts" and click the add 
button. Now add the path to your script, and bind a key. 

I gotta hurry running now, so I cant explain the other two approaches right 
now. But it's quickly done 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/5cb20f4f-71ab-4ee7-a0d6-c8242aa647ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Custom resolutions-xrandr

[Yuraeitha]

On Saturday, March 10, 2018 at 9:21:41 PM UTC+1, randal...@gmail.com wrote:
> If im trying to create a custom resolution that I can auctually see on my 
> 3200x1800 how do I get rid of the black area and make the resolution full 
> screen? I tried adding xrandr --output eDP-1 set "scaling mode" "full aspect" 
> and nothing is happening.I allready made a resolution of 1800x1400, but 
> instead of going full it just shrinks the display to fit into a box.

Careful with running resolutions that are not supported by your graphic card. 
Try run just "xrandr" in dom0, it'll print out all your supported resolutions.

First confirm in dom0 terminal if it works, then make a script that you can 
keybind, autostart, or turn into an icon shortcut. Put it like this;

"xrandr --output eDP1 --mode 1920x1080"

Above resolution is an example, change it to one your card supports. Also the 
same command that finds your supported resolutions, also tells you your 
screen's name. Be sure you got the screen name correct, it will only work if 
you do it precisely. For example, are you sure it's not eDP1 instead of eDP-1? 
It can also be named something else entirely, i.e. HDMI3, you need to confirm 
to be sure.

-- 
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/7c02927b-02c6-4d35-bd7b-e97048a5a904%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes won't boot "kernel panic", where is AppVm data?

[Yuraeitha]

On Sunday, March 11, 2018 at 11:03:02 PM UTC+1, ale10...@gmail.com wrote:
> Hello, I am currently locked out of my qubes system because of a "kernel 
> panic" error I encounter when I boot the system, after the grub screen. I 
> don't really know what to do. 
> The only thing I did before this to happen is to try to install AEM (without 
> success), it may be the reason for this.
> Is there any fix to this? I still have my qubes installation media, I can run 
> the troubleshooting mode. I have qubes R4-rc4. 
> I am also searching for the place to search for my appvms data so I can 
> backup them and then re-install qubes (I use qubes for some months now), I 
> can't find the appvm data anywhere... thanks for your answers !

I recommend you don't delete anything before you made sure it works. Maybe 
backup the whole drive, or pull a copy of all data on it to another drive. Just 
to be safe. 

I also recommend you wait a bit for more answers, there may be ways to save 
your system yet.

Your AppVM data should be saved here;
/var/lib/qubes/appvms/

Your Templates data should be saved here; 
/var/lib/qubes/vm-templates

In general have a look at the base folder
/var/lib/qubes/

I never did a rescue this way, so I don't know if this is sufficient. But I 
believe it is all you need, and then you can create new AppVM's with the same 
name (important, must be same names), and then just drag and drop the AppVM 
files in there.

But it's best you have the confirmation of someone who's done this before, 
however, this should at least get you started. Your system may also be rescued 
if someone knows how to fix it. By any chance, did you try use Grub to boot a 
different older kernel? By default Qubes (and other modern *nix's) save up to 3 
kernels at a time. So you should have 2 older kernels. Maybe they work better 
with AEM? 

-- 
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/f2eca4ca-40a0-48b3-bc4a-6e6c01a4c07e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: anyone else get hit by google's auto-deleting qubes users mail responses the moment they are send?

[Yuraeitha]

On Monday, March 12, 2018 at 7:55:35 AM UTC+1, [ 799 ] wrote:
> Hello,
> 
> 
> 
> Am 12.03.2018 7:40 vorm. schrieb "Yuraeitha" :
> This is getting ridiculousness, another two posts automatically removed 
> straight after or shortly after posting, it's inhuman speeds, it is certainly 
> google-bots pretty censorship handy-work non normal content/language.
> 
> 
> 
> Honestly I haven't understand why Qubes Team is hosting it's Mailinglist on 
> Google.
> 
> 
> [...] Google collects and maintains information about your account activity, 
> including the groups that you join or manage, lists of other members or 
> invitees in the groups, messages or topics you track, custom pages you create 
> or edit, ratings you make, and your preferred settings when using Google 
> Groups [...]
> 
> 
> I am sure that there are solutions where a Mailinglist can be hosted and as 
> others have suggested maybe run a forum.
> 
> 
> Maybe https://savannah.gnu.org/ ?
> 
> 
> [799]

Could the reason maybe be because it has little overhead and maintenance? Goals 
and environment may have changed over the years too. Though of course other 
mail services can do the same too, but were there alternatives around at the 
time they made this? I have no idea, but I think it might be because it was 
more efficient when they were busy building Qubes for the first time, and maybe 
google just stuck since then? 

Savannah looks interesting, so far it looks like a really great alternative. 
Maybe we can do some in-depth research on it and draft an argument for and 
against such a move and present it? Once all the other things we got running 
settles a bit of course.

But at any rate, getting rid of google would be very satisfying though, I'm 
getting more and more salty with them, and more so as the years go by. I only 
use this mail account for google mail-lists btw (if anyone wonders, though I 
should probably get rid of this gmail even so, I'm gettind fed up with google 
so I might end up doing that soon at any rate).

-- 
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/b63865c5-4f20-44ee-bf1c-2a52f045c7df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes won't boot "kernel panic", where is AppVm data?

[Yuraeitha]

On Sunday, March 11, 2018 at 11:03:02 PM UTC+1, ale10...@gmail.com wrote:
> Hello, I am currently locked out of my qubes system because of a "kernel 
> panic" error I encounter when I boot the system, after the grub screen. I 
> don't really know what to do. 
> The only thing I did before this to happen is to try to install AEM (without 
> success), it may be the reason for this.
> Is there any fix to this? I still have my qubes installation media, I can run 
> the troubleshooting mode. I have qubes R4-rc4. 
> I am also searching for the place to search for my appvms data so I can 
> backup them and then re-install qubes (I use qubes for some months now), I 
> can't find the appvm data anywhere... thanks for your answers !

it seems google is having fun with me and auto-deletes messages as I reply... 
given the number of deleted messages we're seeing lately, maybe I'm not the 
only one having this google issue...

well, I'll try again. Try look here for your AppVM's
/var/lib/qubes/appvms 

and here for your templates
/var/lib/qubes/vm-templates 

and in general /var/lib/qubes/ for anything VM related.

I'm not sure if you can restore it all this way, I haven't done this before my 
self. It might be a good idea to wait for confirmation from someone who's done 
it before, or wait and don't delete/overwrite anything before you got 
confirmation on this method. 

However, I believe the approach is to copy this folder /var/lib/qubes and then 
create identical named VM's, shut them down, and then systematically and 
manually replace the VM's data. Be mindful that this "might" be a bad idea to 
do for templates, it's probably best you only do it with AppVM's. 

Also there may still be a way to save your system rather than salvaging, for 
example did you try load the other 2 kernels? (normal 3 kernels are kept at any 
time and Grub should be able to switch between them).

-- 
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/9065f687-5a8e-4319-82e5-2e72c4a9577c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: off topic - invite codes to 'riseup'

[Tim W]

On Saturday, March 10, 2018 at 9:38:38 AM UTC-5, little help wrote:
> On Wednesday, March 7, 2018 at 8:11:25 PM UTC+1, Tim W wrote:
> > I am sorry what is reason so many people want to get and use a riseup.net 
> > account outside political or some other social reason
> > 
> > They had their canary down for over a year because of gag order from the 
> > feds.
> > 
> > They have totally rewritten there canary statement since which was prior 
> > very clear and concise.  Now it looks to be heavily lawyered careful play 
> > on words...thus its vague using words that can having wide varying meaning. 
> >  what is omitted is any speech with the words warrant, gag order, NSL.  If 
> > they get any of those it will NOT of itself require them activating the 
> > canary protocol.
> > 
> > Here is their old Canary statement followed by the new one:
> > 
> > OLD:
> > riseup has not received any National Security Letters or FISA court orders, 
> > and we have not been subject to any gag order by a FISA court, or any other 
> > similar court of any government. Riseup has never placed any backdoors in 
> > our hardware or software and has not received any requests to do so. Riseup 
> > has never disclosed any user communications to any third party.
> > 
> > 
> > NEW:
> > Riseup positively confirms that the integrity of our system is sound. all 
> > our infrastructure is in our control, we have not been compromised or 
> > suffered a data breach, we have not disclosed any private encryption keys, 
> > and we have not been forced to modify our system to allow access or 
> > information leakage to a third party.
> > 
> > 
> > Unfortunately we cannot use common sense to read these but they must be 
> > read thru the eye of a laywer  I think you really see the effects of the 
> > rewritten statement. 
> > 
> > From what I can tell the system is closed source.  They no longer offer any 
> > form of encryption.  I must all be done on your email client.  There is no 
> > two factor authentication.  The user name and password to get your into 
> > your mailbox from what I can see maybe moot as there is no info on any use 
> > of encryption outside users manually or thru a client using gpg.  If that 
> > is correct then any mail not gpg encrypted is sitting in the mailbox in 
> > cleartext.  Unless there is something like AES 256 protecting the mailbox 
> > via your password but then that means thru the recovery passcode system 
> > they very well can get back into your mailbox even with lost credentials 
> > and no reset alternate email address.
> > 
> > For a person that plans to gpg encrypt all their emails what does this 
> > offer anyone over the other free email accounts.  Sure your contacts are 
> > not mined to hell and back but in terms of email content I see no 
> > difference and actually lower login security.
> > 
> > I was looking at the thread and it looks like around 40 people requested 
> > referral codes on this thread while the canary was expired.  One person 
> > even mentioned it and it went uncommented on.
> > 
> > Compare this to say protonmail its not even remotely close.  As both can be 
> > had for free and without all the need for referrals as its targeted toward 
> > liberal/social/anticapital political change groups not sure the point?  
> > Elitism?
> > 
> > I honestly was surprised so many people on this list asking for it and 
> > where unphase by the fact the canary was expired and it was known they were 
> > under a gag order.  We make a big deal about a close source binary blob for 
> > a driver or firmware to a nic or gpu yet a closed source email provider 
> > system with a triggered canary and no one misses a beat?  I know the thread 
> > was off topic and has been running for years and why I never even read it 
> > till now for no other reason than I was wasting time but wow I am surprised.
> 
> 
> 
> Yeah your concerns are legitimate.
> I guess they changed canary to make it more usable. Old one was a bit awkward 
> since due to warrant they were not able to update it or comment anything 
> about it.
> New one doesn't cover subpoenas and gag orders, but only covers 
> infrastructure they control and are always free to comment on.
> So new canary is not as reassuring as old one, but new one will not cause 
> this 6 months old radio silence when users didn't know what is going on.
> 
> Btw old gag order and investigation was because of some cryto blackmailing. I 
> think I found this somewhere on riseup canary pages.
> 
> You are right there is nothing else than username and password protecting 
> your account. But this is the same for every other non two factor 
> authentication account. And two factor isn't perfect either.
> And they are as far I know closed source so you just have to trust them. 
> Which is again same as majority of other email providers.
> 
> You mentioned that "They no longer offer any form of encryption."
> This is not true. After that gag order debacle they introduced 

Re: [qubes-users] Qubes and Whonix now have next-generation Tor onion services!

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-03-12 02:26, Gaijin wrote:
> On 2018-02-12 01:47, Andrew David Wong wrote:
>> On 2018-02-11 18:57, Gaijin wrote:
>>
>>> The Qubes OS v3 and v2 onion services sites don't appear to have been
>>> updated since January when this announcement was made. Shouldn't they
>>> show the same content as the normal Qubes site?
>>>
>>> For example I don't see the news of the 4.0-rc4 release, or recent
>>> changes to the Docs.
>>>
>>
>> Thanks for the report! Tracking:
>>
>> https://github.com/QubesOS/qubes-issues/issues/1352#issuecomment-364812018
>> 
> 
> FYI: The Onion sites are still not syncing with the Qubes site. They're
> still stuck in January 2018...
> 

Bumped/poked fortasse and CCed Patrick (in case fortasse is known to be
traveling or something):

https://github.com/QubesOS/qubes-issues/issues/1352#issuecomment-372525929

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqnOBkACgkQ203TvDlQ
MDDJVBAAvjBN0wOF6XwPhWZZ5TkUWrqc529ZTSdwK6QWywfG0yCMjW/RFGBrh0kB
1b+9BDjw/Gj7fWQEDXBGnaNB1zyRVJLwe23viOSGKiY7Ln0ni/kn53By4x4ljXcy
IFdMEBIAkZYpqS/VKnwrBi36aF7Vl4/FC+06710e9ia+oyWFzs3pH2yLom7WPvvi
qud0xm+EswfnGGKMI4CWP6bEiKjo3YIHQm2Eb3IfMoUNNy892pG/nV/kFHOn9jNu
ue3fH1p8N87D4OyAIaostdP49bpXygIJtC/hObD7pD1+39t5Y5e4XQ4SkfrM3o+q
Mq3Ax6gMFtYslA5ccZEZs7vVszIUmSW9gQ5QwpOQf709OXC7XW9qsP0s6fp1Gh97
2ECq4Q7Ze3ROAP31y6jTI181g18iU9GOJB0VDtuQUD7UTc3xs05O9akpmhhzjHi+
M7j8b8jOfK+davJfnwPH7UQMZ7doQl0myt1GtmyebPbxXBkrlMKSwvnmzLu/JYw1
RPYAd+kgvEv4Tj2MAL/v/Gp2/nZdZx4vakJePUSATQ3QiNNWstezHsZ6/fS4pRDq
M5V76slv6fdVLRXhqtGewVrUFCgf36mhgMpX4/owMa1ZLfua0rlnQ3qrhdA+PTUC
4CAodHZLYQ+Gn/pMs54xZEDW8ec+BKCpLhFkTuQ0sddhimZbKpU=
=VJWO
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ac2d0443-a1b4-488a-7d43-7c0551aed801%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] tcp/udp server on qubes

['awokd' via qubes-users]

On Mon, March 12, 2018 10:21 pm, idanqu...@gmail.com wrote:
> I'm trying to build a server that uses tcp protocol, and I'm having
> trouble figuring the firewall rules that I need to set in order to
> connect the server so it would be able to communicate with a specific
> client through the internet.
>
> I'm aware that there is the guide for networking and firewall:
> https://www.qubes-os.org/doc/firewall/
>
>
> but unfortunately I cant infer it to my use case.

Not sure what you mean- Qubes doesn't need any special rules to
communicate out. If you want to restrict inbound communications to the
single source IP of your client, follow the guide and use that IP in the
rule. I think there's an example like that in there.


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

Re: [qubes-users] Re: FYI: Kernel Hardening; a discussion (2018)

[sevas]

I do find that very interesting and Ive saved the website for further 
investigation a little later. Thanks for 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/a44f5a0d-3618-4a64-befc-c2129b33179f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] dom0 memory allocation (Qubes Manager default memory settings)

[sevas]

Im looking around at dom0 memory management.

I found some Xen server stuff that has equations for 
figuring your mem mgmt. 

Is allocation important?
It must be. 
When they say memory, theyre talking about ram, right? Not HDD memory? Thats a 
stupid question, of course they are. 

dom0_mem = 502 + int(physical_mem * 0.0205)
   2 GB 543 MB
   4 GB 585 MB
   8 GB 669 MB
  16 GB 837 MB
  32 GB 1173 MB
  64 GB 1845 MB
 128 GB 3188 MB
 256 GB 5875 MB 
 512 GB 11249 MB
1024 GB 21997 MB
2048 GB 43493 MB 

I upgraded my ram from 2 to 16.
So Qubes was installed with 2gigs of ram. I set qubes up while I waited for the 
ram to arrive.  

So I need to update Qubes Manager and all the VMs, right?

Currently, I have 
Minimal qube memory: 134MB
dom0 memory boost: 236MB

So Im changing this to dom0=837 and 469...

Good or nah?

-- 
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/9db8d495-fe49-46aa-b797-126334f1b984%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Q3.2 backup to AppVM , how to restore if can't boot Qubes ?

[socks]

Q3.2 backup to AppVM , how to restore if can't boot Qubes ?


I see the procedures in the docs URL, which seem to pertain to folks 
whom have backed up to a USB device. But, somehow I can't imagine how it 
would work to restore the Qubes system from an AppVM (where I am using 
as the location


for my current backups) 


Is backing up to a removable USB device then  the suggested best practice ?

--
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/02f9276b-d250-0df4-8ba2-eb16f708f9e0%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: tcp/udp server on qubes

[idanqubes]

just to be clear I'm using Qubes R3.2

-- 
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/7a5b8490-80e9-481d-84f0-547be74f359c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] tcp/udp server on qubes

[idanqubes]

I'm trying to build a server that uses tcp protocol, and I'm having trouble 
figuring the firewall rules that I need to set in order to connect the server 
so it would be able to communicate with a specific client through the internet.

I'm aware that there is the guide for networking and firewall:
https://www.qubes-os.org/doc/firewall/

but unfortunately I cant infer it to my use case.

-- 
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/e539598f-6bd7-4f28-9bb2-c8f3fabcc7d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Howto: Enable WWAN (LTE Sierra EM7345) in Qubes OS (Howto install ModemManager in Qubes)

[799]

Hello,

On 12 March 2018 at 20:38, akiraloopback via qubes-users <
qubes-users@googlegroups.com> wrote:

> Maybe. No. I just installed sys-usb now, delegating the LTE device to
> sys-net:
> [root@dom0 ~]# qubesctl state.sls qvm.sys-usb
> [user@dom0 ~]$ qvm-usb -a sys-net sys-usb:4-10
>
> Seems to work well.


happy to heat, that you made it work.
For some reason sometimes the exalt USB ID changes (example same device
which was sys-usb:4-10 before is then sys-usb:5-10).
I have thereof written a small helper script which will attach the
WWAN-card based on the name:

#!/bin/bash
# Attaches internal LTE-Card to sys-net
qvm-usb attach sys-net `qvm-usb | grep H5321 | gawk '{ print $1 }'`

You might need to change H5321 in your case so that the string is within
the description of your WWAN card.

[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/CAJ3yz2s-L7hkgxeQMQ48Xq-ZypuRDOQJfR%2Bn6%2ByXTXXLj-97qg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Howto: Enable WWAN (LTE Sierra EM7345) in Qubes OS (Howto install ModemManager in Qubes)

[akiraloopback via qubes-users]

Maybe. No. I just installed sys-usb now, delegating the LTE device to sys-net:
[root@dom0 ~]# qubesctl state.sls qvm.sys-usb
[user@dom0 ~]$ qvm-usb -a sys-net sys-usb:4-10

Seems to work well.

-- 
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/bcd10672-4241-4b50-946e-e71466f4656e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Howto: Enable WWAN (LTE Sierra EM7345) in Qubes OS (Howto install ModemManager in Qubes)

['awokd' via qubes-users]

On Mon, March 12, 2018 5:40 pm, akiraloopback via qubes-users wrote:
>> As you might guess all other USB devices that are connected to the same
>> Bus / same USB-Controller will also be "lost" to the sys-net VM.
>> On the Lenovo W540 notebook this means that 3 out of 4 USB ports are
>> passed through to sys-net. If you enable USB3 in the BIOS you will even
>> loose all 4 USB ports to sys-net. I have disabled USB3 in the BIOS and
>> will use a USB3-PCMCIA Express Card to have USB3 available if I need it
>> (as suggested in another thread)
>>
>
> On a T540p, I loose all USB ports to sys-net, making the whole notebook
> quite unusable, since you cannot connect mice or disks any more.
>
> Everything seems to be on one bus (003):

If I understand the theory right, if you disable the strict-reset
requirement you should still be able to assign different devices on the
same bus to different VMs. 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/ce87a2635f06fa628d838bfa63c078ed.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DNS propagation in Qubes

[David Hobach]

On 03/11/2018 03:15 PM, David Hobach wrote:
An alternative might be to setup the local DNS service in a VM closer to 
the Internet, i.e. not in the proxy VM which also implements the qubes 
firewall.


Something like
Internet <-- sys-net <-- sys-firewall <-- DNS server VM <-- proxy VM 
with qubes-fw <-- client VM


I didn't test that though.


I just tested that as well now and it works as expected without any of 
the aforementioned caveats.


So I'd recommend the one above over the previously discussed
Internet <-- sys-net <-- sys-firewall <-- DNS server VM <-- client VM
(at least I was talking about that architecture - maybe the others were 
talking about something different...).

The same holds true for VPN users.

I also documented this at 
https://github.com/QubesOS/qubes-issues/issues/3051


--
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/b1482304-c9c8-11d6-c988-4adcc737380b%40hackingthe.net.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [qubes-users] Howto: Enable WWAN (LTE Sierra EM7345) in Qubes OS (Howto install ModemManager in Qubes)

[akiraloopback via qubes-users]

> As you might guess all other USB devices that are connected to the same Bus / 
> same USB-Controller will also be "lost" to the sys-net VM.
> On the Lenovo W540 notebook this means that 3 out of 4 USB ports are passed 
> through to sys-net.
> If you enable USB3 in the BIOS you will even loose all 4 USB ports to 
> sys-net. I have disabled USB3 in the BIOS and will use a USB3-PCMCIA Express 
> Card to have USB3 available if I need it (as suggested in another thread)

On a T540p, I loose all USB ports to sys-net, making the whole notebook quite 
unusable, since you cannot connect mice or disks any more.

Everything seems to be on one bus (003):

[user@dom0 ~]$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 17ef:1010 Lenovo 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 008: ID 046d:c526 Logitech, Inc. Nano Receiver
Bus 003 Device 006: ID 17ef:100f Lenovo 
Bus 003 Device 004: ID 17ef:1010 Lenovo 
Bus 003 Device 003: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
Bus 003 Device 002: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
Bus 003 Device 009: ID 5986:026a Acer, Inc 
Bus 003 Device 007: ID 8087:07da Intel Corp. 
Bus 003 Device 005: ID 1199:a001 Sierra Wireless, Inc. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[user@dom0 ~]$ readlink /sys/bus/usb/devices/usb?
../../../devices/pci:00/:00:1a.0/usb1
../../../devices/pci:00/:00:1d.0/usb2
../../../devices/pci:00/:00:14.0/usb3
../../../devices/pci:00/:00:14.0/usb4

[user@dom0 ~]$ lspci | grep USB
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 04)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 04)

Why do you have to disable USB3 in BIOS?
And what about bus 001 and 002, where may they be connected to?

If I delegate device 00:14.0 to sys-net, I cannot use any physical USB port in 
dom0 any more.

-- 
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/2582ea99-5891-4626-a935-3e6e1d117a36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4rc5 + win7 HVM :: Can't resize Windows

[799]

Hello,

After a fresh installation of Qubes 4rc5 I provisioned a new win7 HVM from
scratch.
As I had detailed notes from my prior I installation this was mostly copy
and paste and the win7 is running including Qubes Windows Tools + seamless
mode.

The only but annoying problem is, that I can't resize windows as the window
is always running maximized.

Under Qubes 3.2 it was possible to resize Windows in seamless mode, if I
can only run full-size windows there is not much benefit running seamless
mode.
Has something changed from Q3.2 to Q4? Or is it something like a bug with
QWT under Q4?

[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/CAJ3yz2spvmnj6SdgE3S4K3UyGm2-D5%2B7Luyg6%3D1J_-kfhN4fzw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: anyone else get hit by google's auto-deleting qubes users mail responses the moment they are send?

[Steve Coleman]

I would say that if somebody has such an email in their out box, and you 
know it was removed, then contact Google and resolve the issue rather 
than just complaining here. No offense meant by this, its just that you 
have exactly what they need to tack down the problem sitting in your 
outbox. How on earth would they benefit by randomly deleting your mail 
on purpose? Their business it learning about you, to better market you, 
not pissing people off. Deleting legitimate information about you and 
what you like to talk about is exactly what they want to keep on file. 
Deleting it make so sense in their business model.


The explanation I would offer is their infantile 
data-collecting/spam-eliminating AI filter has been mistrained, and 
needs to be slapped silly by a human and corrected. The problem we have 
is that much of the "logic" they use these days is due to machine 
learning algorithms that one can not even ask the model why it did 
something completely stupid. It's merely the result of it learning the 
wrong logic from what data we gave it during the "training process".


There was once a DoD contractor who jumped on the AI bandwagon back in 
the 70's, who trained the system to pick out tanks hiding in camouflage. 
It did great, so they wanted to show the top brass. Before doing so they 
took new photographs because the old ones were quite worn, and the new 
photos flunked the test. What the system learned was cloudy vs sunny 
days, not tanks and no-tanks. Filtering emails based on the same "logic" 
is bound to have its problems.


So, don't attribute to malice where it can be the result of complete 
incompetents in machine learning. This unfortunately is the reality of 
the 'new software' era we now live in. Make them get it right if you 
disapprove.


btw - If this email response to you disappears then I will want answers 
from them myself. The more people who point out actual instances of 
missing legitimate emails, the sooner they will be forced to reevaluate 
their own methods of verification of this kind of ML mistraining.



On 03/12/18 02:55, 799 wrote:

Hello,

Am 12.03.2018 7:40 vorm. schrieb "Yuraeitha" >:


This is getting ridiculousness, another two posts automatically
removed straight after or shortly after posting, it's inhuman
speeds, it is certainly google-bots pretty censorship handy-work non
normal content/language.


Honestly I haven't understand why Qubes Team is hosting it's Mailinglist 
on Google.


[...] Google collects and maintains information about your account 
activity, including the groups that you join or manage, lists of other 
members or invitees in the groups, messages or topics you track, custom 
pages you create or edit, ratings you make, and your preferred settings 
when using Google Groups [...]


I am sure that there are solutions where a Mailinglist can be hosted and 
as others have suggested maybe run a forum.


Maybe https://savannah.gnu.org/ ?

[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/CAJ3yz2vqmL64MVPVOLkfeJKRNYsi24Do6Dzgs%2BkcnxX3CWdvHw%40mail.gmail.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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/e29f3ed9-e704-9cce-4397-504e5aa85947%40jhuapl.edu.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Boot Qubes 4.0 r5 / Try to start an old VM ...

[ThierryIT]

who does not exist anymore during the boot sequence 
Any idea on how to deal with this ?

thx

-- 
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/ad536013-fbb9-47ce-b4fc-e2cf3f9e02d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] bash autocomplete

[brendan . hoar]

On Sunday, March 11, 2018 at 9:11:07 AM UTC-4, haaber wrote:
> Thank you Holger,
> I don't know what this 3D-thing, is I'll learn it. I have, in the
> meanwhile, tested the attached file, that distinguishes also running,
> paused and halted VM's. For the moment this is completely sufficient for
> me. Maybe I'll add the completion "root" when I complete "qvm-run -u",
> since this is what I need for updating sudo-less minimal templates :)
> 
> I put the file it in /etc/bash_completion.d/ within dom0, and source it
> in .bashrc.   Bernhard

FYI, I noticed a qvmhall instead of a qvmall on one of the lines in your 
script, just FYI.

Brendan

-- 
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/c7aa48ef-aca1-4b35-bed1-19e7b5d8550e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] DNS propagation in Qubes

[Alex Dubois]

Sent from my mobile phone.

> On 11 Mar 2018, at 10:21, Chris Laprise  wrote:
> 
>> On 03/10/2018 04:43 PM, Alex Dubois wrote:
>>> On Saturday, 10 March 2018 13:16:37 UTC, Micah Lee  wrote:
>>> ‐‐‐ Original Message ‐‐‐
>>> 
 On March 8, 2018 11:26 AM, Chris Laprise  wrote:
 
 ​​
 
>>> \> \[1\] https://dnsprivacy.org/wiki/
 
 \[2\] https://www.qubes-os.org/doc/networking/
 
 Micah,
 
 If you have any specific instructions on how to setup the forwarder
 
 you're using, I'd be happy to try it myself and post a solution for use
 
 with qubes-firewall.
 
 I found the dnsprivacy wiki to be a bit scattered and not very specific.
 
 Their video "tutorial" is really a lecture on the concept.
>>> 
>>> Thanks, yes I'd love to share instructions. I haven't gotten it working yet 
>>> -- I'm traveling right now and haven't spent a lot of time on it, and might 
>>> not for the next week or two. But once I figure it out I'd like to write a 
>>> blog post or something with instructions. But maybe I should sent it to 
>>> this list first for people to test and give feedback.
>> For your info, I have a wiki on how to use dns-crypt here: 
>> https://github.com/adubois/adubois.github.io/blob/master/_posts/2013-11-19-setup-dnscrypt-unbound.md
>> It is supposed to be exposed via blog.bowabos.com but github changed 
>> something and the static site does not get automatically generated at the 
>> moment...
> 
> Nice. I gave this a try on debian-9, using apt to install dnscrypt-proxy and 
> unbound.
> 
> One problem is that the howto assumes particular Qubes 10.137.2.x and 
> 10.138.2.x nets for unbound.

Yes I need to rewrite it for Qubes 4.

The other blog post on Atlassian stack also needs a rewrite and I have now a 
better network topology (more secure) for it. Time is my problem

> 
> Another problem is that on Qubes 4.0 the vif interfaces plus eth0 all share 
> the same IP address. This isn't explained in the Qubes networking or firewall 
> docs, so it may be a bug...
> 
> To keep unbound.service from failing I changed unbound.conf to this:
> 
>> interface: 
>> access-control: 10.137.0.0/24 allow
>> harden-large-queries: yes
>> private-address: 10.0.0.0/8
>> private-address: 192.168.0.0/16
>> val-permissive-mode: yes
>> do-not-query-localhost: no
> 
> ...and for now omitted the '-d' destination part in iptables.
> 
> Then if I issue:
> 
>> sudo iptables -t nat -F PR-QBS
>> sudo iptables -t nat -A PR-QBS  -i vif+ -p udp --dport 53 -j DNAT --to 
>> $eth0_address
>> sudo iptables -t nat -A PR-QBS  -i vif+ -p tcp --dport 53 -j DNAT --to 
>> $eth0_address
> 
> it appears to work from a downstream appVM. But I haven't checked yet to see 
> if its really using the dnscrypt proxy; even if it is, the config may need to 
> be adjusted for better security.
> 
> -- 
> 
> 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/8ECF3140-FD4B-400C-AB7D-A459F74327AC%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes and Whonix now have next-generation Tor onion services!

[Gaijin]

On 2018-02-12 01:47, Andrew David Wong wrote:
> On 2018-02-11 18:57, Gaijin wrote:
> 
>> The Qubes OS v3 and v2 onion services sites don't appear to have been
>> updated since January when this announcement was made. Shouldn't they
>> show the same content as the normal Qubes site?
>>
>> For example I don't see the news of the 4.0-rc4 release, or recent
>> changes to the Docs.
>>
> 
> Thanks for the report! Tracking:
> 
> https://github.com/QubesOS/qubes-issues/issues/1352#issuecomment-364812018
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org


FYI: The Onion sites are still not syncing with the Qubes site. They're
still stuck in January 2018...

-- 
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/c56b5c1d344eeb12b4a69fc3b0975145%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: anyone else get hit by google's auto-deleting qubes users mail responses the moment they are send?

[799]

Hello,

Am 12.03.2018 7:40 vorm. schrieb "Yuraeitha" :

This is getting ridiculousness, another two posts automatically removed
straight after or shortly after posting, it's inhuman speeds, it is
certainly google-bots pretty censorship handy-work non normal
content/language.


Honestly I haven't understand why Qubes Team is hosting it's Mailinglist on
Google.

[...] Google collects and maintains information about your account
activity, including the groups that you join or manage, lists of other
members or invitees in the groups, messages or topics you track, custom
pages you create or edit, ratings you make, and your preferred settings
when using Google Groups [...]

I am sure that there are solutions where a Mailinglist can be hosted and as
others have suggested maybe run a forum.

Maybe https://savannah.gnu.org/ ?

[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/CAJ3yz2vqmL64MVPVOLkfeJKRNYsi24Do6Dzgs%2BkcnxX3CWdvHw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: anyone else get hit by google's auto-deleting qubes users mail responses the moment they are send?

[Yuraeitha]

This is getting ridiculousness, another two posts automatically removed 
straight after or shortly after posting, it's inhuman speeds, it is certainly 
google-bots pretty censorship handy-work non normal content/language. 

https://groups.google.com/forum/#!topic/qubes-users/oZnaHZROW0c

If I can post here again now, for some reason, this thread is immune. Maybe 
it's because I hosted the original mail... either way, google... yeah, I'm lost 
for words.

-- 
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/9cb69ee8-baa4-4f35-a4f7-f476ec716c4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.