Re: [qubes-users] Networking with debian10-minimal instead of fedora-33

2021-07-11 Thread Sven Semmler

On 7/11/21 3:23 PM, 799 wrote:

Not sure if there is a big benefit using Debian over Fedora 33 but I would
like to hear if there is a benefit.


Personally I like that once I setup a Debian qube, it'll run and receive 
security updates for many years. I haven't looked up how quickly a 
Fedora qube EOLs but it 'feels' like year, maybe 18 months.


It kind of depends what you want from your setup. I've reached a point 
where I have plenty of stuff to do and don't want to deal with things 
like updates and changing interfaces any more than necessary. Don't get 
me wrong: I thoroughly enjoyed the learning curve and setting everything 
up, but now that it works I enjoy not having to think about it all the time.


/Sven

--
 public key: https://www.svensemmler.org/2A632C537D744BC7.asc
fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5abc-e046-8397-a061-de75bc976e50%40SvenSemmler.org.


OpenPGP_signature
Description: OpenPGP digital signature


Re: [qubes-users] Disposable sys-net >> wifi login

2021-07-11 Thread Sven Semmler

Hi one7two99,

there is another way.

Your sys-net is a named disposable VM, which is based on an AppVM that 
has the "template_for_dispvm" property set true. This AppVM is in turn 
based on your fedora-33-minimal clone.


The reason you have an AppVM as template for disposable VMs is the 
ability to do customization. So here is what I do:


AppVM:

1) set virt_mode to 'hvm'
2) attach wifi via qvm-pci
3) launch
4) connect to wifi (this will safe the password)
5) shutdown
6) detach wifi
7) set virt_mode to 'pvh'

sys-net:

1) attach the wifi again
2) start

... from now on your sys-net will automatically connect to your Wifi. I 
do this for my home wifi and my hotspot.


/Sven

--
 public key: https://www.svensemmler.org/2A632C537D744BC7.asc
fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/73960ab5-788c-c515-8923-311abb9e65ad%40SvenSemmler.org.


OpenPGP_signature
Description: OpenPGP digital signature


Re: [qubes-users] Disposable sys-net >> wifi login

2021-07-11 Thread 'awokd' via qubes-users

'awokd' via qubes-users:


Possibly an nmcli command run in the disposable template could do that?


Disposable sys-net, I mean.

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e3abbf40-a362-96d9-774a-8d1a39a42aed%40danwin1210.me.


Re: [qubes-users] Disposable sys-net >> wifi login

2021-07-11 Thread 'awokd' via qubes-users

799:


I also would like to make my sys-net a disposable VM but without the hazzle
to enter my wifi credentials each time when I am connecting to the wifi
network.


There's this from a recent thread: 
https://www.mail-archive.com/qubes-users@googlegroups.com/msg36839.html.




Is there a way to initiate a wifi connection via dom0 and passing the
credentials for the wifi network?
qvm-run --pass-io --auto sys-net 'command1 && commands && [...] command n'
with passing credentials via piping from Dom0 ?
Basically I am looking how I can initiate a new wifi connection from the
CLI.


Possibly an nmcli command run in the disposable template could do that?

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ed41bc3c-ad6a-1e10-32ac-a5b1a4b4791d%40danwin1210.me.


Re: [qubes-users] Networking with debian10-minimal instead of fedora-33

2021-07-11 Thread 799
Hello,

Steve Coleman  schrieb am Do., 1. Juli 2021

> I don't have any suggestion for the Debian issue, but what I do to limit
> the updates is clone the fedora-33-minimal to a template called
> fedora-33-net, strip out any apps not needed, and then use that for my
> networking AppVM's. With fewer apps there are far fewer updates to deal
> with.
>

Not sure if there is a big benefit using Debian over Fedora 33 but I would
like to hear if there is a benefit.
I am using my own "minimalized" Templates which are build from a
fedora-33-minimal template.
You can find more about my templates here:
https://github.com/one7two99/my-qubes/blob/master/my-qubes-templates/20%20template-sys-vms.md

The template will work for sys-net / sys-firewall / sys-usb and also for a
vpn-qube.
I don't see that updating my fedora-based template takes much longer than
my debian templates.

