[qubes-users] How to qvm-copy FROM a win 7 appvm?

[xyzo]

I can use qvm-copy-to-vm to copy files to win7vm. But how do copy FROM win 7 to 
another appvm? 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/090b621c-57c3-406e-b0ec-08af588d8259o%40googlegroups.com.

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[brendan . hoar]

On Sunday, June 7, 2020 at 12:29:28 PM UTC-4, Andrew Sullivan wrote:
...

On the fedora-based VMs, the tool `gnome-disks` is a gui way of manually 
mounting filesystems.

[I tend to forget the order of operations and/or flags for things like 
mount (which is the mountpoint? which is the source device?) so either 
script it or use GUI tools when my brain is a bit fuzzy.]

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/230048f2-5bb9-469b-8e0c-153285ad37e9o%40googlegroups.com.

Re: [qubes-users] Re: Replacing SSD with larger SSD on Qubes System

[a]

On 2020-06-07 08:06, TheGardner wrote:

Did this in the past with a

- clon of the entire (smaller) in Tails - Drives on a extern backup
dive

- replace the old drive with the new one
- and extend the written partition later up to 1TB

A fresh install is also a way. Just backup all your VMs and restore
them later on the new system. I -for myself- would do such a new
install / rename all new and fresh vms to somewhat "original-x"
and then restore the backup.
So you have your old system beside fresh installed original cubes from
a actual Qbs installation.

Am Samstag, 6. Juni 2020 21:27:32 UTC+2 schrieb Verifiable List:


Hello All,

I'm a long-time user of Qubes. I'm upgrading my laptop from a 256GB
SSD
to a 1TB SSD. I wanted to check whether it is preferable to clone
the
existing drive to the new one and expand the volumes, or whether I
should do a fresh Qubes install on the new drive and restore from
backup. I've not had great luck with Qubes' restore process in the
past,
but it's been a long time since I've needed to use it. Also, if the
fresh install/restore method is preferable, should I install Qubes
with
the "Do not configure anything" option checked so that none of the
default VMs are created?

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 view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/6e032ee9-bdaf-4fc4-9668-b0c5b7e091dao%40googlegroups.com
[1].


Links:
--
[1] 
https://groups.google.com/d/msgid/qubes-users/6e032ee9-bdaf-4fc4-9668-b0c5b7e091dao%40googlegroups.com?utm_medium=email_source=footer



Restoring from backup would be my preference, but it doesn't seem to 
work. It fails immediately. After restoring multiple VMs failed, I 
attempted to restore *only* a template VM. These are the resulting 
errors from journalctl (any help would be greatly appreciated):


Jun 07 16:36:44 dom0 qubesd[2664]: Creating directory: 
/var/lib/qubes/vm-templates/fedora-30
Jun 07 16:36:44 dom0 qubesd[2664]: unhandled exception while calling 
src=b'dom0' meth=b'admin.vm.volume.Info' dest=b'fedora-30' arg=b'kernel' 
len(untrusted_payload)=0

Jun 07 16:36:44 dom0 qubesd[2664]: Traceback (most recent call last):
Jun 07 16:36:44 dom0 qubesd[2664]:   File 
"/usr/lib/python3.5/site-packages/qubes/__init__.py", line 227, in 
__get__
Jun 07 16:36:44 dom0 qubesd[2664]: return getattr(instance, 
self._attr_name)
Jun 07 16:36:44 dom0 qubesd[2664]: AttributeError: 'TemplateVM' object 
has no attribute '_qubesprop_kernel'
Jun 07 16:36:44 dom0 qubesd[2664]: During handling of the above 
exception, another exception occurred:

Jun 07 16:36:44 dom0 qubesd[2664]: Traceback (most recent call last):
Jun 07 16:36:44 dom0 qubesd[2664]:   File 
"/usr/lib/python3.5/site-packages/qubes/vm/qubesvm.py", line 128, in 
_func
Jun 07 16:36:44 dom0 qubesd[2664]: return getattr(self.template, 
prop)
Jun 07 16:36:44 dom0 qubesd[2664]: AttributeError: 'TemplateVM' object 
has no attribute 'template'
Jun 07 16:36:44 dom0 qubesd[2664]: During handling of the above 
exception, another exception occurred:

