*long day, missed the part where I blasted my old keyrings if step 3 fails:
sudo rm -rf /home/user/.local/share/keyrings
I had no saved passwords/keys but it was still an issue somehow, so this
forced the new first-time keyring password prompt on AppVM reboot that I
left blank. So apparently
libgnome-keyring, not just gnome-keyring.
Various forums suggest an issue (is there though?) in Fedora where PAM and
the gnome keyring do not play nice together and an additional theory that
the Fedora keyring is just not making Nextcloud entries due to some bug.
My current solution:
On Fri, 16 Aug 2019 at 11:22, Stefan Leibfarth wrote:
> I'd guess it's not directly Qubes related, maybe this problem:
I tried nearly everything from this forum post, I also tried
Am 15.08.2019 um 00:03 schrieb one7two99:
> I want to use a dedicated AppVM to sync data to a private NextCloud-Server.
> Can someone explain why I the login/sync fails after rebooting the AppVM?
> This are the steps to build a NextCloud-Client-Template and an AppVM
> based on
oh I am dumb, perhaps try logging in with your template vm, do the key
exchange, and then shut it down. It may stick into the appvm?
On Thursday, August 15, 2019 at 11:15:46 AM UTC-7, 799 wrote:
> *Null* ** > schrieb am Do., 15. Aug.
> 2019, 19:12:
>> OCC commands:
*Null* ** schrieb am Do., 15. Aug. 2019, 19:12:
> OCC commands:
Now I understand what you've meant, regarding the movement of directories.
This was related to
Oh yeah /home is saved too... I thought just /rw. It is advised on the
nextcloud hardening guide to not keep it in the default location and on my
setup I had to move it anyways because of how the machine is set up.
You received this message because you are subscribed to the Google Groups
In qubes you have to specify the file path to occ(in the docs it lets you call
occ by itself).
So for a typical fedora/apache/nc install in the template you would enter:
*Null* ** schrieb am Do., 15. Aug. 2019, 14:46:
> Sorry my initial reply was the wrong answer.
> To set up a login that is persistant you need to do it in the template
> with the occ commands. Any user made in the appvm will not survive a reboot.
What exactly is meant by "occ
Sorry my initial reply was the wrong answer.
To set up a login that is persistant you need to do it in the template with the
occ commands. Any user made in the appvm will not survive a reboot.
The nextcloud storage area needs to be made persistant using the
qubes-bind-dirs directory in the
Youve got to set up your user names in the template. So fire up httpd in your
template and use the occ commands to add users. Its inconvienent, but the appvm
non persistance is the secuity feature that is also preventing anyone from
embedding anything too nasty in your system.
I have tried to
I want to use a dedicated AppVM to sync data to a private NextCloud-Server.
I have setup a dedicated template for this, which is based on
fedore-30-minimal (as all my other templates).
Configuration of the template and the AppVM was straight forward and I
was able to make an initial
Mail list logo