One7two99

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAJ3yz2unSCN8HAKaK_zrYXNSoS5TKaoj67PD2%3D7NHr_eCZSKPQ%40mail.gmail.com.


Re: [qubes-users] Question related to Qubes Updater of dom0

2021-07-11 Thread Viktor Ransmayr
unman schrieb am Sonntag, 11. Juli 2021 um 12:52:51 UTC+2:

> On Sun, Jul 11, 2021 at 01:13:04AM -0700, Viktor Ransmayr wrote: 
> > Can you please elaborate a bit more! - What were you looking for? 
>
> I was looking for a problem with the update process. 
> There has been a long thread in the forum about why you should use the 
> updated tool instead of updating locally. In brief, it's used to apply 
> other things (e.g. configuration changes) besides raw updates. 
>

Looks like I should subscribe to the new forum !

> 
> > - Why is 'qubes updater' notified in the first place, if nothing needs 
> > to be done? - OR - 
> > 
> > 
> > - If something got done 'locally', why isn't at least a minimal 
> > information about the performed activity returned? 
> > 
> > This inconsistency / uncertainty is confusing (at least to me ). 
>
> Because the updater does more than just update, it is possible that 
> there are things not applied. 
>
> What's the situation here? What Qubes version are you on? 


Qubes version is 4.0 - for more info I've attached the info from
'qubes manager' below.
 

> Do you mean 
> that dom0 is always marked a requiring updates in the updater tool?
>

No, not always. - But lately multiple updates have been requested for
dom-0, which I performed - but- the system did not provide any change
info ...

Is it still showing that updates are required? 
>

No, currently there is no notification active about a required update for
dom-0.

With kind regards,

Viktor



xen_version: 4.8.5-34.fc25
Linux 5.4.125-1.fc25.qubes.x86_64
  
Installed Packages:  
  
kernel-qubes-vm.x86_64
1000:5.4.107-1.fc25.qubes 
kernel-qubes-vm.x86_64
1000:5.4.120-1.fc25.qubes 
kernel-qubes-vm.x86_64
1000:5.4.125-1.fc25.qubes 
python2-qubesadmin.noarch 4.0.32-1.fc25 
python2-qubesimgconverter.x86_64  4.0.31-1.fc25 
python3-qubesadmin.noarch 4.0.32-1.fc25 
python3-qubesdb.x86_644.0.16-1.fc25 
python3-qubesimgconverter.x86_64  4.0.34-1.fc25 
qubes-anaconda-addon.noarch   4.0.11-1.fc25 
qubes-artwork.noarch  4.0.1-2.fc25 
qubes-core-admin-addon-whonix.noarch  4.0.2-1.fc25 
qubes-core-admin-client.noarch4.0.32-1.fc25 
qubes-core-dom0.x86_644.0.58-1.fc25 
qubes-core-dom0-linux.x86_64  4.0.30-1.fc25 
qubes-core-dom0-linux-kernel-install.x86_64
qubes-db.x86_64   4.0.16-1.fc25 
qubes-db-dom0.x86_64  4.0.16-1.fc25 
qubes-db-libs.x86_64  4.0.16-1.fc25 
qubes-desktop-linux-common.noarch 4.0.22-1.fc25 
qubes-desktop-linux-manager.noarch4.0.25-1.fc25 
qubes-gpg-split-dom0.x86_64   2.0.50-1.fc25 
qubes-gui-dom0.x86_64 4.0.13-1.fc25 
qubes-img-converter-dom0.x86_64   1.2.10-1.fc25 
qubes-input-proxy.x86_64  1.0.23-1.fc25 
qubes-input-proxy-receiver.x86_64 1.0.23-1.fc25 
qubes-libvchan-xen.x86_64 4.0.9-1.fc25 
qubes-manager.noarch  4.0.45-1.fc25 
qubes-menus.noarch4.0.22-1.fc25 
qubes-mgmt-salt.noarch4.0.26-1.fc25 
qubes-mgmt-salt-admin-tools.noarch4.0.26-1.fc25 
qubes-mgmt-salt-base.noarch   4.0.4-1.fc25 
qubes-mgmt-salt-base-config.noarch4.0.2-1.fc25 
qubes-mgmt-salt-base-overrides.noarch 4.0.2-1.fc25 
qubes-mgmt-salt-base-overrides-libs.noarch 
qubes-mgmt-salt-base-topd.noarch  4.0.2-1.fc25 
qubes-mgmt-salt-config.noarch 4.0.26-1.fc25 
qubes-mgmt-salt-dom0.noarch   4.0.26-1.fc25 
qubes-mgmt-salt-dom0-qvm.noarch   4.0.10-1.fc25 
qubes-mgmt-salt-dom0-update.noarch4.0.10-1.fc25 
qubes-mgmt-salt-dom0-virtual-machines.noarch   
qubes-pdf-converter-dom0.x86_64   2.1.12-1.fc25 
qubes-release.noarch  4.0-10 
qubes-release-notes.noarch4.0-10 
qubes-rpm-oxide.x86_640.2.2-1.fc25 
qubes-template-debian-10.noarch   4.0.1-201910230150 
qubes-template-fedora-33.noarch   4.0.6-202012100255 
qubes-template-whonix-gw-15.noarch4.0.1-202003070901 
qubes-template-whonix-ws-15.noarch4.0.1-202003070901 
qubes-usb-proxy-dom0.noarch   1.0.30-1.fc25 
qubes-utils.x86_64 