Jun 07 16:36:44 dom0 qubesd[2664]: Traceback (most recent call last):
Jun 07 16:36:44 dom0 qubesd[2664]:   File 
"/usr/lib/python3.5/site-packages/qubes/__init__.py", line 227, in 
__get__
Jun 07 16:36:44 dom0 qubesd[2664]: return getattr(instance, 
self._attr_name)
Jun 07 16:36:44 dom0 qubesd[2664]: AttributeError: 'Qubes' object has no 
attribute '_qubesprop_default_kernel'
Jun 07 16:36:44 dom0 qubesd[2664]: During handling of the above 
exception, another exception occurred:

Jun 07 16:36:44 dom0 qubesd[2664]: Traceback (most recent call last):
Jun 07 16:36:44 dom0 qubesd[2664]:   File 
"/usr/lib/python3.5/site-packages/qubes/api/__init__.py", line 275, in 
respond
Jun 07 16:36:44 dom0 qubesd[2664]: 
untrusted_payload=untrusted_payload)
Jun 07 16:36:44 dom0 qubesd[2664]:   File 
"/usr/lib64/python3.5/asyncio/futures.py", line 381, in __iter__
Jun 07 16:36:44 dom0 qubesd[2664]: yield self  # This tells Task to 
wait for completion.
Jun 07 16:36:44 dom0 qubesd[2664]:   File 
"/usr/lib64/python3.5/asyncio/tasks.py", line 310, in _wakeup

Jun 07 16:36:44 dom0 qubesd[2664]: future.result()
Jun 07 16:36:44 dom0 qubesd[2664]:   File 
"/usr/lib64/python3.5/asyncio/futures.py", line 294, in result

Jun 07 16:36:44 dom0 qubesd[2664]: raise self._exception
Jun 07 16:36:44 dom0 qubesd[2664]:   File 
"/usr/lib64/python3.5/asyncio/tasks.py", line 240, in _step

Jun 07 16:36:44 dom0 qubesd[2664]: result = coro.send(None)
Jun 07 16:36:44 dom0 qubesd[2664]:   File 
"/usr/lib64/python3.5/asyncio/coroutines.py", line 210, in coro

Jun 07 16:36:44 dom0 qubesd[2664]: res = func(*args, **kw)
Jun 07 16:36:44 dom0 qubesd[2664]:   File 
"/usr/lib/python3.5/site-packages/qubes/api/admin.py", line 349, in 

Re: [qubes-users] Re: Do you use Qubes OS as your main OS on primary PC? What kind of work do you get done on it?

[preilly40]

On 6/3/20 11:25 AM, Daniil Travnikov wrote:
> I know that this is kinda off topic. But what about Battery Runtime in
> your laptops? I mean is it the same in Qubes like in any other OS?
> I am asking because my laptop working in Ubuntu about 5 hours, but in
> Qubes only 1 hour. On any version till the last one - I started use it
> from 3.2.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 view this discussion on the web visit
> https://groups.google.com/d/msgid/qubes-users/d5a8f26b-7012-496a-9bf2-c8ca47380f9c%40googlegroups.com
> .

installing powertop in dom0 may help.  (sudo qubes-dom0-update powertop)



-- 
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/ab2c40c7-53b6-6f91-1831-7f8b10c10e25%40gmail.com.

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[Andrew Sullivan]

