Try drop on issues like previous.
Timeout file too big?
Timeout password entry taking too long while unattended?
Not sure yet. Haven’t seen the error. The script just runs the command for convince. Same should happen on manual execution. Should be possible to copy/paste same command. What’s wrong with the command? Ask upstream?
This command I quoted unrecognized by gpg-agent and cripples any gpg operations.
Can’t work since that config file looks obviously invalid.
“pinentry-qt /usr/bin/pinentrynno-grabndefault-cache-ttl 7200”
Shouldn’t use sudo since file location in user owned location. Best to delete ~/.gnupg/gpg-agent.conf and recreate with proper permissions and owned by user.
Used this with same consequences Turns out you can ignore the cache completely and go ahead with the signing. Will drop the sudo and start again:
echo -e “pinentry-program /usr/bin/pinentry-qt\nno-grab\nignore-cache-for-signing\nmax-cache-ttl 7200” | sudo tee ~/.gnupg/gpg-agent.conf
Anyway I ran the most simplified version of the signing command manually in attempt to forget about the prepare release script. Ended up timing out. There must be something else screwing this up:
user@host:~/whonix_binary$ gpg --detach-sign --armor *.libvirt.xz
gpg: signing failed: Timeout
gpg: signing failed: Timeout
Done at last. Uploaded. Up and running on my end with all the wiki instructions tested and working.
I ended up pressing ‘c’ to override the errors and it worked, signing everything and producing valid sigs.
The command for gpg-agent for reference though I’m not sue it helped is:
echo -e “pinentry-program /usr/bin/pinentry-qt\nno-grab\nignore-cache-for-signing\nmax-cache-ttl 7200\npinentry-timeout 86400” | tee ~/.gnupg/gpg-agent.conf
You might want to add signify-openbsd as a build dep for the dev guide if you haven’t already.
So far so good. Beautiful theme. I like how users are advised to select highest sec on TBB first run. Amazing stuff. Will put out a new release notice at some point today.
sudo or not.
The usage of
\n (which is included in that command) does not work.
Please look at the resulting configuration file and check if it looks as intended. It doesn’t.
The forum software is formatting my quotes into the italic type that would indeed not give proper formatting but the ones I used on my end were the normal ones.
Please use code tags for code, not quote. Like this:
Mistake with video setting in GW, kicksecure and custom WS prevents them form starting.
Removed rombar off because having it enabled for more than 1 NIC caused the GW to freak out
Question: Are we already providing Kicksecure releases?
I’ll do another build once accepted since 184.108.40.206.8 includes these problems. I don’t see the point of linking to that build now.
Life would be easier if users actually bothered testing these things and reported back…
A post was merged into an existing topic: AppArmor for Complete System - Including init, PID1, Systemd, Everything! - Full System MAC policy
3 posts were merged into an existing topic: use sudoedit in Whonix documentation and Whonix software
@Patrick just noticed xpdf silently fails to run when trying to open a pdf in 220.127.116.11.6
can you reproduce that? Any logs needed?
Scratch that, the file is malformed