[qubes-users] Disposable sys-net >> wifi login

2021-07-11 Thread 799
Hello,

I switches my setup and I am using static disposable VMs for sys-usb and
sys-firewall (Based on an own template which has been cloned from a
fedora-33-minimal template + the bare minimal packages).

I also would like to make my sys-net a disposable VM but without the hazzle
to enter my wifi credentials each time when I am connecting to the wifi
network.

Is there a way to initiate a wifi connection via dom0 and passing the
credentials for the wifi network?
qvm-run --pass-io --auto sys-net 'command1 && commands && [...] command n'
with passing credentials via piping from Dom0 ?
Basically I am looking how I can initiate a new wifi connection from the
CLI.
If I know this, I can combine a script myself which will pass the relevant
information from Dom0 to the sys-net.

And one more question:
Wouldn't it be much better if we always use disposable.sys-Vms when this is
possible?

Kind regards

one7two99

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAJ3yz2tvAAiLjvLLnuwAFt8BquSoDE-WZDbZPyszZz%3D8orNs%2BQ%40mail.gmail.com.


Re: [qubes-users] Question related to Qubes Updater of dom0

2021-07-11 Thread unman
On Sun, Jul 11, 2021 at 01:13:04AM -0700, Viktor Ransmayr wrote:
> Hello unman,
> 
> unman schrieb am Samstag, 10. Juli 2021 um 16:57:43 UTC+2:
> 
> > Looks good to me 
> >
> 
> Can you please elaborate a bit more! - What were you looking for?

I was looking for a problem with the update process.
There has been a long thread in the forum about why you should use the
updated tool instead of updating locally. In brief, it's used to apply
other things (e.g. configuration changes) besides raw updates.

> 
>- Why is 'qubes updater' notified in the first place, if nothing needs 
>to be done? - OR -
>
> 
>- If something got done 'locally', why isn't at least a minimal 
>information about the performed activity returned?
> 
> This inconsistency / uncertainty is confusing (at least to me ).

Because the updater does more than just update, it is possible that
there are things not applied.

What's the situation here? What Qubes version are you on? Do you mean
that dom0 is always marked a requiring updates in the updater tool?
Is it still showing that updates are required?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20210711105246.GA9877%40thirdeyesecurity.org.


Re: [qubes-users] Question related to Qubes Updater of dom0

2021-07-11 Thread Viktor Ransmayr
Hello unman,

unman schrieb am Samstag, 10. Juli 2021 um 16:57:43 UTC+2:

> Looks good to me 
>

Can you please elaborate a bit more! - What were you looking for?

   - Why is 'qubes updater' notified in the first place, if nothing needs 
   to be done? - OR -
   

   - If something got done 'locally', why isn't at least a minimal 
   information about the performed activity returned?

This inconsistency / uncertainty is confusing (at least to me ).

With kind regards,

Viktor

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b57c9589-9d33-4e4c-afa7-c1556364268fn%40googlegroups.com.