On Sunday, 7 June 2020 16:28:54 UTC+1, unman wrote:
>
> On Sun, Jun 07, 2020 at 04:04:25AM -0700, Andrew Sullivan wrote: 
> > 
> > 
> > On Sunday, 7 June 2020 07:12:23 UTC+1, haaber wrote: 
> > > 
> > > On 6/6/20 6:33 PM, Andrew Sullivan wrote: 
> > > > 
> > > > If you use qvm-block in dom0 can you see the 
> disk/partitions? 
> > > > 
> > > > 
> > > >   Don't know, I'll give it a try and post back. 
> > > > 
> > > > 
> > > > OK, if I click on the  Devices widget I can indeed see all the 
> > > > partitions on my internal SSD, with an arrow next to each.  If I 
> click 
> > > > the arrow I get a list of qubes, which I believe allows me to attach 
> the 
> > > > selected partition to where I want.  However, when I do this I can't 
> > > > find the partition in the Files application in the qube.  Think I'm 
> > > > still missing something...  Also, am I correct that this attachment 
> will 
> > > > only persist until I close the qube? 
> > > 
> > > they will be inserted in the appvm-qube as /dev/xvdi, /dev/xvdk ... 
> > > [vd = virtual device, I guess]. The existence of a device does not 
> mean 
> > > mounting it. I do that by hand: in a terminal, type 
> > > 
> > > sudo mount /dev/xvdi /media 
> > > 
> > > will mount the attached device to /media and allow file access. If it 
> is 
> > > a luks-encrypted system, do 
> > > 
> > > sudo crypsetup luksOpen  /dev/xvdi  MYSSDVOL 
> > > sudo mount  /dev/mapper/MYSSDVOL/media 
> > > 
> > > cheers 
> > > 
> > 
> > Many thanks for that, works exactly as described!  Seems a bit strange 
> that 
> > the partition isn't mounted at the time it was attached (not sure why 
> you'd 
> > want to attach it if you didn't plan to read or write to it?).   
> Anyways... 
>
> You may want to read/write *without* mounting - for example, when using 
> dd to write a disk image. 
>
> > 
> > Is there any way the attachment and mounting can be made permanent? 
> > 
>
> `man` is your friend - specifically `man qvm-block`. 
> You will see that there is indeed a `--persistent` option. 
>
> Mounting could be a simple (and standard) entry in /etc/fstab - nothing 
> Qubes 
> specific here. Or simply a call to `mount`. 
> Make sure that you use a good identifier - /dev/xvdi may or may not work 
> - a label or UUID would be much better. 
> Again `man fstab` and `man mount` will help. 
>
> The Qubes specific part will be to make sure that any changes you  make 
> to /etc/fstab are persistent - you could do this using bind-dirs or by 
> an entry in /rw/config/rc.local 
>
>
>
>
> > Next challenge - access files on another Linux laptop on the same 
> network! 
> > 
> > -- 
> > 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...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/da8f0bd7-8736-4e32-b64c-9721ab8fabaco%40googlegroups.com.
>  
>
>

Thanks, that's very helpful, I'll give it a try. 

-- 
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/bb4154fe-0d93-440c-bca5-49752b2e8214o%40googlegroups.com.

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[unman]

On Sun, Jun 07, 2020 at 04:04:25AM -0700, Andrew Sullivan wrote:
> 
> 
> On Sunday, 7 June 2020 07:12:23 UTC+1, haaber wrote:
> >
> > On 6/6/20 6:33 PM, Andrew Sullivan wrote: 
> > > 
> > > If you use qvm-block in dom0 can you see the disk/partitions? 
> > > 
> > > 
> > >   Don't know, I'll give it a try and post back. 
> > > 
> > > 
> > > OK, if I click on the  Devices widget I can indeed see all the 
> > > partitions on my internal SSD, with an arrow next to each.  If I click 
> > > the arrow I get a list of qubes, which I believe allows me to attach the 
> > > selected partition to where I want.  However, when I do this I can't 
> > > find the partition in the Files application in the qube.  Think I'm 
> > > still missing something...  Also, am I correct that this attachment will 
> > > only persist until I close the qube? 
> >
> > they will be inserted in the appvm-qube as /dev/xvdi, /dev/xvdk ... 
> > [vd = virtual device, I guess]. The existence of a device does not mean 
> > mounting it. I do that by hand: in a terminal, type 
> >
> > sudo mount /dev/xvdi /media 
> >
> > will mount the attached device to /media and allow file access. If it is 
> > a luks-encrypted system, do 
> >
> > sudo crypsetup luksOpen  /dev/xvdi  MYSSDVOL 
> > sudo mount  /dev/mapper/MYSSDVOL/media 
> >
> > cheers 
> >
> 
> Many thanks for that, works exactly as described!  Seems a bit strange that 
> the partition isn't mounted at the time it was attached (not sure why you'd 
> want to attach it if you didn't plan to read or write to it?).   Anyways...

You may want to read/write *without* mounting - for example, when using
dd to write a disk image.

> 
> Is there any way the attachment and mounting can be made permanent?
> 

`man` is your friend - specifically `man qvm-block`.
You will see that there is indeed a `--persistent` option.

Mounting could be a simple (and standard) entry in /etc/fstab - nothing Qubes
specific here. Or simply a call to `mount`.
Make sure that you use a good identifier - /dev/xvdi may or may not work
- a label or UUID would be much better.
Again `man fstab` and `man mount` will help.

The Qubes specific part will be to make sure that any changes you  make
to /etc/fstab are persistent - you could do this using bind-dirs or by
an entry in /rw/config/rc.local




> Next challenge - access files on another Linux laptop on the same network!
> 
> -- 
> 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/da8f0bd7-8736-4e32-b64c-9721ab8fabaco%40googlegroups.com.

-- 
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/20200607152850.GC14422%40thirdeyesecurity.org.

Re: [qubes-users] Has anyone tried pptp in qubes 4.0?

[unman]

On Sat, Jun 06, 2020 at 08:02:20PM +0200, onelovecisco via qubes-users wrote:
> And i forgot to tell you that pptp doesnt work from sys-net directly else. Do 
> you know why?
> Journalctl gives me a little info such like "Modem hangs up".So i cant?? 
> troubleshooting connection.
> >From another host it works good. Firewall doesnt block 1723 (telnet and ping 
> >to server works)
>  Nat_conntrack enabled in fedora template kernel.
> 
> 
> Jun 6, 2020, 17:51 by un...@thirdeyesecurity.org:
> 
> > On Thu, Jun 04, 2020 at 08:25:50PM +0200, 0rb via qubes-users wrote:
> >
> >> Telnet 1723 port works and i can ping server?? from 
> >> sys-net/sys-firewall/proxy-vm
> >> But connection can't be established from proxy-vm. Modem hangs if watch 
> >> journalctl | grep ppptp
> >>
> >> [user@sys-net ~]$ lsmod | grep pptp
> >> nf_nat_pptp?? 16384?? 0
> >> nf_nat_proto_gre 16384?? 1 nf_nat_pptp
> >> nf_conntrack_pptp?? 16384?? 1 nf_nat_pptp
> >> nf_conntrack_proto_gre?? 16384?? 1 nf_conntrack_pptp
> >> nf_nat 36864?? 5 
> >> nf_nat_ipv4,xt_nat,nf_nat_pptp,nf_nat_proto_gre,xt_REDIRECT
> >> nf_conntrack?? 163840?? 11 
> >> xt_conntrack,nf_nat,nft_ct,xt_state,nf_conntrack_pptp,ipt_MASQUERADE,nf_nat_ipv4,xt_nat,nf_nat_pptp,nf_conntrack_proto_gre,xt_REDIRECT
> >>
> >> Can anyone help how to use ppptp in QubesOS ?
> >>
> >> In 2016 Unman says
> >>
> >> First you need to allow INBOUND protocol 47:
> >> On sys-net:
> >> modprobe ip_conntrack_pptp
> >> modprobe ip_nat_pptp
> >> iptables -I FORWARD -p 47 -s ?? -j ACCEPT
> >>
> >> On proxyVM:
> >> iptables -I INPUT -p 47 -s  -j ACCEPT
> >>
> >> Now, zero the iptables counters, (using -Z), and try to start the vpn.
> >> You should see the counters incrementing both in sys-net and on the
> >> vpn proxy.
> >> If the connection fails look to see if any DROP rules are being
> >> triggered.
> >> By default PPTP uses tcp port 1723 so you could put in a rule to log
> >> that traffic :
> >> iptables -I FORWARD -p tcp --dport 1723 -j LOG
> >>
> >> But it doesnt solve the problem.
> >>
> >
> > 4 year old suggestions will rarely work in Qubes, but the principle is
> > good.
> > I don't use pptp myself, but have set this up for various users - a little
> > more information from your end would be useful.
> > Where are you trying to set up pptp connection from?
> > What does your Qubes netvm structure look like?
> > Have you set up firewall rules to allow INBOUND protocol 47?
> >


The convention here is not to top-post.
Please scroll to the bottom of the message before you start typing. Or
reply inline.
It only takes you seconds, makes it much easier to follow threads, and
cumulatively saves your fellow users hours.

Have you allowed inbound proto 47?
TCP port 1723 is the control connection, but the pptp tunnel is GRE -
that's PROTOCOL 47
It might be helpful if you post your firewall rules

unman

-- 
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/20200607151318.GB14422%40thirdeyesecurity.org.

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[Andrew Sullivan]

On Sunday, 7 June 2020 15:25:02 UTC+1, haaber wrote:
>
> On 6/7/20 1:04 PM, Andrew Sullivan wrote: 
> > 
> > 
> > On Sunday, 7 June 2020 07:12:23 UTC+1, haaber wrote: 
> > 
> > they will be inserted in the appvm-qube as /dev/xvdi, /dev/xvdk ... 
> > [vd = virtual device, I guess]. The existence of a device does not 
> mean 
> > mounting it. I do that by hand: in a terminal, type 
> > 
> >  sudo mount /dev/xvdi /media 
> > 
> > will mount the attached device to /media and allow file access. If 
> > it is 
> > a luks-encrypted system, do 
> > 
> >  sudo crypsetup luksOpen  /dev/xvdi  MYSSDVOL 
> >  sudo mount  /dev/mapper/MYSSDVOL/media 
> > 
> >  cheers 
> > 
> > 
> > Many thanks for that, works exactly as described!  Seems a bit strange 
> > that the partition isn't mounted at the time it was attached (not sure 
> > why you'd want to attach it if you didn't plan to read or write to 
> > it?).   Anyways... 
>
> like any device that lurks in your machine(say a WIN partition. Unless 
> you ask for mounting in fstab it won't be done. 
>
> > Is there any way the attachment and mounting can be made permanent? 
> no clue. never tried that. 
>
> > Next challenge - access files on another Linux laptop on the same 
> network! 
>
> use scp to copy individual files  and use 
>
> rsync -auv --rsh=ssh user@anotherlinuxmachine:path/  new-qubes-path/ 
>
> is your friend to mass-copy data. 
>

Thanks for that - useful to know but not exactly what I need right now.  I 
want to be able to access a folder on another Linux laptop on the same 
network (like I can access another disk in the same laptop).  I currently 
do this (in Linux Mint) using Samba.  I'll give that a try in Qubes and if 
I get problems I probably ought to start a new  thread (I got into trouble 
before when I raised a new topic in a thread...). 

-- 
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/89ec1490-5409-4b56-954c-17a370fe3b06o%40googlegroups.com.

Re: [qubes-users] Connect to wifi - settings doesnt load

[euroundusd via qubes-users]

@unman I installed your precompiled bionic template. I booted it with the 
options hvm and kernel=none and installed the backport-iwlwifi-dkms package 
inside. After that, I modified sys-net to use the template, again with the 
options hvm and kernel=none. I restarted the system and... The Problem is still 
there. The state of my wifi device is still switching between 'device not 
ready' and 'device not managed' and the dmesg output is the same as before. Did 
you do anything else to get this working? Do you have any idea how to fix this 
card issue without buying another one or recompiling the kernel? Thanks in 
advance

-- 
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/1ffa4fa4-3755-4b8b-ab9a-6c1fc2f3f3d7o%40googlegroups.com.

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[haaber]

On 6/7/20 1:04 PM, Andrew Sullivan wrote:



On Sunday, 7 June 2020 07:12:23 UTC+1, haaber wrote:

they will be inserted in the appvm-qube as /dev/xvdi, /dev/xvdk ...
[vd = virtual device, I guess]. The existence of a device does not mean
mounting it. I do that by hand: in a terminal, type

     sudo mount /dev/xvdi /media

will mount the attached device to /media and allow file access. If
it is
a luks-encrypted system, do

     sudo crypsetup luksOpen  /dev/xvdi  MYSSDVOL
     sudo mount  /dev/mapper/MYSSDVOL    /media

     cheers


Many thanks for that, works exactly as described!  Seems a bit strange
that the partition isn't mounted at the time it was attached (not sure
why you'd want to attach it if you didn't plan to read or write to
it?).   Anyways...


like any device that lurks in your machine(say a WIN partition. Unless
you ask for mounting in fstab it won't be done.


Is there any way the attachment and mounting can be made permanent?

no clue. never tried that.


Next challenge - access files on another Linux laptop on the same network!


use scp to copy individual files  and use

rsync -auv --rsh=ssh user@anotherlinuxmachine:path/  new-qubes-path/

is your friend to mass-copy data.

--
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/392f510b-512c-48aa-759a-09a9111d9698%40web.de.

Re: [qubes-users] SplitGPG with Subkeys Encryption Error

[unman]

On Sat, Jun 06, 2020 at 06:22:31PM -0700, Robert Spigler wrote:
> 
> 
> > > 
> >
> > Read my last message - you dont actually type the angle brackets 
> > This is simply a bash script, you can inspect for yourself: it's at 
> > /usr/bin/qubes-gpg-client-wrapper 
> >
> > I'm not sure I understand your clarification - in any case, use the 
> > command line I cited without the angle brackets. 
> >
> 
>  I tried your suggestion:
> 
> qubes-gpg-client-wrapper -r robertspig...@protonmail.ch --trusted-key 
> C2C60E279E86F10D5697782535CE0FE6C2141823 -e 
> '/home/user/Documents/Test_Encryption.txt' -o /home/user/Documents/Final.gpg
> 
> But with the error in terminal:
> 
> gpg: C2C60E279E86F10D5697782535CE0FE6C2141823 is not a valid long keyID
> 
> However, this time the qubes-gpg-client interface did pop up, as well as 
> the file Final.gpg being created (but it was empty).  Seems like we're 
> getting closer.  That definitely is the valid keyID, so I don't know what 
> is wrong.
> 

What is wrong is that you dont seem to understand the difference between
fingerprints and keyIDs.
fingerprint C2C60E279E86F10D5697782535CE0FE6C2141823
long keyID  35CE0FE6C2141823
short keyID C2141823

I've included "short" only for reference - dont use it.

-- 
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/20200607134715.GA14422%40thirdeyesecurity.org.

[qubes-users] Re: Replacing SSD with larger SSD on Qubes System

[TheGardner]

Did this in the past with a 
- clon of the entire (smaller) in Tails - Drives on a extern backup dive
- replace the old drive with the new one
- and extend the written partition later up to 1TB

A fresh install is also a way. Just backup all your VMs and restore them 
later on the new system. I -for myself- would do such a new install / 
rename all new and fresh vms to somewhat "original-x" and then restore 
the backup.
So you have your old system beside fresh installed original cubes from a 
actual Qbs installation.

Am Samstag, 6. Juni 2020 21:27:32 UTC+2 schrieb Verifiable List:
>
> Hello All, 
>
> I'm a long-time user of Qubes. I'm upgrading my laptop from a 256GB SSD 
> to a 1TB SSD. I wanted to check whether it is preferable to clone the 
> existing drive to the new one and expand the volumes, or whether I 
> should do a fresh Qubes install on the new drive and restore from 
> backup. I've not had great luck with Qubes' restore process in the past, 
> but it's been a long time since I've needed to use it. Also, if the 
> fresh install/restore method is preferable, should I install Qubes with 
> the "Do not configure anything" option checked so that none of the 
> default VMs are created? 
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/6e032ee9-bdaf-4fc4-9668-b0c5b7e091dao%40googlegroups.com.

Re: [EXT] [qubes-users] Libreoffice window sized tiny every time

[TheGardner]

This issue is in Fedora-32 too. There isn't currently a workaround, but 
from what I read in the last weeks, they're on it to fix that.

Am Freitag, 5. Juni 2020 23:18:16 UTC+2 schrieb Ulrich Windl:
>
> On 5/22/20 12:05 PM, qtpie wrote: 
> > Anyone else having this issue or know a solution? 
> > 
>
>

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

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[Andrew Sullivan]

On Sunday, 7 June 2020 07:12:23 UTC+1, haaber wrote:
>
> On 6/6/20 6:33 PM, Andrew Sullivan wrote: 
> > 
> > If you use qvm-block in dom0 can you see the disk/partitions? 
> > 
> > 
> >   Don't know, I'll give it a try and post back. 
> > 
> > 
> > OK, if I click on the  Devices widget I can indeed see all the 
> > partitions on my internal SSD, with an arrow next to each.  If I click 
> > the arrow I get a list of qubes, which I believe allows me to attach the 
> > selected partition to where I want.  However, when I do this I can't 
> > find the partition in the Files application in the qube.  Think I'm 
> > still missing something...  Also, am I correct that this attachment will 
> > only persist until I close the qube? 
>
> they will be inserted in the appvm-qube as /dev/xvdi, /dev/xvdk ... 
> [vd = virtual device, I guess]. The existence of a device does not mean 
> mounting it. I do that by hand: in a terminal, type 
>
> sudo mount /dev/xvdi /media 
>
> will mount the attached device to /media and allow file access. If it is 
> a luks-encrypted system, do 
>
> sudo crypsetup luksOpen  /dev/xvdi  MYSSDVOL 
> sudo mount  /dev/mapper/MYSSDVOL/media 
>
> cheers 
>

Many thanks for that, works exactly as described!  Seems a bit strange that 
the partition isn't mounted at the time it was attached (not sure why you'd 
want to attach it if you didn't plan to read or write to it?).   Anyways...

Is there any way the attachment and mounting can be made permanent?

Next challenge - access files on another Linux laptop on the same network!

-- 
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/da8f0bd7-8736-4e32-b64c-9721ab8fabaco%40googlegroups.com.

Re: [qubes-users] Accessing files on a different SSD on the same laptop...

[haaber]

On 6/6/20 6:33 PM, Andrew Sullivan wrote:


If you use qvm-block in dom0 can you see the disk/partitions?


      Don't know, I'll give it a try and post back.


OK, if I click on the  Devices widget I can indeed see all the
partitions on my internal SSD, with an arrow next to each.  If I click
the arrow I get a list of qubes, which I believe allows me to attach the
selected partition to where I want.  However, when I do this I can't
find the partition in the Files application in the qube.  Think I'm
still missing something...  Also, am I correct that this attachment will
only persist until I close the qube?


they will be inserted in the appvm-qube as /dev/xvdi, /dev/xvdk ...
[vd = virtual device, I guess]. The existence of a device does not mean
mounting it. I do that by hand: in a terminal, type

   sudo mount /dev/xvdi /media

will mount the attached device to /media and allow file access. If it is
a luks-encrypted system, do

   sudo crypsetup luksOpen  /dev/xvdi  MYSSDVOL
   sudo mount  /dev/mapper/MYSSDVOL/media

   cheers

--
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/6ab43a05-0672-d51d-1496-43a435d9cff9%40web.de.