s appear to be
> here:
> https://github.com/qubenix/qubes-whonix-bitcoin
>
> Comments for qubenix:
> - Some systems have limited disk space (e.g SSDs) so it may make sense
> to run a pruned node
That's true, but using a pruned bitcoind will limit its usefulness as a
backend f
t, then create an AppVM based on
> it networked to sys-whonix.
>
Don't need to install in a template. Just run a release in an AppVM.
--
qubenix
CODE PGP: FE7454228594B4DDD034CE73A95D4D197E922B20
EMAIL PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
IRC OTR: DFD1DA35 D74E775B 3E3DADB1
honix-next-gen-tor-onion-services/
>
> This announcement is also available on the Qubes website:
> https://www.qubes-os.org/news/2019/03/24/tor-onion-services-no-longer-maintained/
>
>
Wow, very sad. May I ask why so many extra resources are needed? Can't
you just install
OGBaby:
> Hey Qubenix, I have an update for you and anyone curious. The MDB_BAD_TXN
> error has been resolved. For anyone wondering this error most likely mean
> your blockchain was interrupted during sync and is now corrupt.
>
> The solution advised by Monero channe
eature exists in practice
> ;) Search back for the details.
>
>
I can't speak to the security risk from personal experience or
knowledge, but I found this:
https://security.stackexchange.com/questions/162122/gpu-passthrough-security/162175.
- --
qubenix
CODE PGP:
ew issue or you are out of space again (I think I remember
seeing that in one of your original mails iirc).
Either way it's not specific to your setup or to Qubes. Best to check on
Monero channels (reddit, irc, etc).
--
qubenix
CODE PGP: FE7454228594B4DDD034CE73A95D4D197E9
Is this normal behavior?
>
As I said, don't run the daemon from the command line. `systemd` is
handling it already.
--
qubenix
CODE PGP: FE7454228594B4DDD034CE73A95D4D197E922B20
EMAIL PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
IRC OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765
--
is a bit scattered however I completely
understand if you'd rather point me some links or resource instead. Any
more guidance is appreciated.
>
Try here for further reading:
https://ww.getmonero.org/resources/user-guides/.
--
qubenix
CODE PGP: FE7454228594B4DDD034CE73A95D4D197E922B20
EMAIL PG
e header (untested).
--
qubenix
CODE PGP: FE7454228594B4DDD034CE73A95D4D197E922B20
EMAIL PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
IRC OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765
--
You received this message because you are subscribed to the Google Groups
"qubes-users"
OGBaby:
> Thanks Qubenix,
>
> Wouldn't a fully synced daemon mean the blockchain is downloaded onto disk? I
> was under the impression a benefit to remote node over local was to entirely
> avoid downloading the blockchain.
>
> With the bootstrap-daemon address attempti
OGBaby:
> On Monday, December 10, 2018 at 5:16:01 PM UTC-6, qubenix wrote:
>> The best thing for you to do is:
>>
>> 1. Start the daemon's AppVM fresh.
>> 2. In a terminal on the daemon's vm do: `sudo tail -f
>> /home/monerod/.bitmonero/bitmonero.log`.
>&
OGBaby:
> Greatly appreciate your help Qubenix.
>
> I can confirm my systemd file (/lib/systemd/system/monerod-mainnet.service)
> matches yours now. I have removed the following to do so:
>
> ConditonPathExists=/var/run/qubes-service/monerod-mainnet
> After=
nything besides the daemon vm.
[1]:
https://github.com/monero-project/monero/issues/4468#issuecomment-429671939
--
qubenix
CODE PGP: FE7454228594B4DDD034CE73A95D4D197E922B20
EMAIL PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
IRC OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765
--
You received this
eresting.
>
>
> Achim Patzner
>
Good response to this flawed, ignorant study:
https://twitter.com/nic__carter/status/1056976815032582144.
--
qubenix
CODE PGP: FE7454228594B4DDD034CE73A95D4D197E922B20
EMAIL PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
IRC OTR: DFD1DA35 D74E775B 3E3DA
r version. For that you have to run
`tor --version` from the gateway.
You could also just do `cat /etc/whonix_version` from the workstation or
gateway for your Whonix version. I mention it because whonixcheck
produces output you don't need.
--
qubenix
CODE PGP: FE7454228594B4DDD034CE
ind of basic load-balancing measure.
--
qubenix
CODE PGP: FE7454228594B4DDD034CE73A95D4D197E922B20
EMAIL PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
IRC OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765
--
You received this message because you are subscribed to the Google Groups
"qubes-u
th, 2009.
>
Thank you for all your contributions. Your standards for security and
best practices have been an inspiration to me.
I wish you the best of luck and success in the future.
--
qubenix
PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
OTR: qube...@chat.freenode.net
OTR: DFD1DA35 D74
, that's very annoying.
>
> I checked the group and have not found anything helpful here. I don't think
> that this is a too uncommon problem? Any suggestions on how to solve it?
>
> Thanks a lot!
>
> Best regards,
> Bjoern
>
Off the top of my head: set ke
a way to have addons in a browser in a dispappvm and avoid
> this issue?
>
This should help you: https://www.qubes-os.org/doc/dispvm-customization/.
--
qubenix
PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
OTR: qube...@chat.freenode.net
OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765
--
't matter, only with systemd needs it) is
the best experience I've had with it on Whonix in years.
--
qubenix
PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
OTR: qube...@chat.freenode.net
OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765
--
You received this message because you are subscribed to t
qubenix:
> mk:
>> One last thing,
>>
>> It should be noted that I still had to remove option
>> "--p2p-bind-ip=127.0.0.1" to let monerod bind on 0.0.0.0 to make it work.
>>
>> Any security implication about this ? Does all traffic is still ro
when using Whonix gateway or binding p2p ip to 0.0.0.0 if not using a
Whonix gateway. Next I started to experience stalls, which I still
haven't found a solution for yet.
[1] https://github.com/monero-project/monero/issues/4468
[2] https://github.com/monero-project/monero/issues/4469
--
qubenix
P
mk:
> qubenix,
>
> I thought I had to run a full node to be synced with main blockchain but I
> now understand that running a local node is enough
>
> So everything works as expected,
>
> Thanks for you answer and clarification :)
>
It's still a full node bec
want to use sys-firewall you'll have to remove the
p2p-bind-ip=127.0.0.1 from the /lib/systemd/system/monerod.service file
on the TemplateVM. You will probably also have to allow the port forward
on your home router somehow.
--
qubenix
PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
OTR: qube...@chat
.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
> Thunderbird/60.0
> OS Linux 4.14.67-1.pvops.qubes.x86_64
>
>
>
Not sure why Enigmail is not recognizing the env var, but you could put
your gpg domain into the file /rw/config/gpg-split-domain as a
workaround. I use this method wit
is:
curl -s https://updates.signal.org/desktop/apt/keys.asc | sudo apt-key add -
This should work as expected, I just tested it.
--
qubenix
PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
OTR: qube...@chat.freenode.net
OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765
--
You received this me
the upgrade, and switched to
`stretch-proposed-updates` repo.
Don't forget you can always use `qvm-volume` to revert your template
changes (as long as you haven't restarted the vm since breaking it)
instead of reinstalling. See `qvm-volume --help` for details.
--
qubenix
PGP: 96096E4CA0870F1C5B
Hello all.
I'm attempting to build a custom Qubes with one patch added to Xen. Is
it enough to simply add the patch with the others in
qubes-builder/qubes-src/vmm-xen/, add a line for it in
qubes-builder/qubes-src/vmm-xen/xen.spec.in, and then build?
--
qubenix
PGP
to the following keys:
Andrew - BBAF910D1BC9DDF41043629FBC211FCEE9C54C53
Joanna - 49A322D9CA0D1D7DAEFA2AC63393D8BF0DDC6718
Marek - 86BA6E93318FBA446642A90ADB8FD31CCAD7D72C
--
qubenix
PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54
--
You received this message because you are subscribed to the Google Groups
e https://www.qubes-os.org/doc/tails/.
>>
>>
> technically this is a whonix question, I would suggest posting there :
>
> https://forums.whonix.org/
>
> or read their docs a bit 1st, then patrick and crew respond to most
> posts .
>
awokd:
> On Fri, May 11, 2018 2:56 am, qubenix wrote:
>> Hey everyone! Hope you are all doing well.
>>
>> I followed the guide here: https://www.qubes-os.org/doc/tips-and-tricks/
>> so links clicked in one debian-9 AppVM will open in separate debian-9
>> AppVM. Wha
, everything
works as expected. The link opens a new tab in the proper AppVM.
However, if firefox is not currently running, a clicked link will open
the link in a browser in both VMs.
Any ideas?
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
You received this message because you
llet.com/hc/en-us/articles/115005165269-What-to-do-if-my-Ledger-Nano-S-is-not-recognized-on-Windows-and-or-Linux-
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscri
qubenix:
> pauHana:
>> After completing the to VM setups and shutting them down is the intention
>> then to start monero-wallet-ws and interact with the wallet thru this vm as
>> per the usual ./monero-wallet-cli?
>>
>
> Correct. You should be able to run the gu
ut I haven't tried it myself.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
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+unsubs
M and use qrexec to forward the
needed ports from your daemon. Here's a guide for doing it with monero:
https://getmonero.org/resources/user-guides/cli_wallet_daemon_isolation_qubes_whonix.html.
The same basic procedure can be used for most crypto wallets.
--
qubenix
GPG: B536812904D455B491DCDCDD0
cooloutac:
> On Monday, April 2, 2018 at 12:31:09 PM UTC-4, qubenix wrote:
>> Hello all. I'm currently still on R3.2.
>>
>> I had a situation where I was working with a normal (for me) amount of
>> VMs running. Nothing even close to extreme as far as cpu/mem/io/temp.
&g
on screen, connected with hdmi) and then right
into a restart.
How can I debug this in a useful way? Does someone have an idea what
might cause it?
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
You received this message because you are subscribed to the Google Groups
"qub
> So let me be blunt as this is likely the last email from me to qubes
anyway;
Bye, I'm happy to see you go away finally. It was killing me inside that
you were working on the new gui controller. Fuck off back to bcash.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
You recei
d save the gpu for passthrough.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
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...
another Debian stretch template audio is normal. The pulse
packages there are:
$ sudo dpkg -l | grep pulse
ii gstreamer1.0-pulseaudio:amd64 1.10.4-1
amd64GStreamer plugin for PulseAudio
ii libpulse-mainloop-glib0:amd64 10.0-1+deb9u1
amd64PulseAudio clie
yreb-qusw:
> On 07/19/2017 05:53 AM, qubenix wrote:
>> qubester:
>>> On 07/18/2017 02:27 PM, '0brand' via qubes-users wrote:
>>>> I've been trying to resolve a problem with both of my Debian-8
>>>> vault-appvms.. For some reason my Keepass passwords no lon
sniffer or dumping traffic.
>
> Start at the outmost node, and work inwards. At the point where you dont
> see traffic you know the problem lies one hop upstream, (unless it
> doesn't get to the router obviously).
>
> If you see the traffic inbound at the destination qube, then it'
interface to KeePassX password manager databases
libfile-keepass-perl - interface to KeePass V1 and V2 database files
I ask because I have been using keepassx for three or four years with
only two databases. I keep multiple copies on different storage devices
and I have had only one copy ever become cor
wordswithn...@gmail.com:
> On Wednesday, June 28, 2017 at 10:07:04 AM UTC-4, qubenix wrote:
>> qubenix:
>>> wordswithn...@gmail.com:
>>>> I want to copy network connection profiles from sys-net to
>>>> sys-net-profiles as my computer shuts down.
&g
qubenix:
> wordswithn...@gmail.com:
>> I want to copy network connection profiles from sys-net to sys-net-profiles
>> as my computer shuts down.
>>
>> I'm creating a bash script in dom0 to help with this.
>>
>> I could use
>>
>> qvm-run -ap sys
sys-net "ls
/etc/NetworkManager/system-connections/"); do qvm-run -a -p -u root "cat
/etc/NetworkManager/system-connections/$i" > $i; qvm-move-to-vm
sys-net-profiles $i; done
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
You received this message becaus
: Variable: WixBundleVersion = 3.2.2.3
[0AA0:0AA4][2017-06-25T18:17:24]i007: Exit code: 0x1, restarting: No
```
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from
razy in a Debian vm with
intense I/O and CPU. Kswapd persisted to rock the cpu even after all the
software was done, for about 10 minutes, until I shutdown the vm. Seems
to be a rare condition though because I experience it only 1/50 times
with this vm.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E6
next boot applet was there.
---
Attached are the reports. Support report is encrypted to Qubes Devs:
ADW, JR, and MM.
Thank you to all devs and everyone on this list. My favorite host OS
and a very helpful community.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
You received th
carrefamilyhomes...@gmail.com:
> On Saturday, June 10, 2017 at 8:35:52 PM UTC-4, qubenix wrote:
>> carr...@gmail.com:
>>> Hi,
>>>
>>> My motherboard broke and I need to rebuild my computer. I am looking to get
>>> something that will last for
ng this error from my usb vm on startup. It has a Fedora24
template. The template is untouched from initial Qubes install, aside
from updates via qubes-vm-r3.2-current-testing repo.
For me the issue just started today for no obvious reason.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E50
his page (maybe more?): http://qubesos4z6n4.onion/doc/firewall/
gets stuck in a redirection loop.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from
Reg Tiangha:
> On 04/15/2017 01:06 PM, qubenix wrote:
>> peter...@hushmail.com:
>>> Is there a script to randomize hostname on each boot?
>>>
>> I think blank hostname is better than randomized. How would it be
>> randomized: dictionary words, rng
han blank.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
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
cooloutac:
> On Wednesday, April 12, 2017 at 10:55:08 AM UTC-4, qubenix wrote:
>> Unman:
>>> On Tue, Apr 11, 2017 at 06:20:38AM -0700, Dominique St-Pierre Boucher wrote:
>>>> On Monday, April 10, 2017 at 5:06:30 PM UTC-4, qubenix wrote:
>>>>> qubenix:
Unman:
> On Tue, Apr 11, 2017 at 06:20:38AM -0700, Dominique St-Pierre Boucher wrote:
>> On Monday, April 10, 2017 at 5:06:30 PM UTC-4, qubenix wrote:
>>> qubenix:
>>>> Andrew David Wong:
>>>>> On 2017-04-09 15:25, Joonas Lehtonen wrote:
>>>&
qubenix:
> Andrew David Wong:
>> On 2017-04-09 15:25, Joonas Lehtonen wrote:
>>> Hi,
>>
>>> if you setup MAC randomization via network manager in a debian 9
>>> template as described here:
>>> https://www.qubes-os.org/doc/anonymizing-your-mac-add
Wondering if the list has seen this yet:
https://googleprojectzero.blogspot.com/2017/04/pandavirtualization-exploiting-xen.html
PoC on Qubes 3.2.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
You received this message because you are subscribed to the Google Groups
"qubes-
ion of
two VMs trying to start same proxy vm for example).
It seems others were having these issues before the upgrade, and since I
haven't noticed any complaints. My experience was the opposite. I had no
issues previous to this upgrade.
Please let me know any other info/logs that may be helpful.
-
;
> Bernd
>
>
>
See here for details:
https://groups.google.com/d/msgid/qubes-users/94997d39-2302-4c94-9aa1-ffee6f639bb1%40googlegroups.com
In short you need to:
- Change qubes repo to `stretch-testing`
- update and dist-upgrade your template
If you run into problems, all the
Chris Laprise:
> On 12/15/2016 01:58 PM, Reg Tiangha wrote:
>> On 12/15/2016 11:50 AM, qubenix wrote:
>>> I've used the docs[1] to randomize my MAC on sys-net with debian-9 as
>>> it's template. At first everything was working normal, but I've noticed
>>> now th
Boris Kourtoukov:
> On Tuesday, December 13, 2016 at 3:11:12 PM UTC-5, qubenix wrote:
>> Boris Kourtoukov:
>>> On Tuesday, December 13, 2016 at 2:49:23 PM UTC-5, qubenix wrote:
>>>> Boris Kourtoukov:
>>>>> This is similar to what happened
Boris Kourtoukov:
> On Tuesday, December 13, 2016 at 2:49:23 PM UTC-5, qubenix wrote:
>> Boris Kourtoukov:
>>> This is similar to what happened with the Whonix discussion here:
>>> https://groups.google.com/d/msg/qubes-users/IHhxklnCpYc/Wj2K5euVBAAJ
>>
retch xserver-xorg-core -y && apt-get dist-upgrade -y"
Restart your template and see that you get display again, should fix it.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
erver-xorg-core -y && apt-get dist-upgrade -y"
Restart Template and/or AppVMs based from it. That should fix things in
your TemplateVM and AppVMs.
--
qubenix
GPG: B536812904D455B491DCDCDD04BE1E61A3C2E500
--
You received this message because you are subscribed to the Goo
qubenix:
> qubenix:
>> Marek Marczykowski-Górecki:
>>> On Mon, Dec 12, 2016 at 05:10:00PM +, qubenix wrote:
>>>> Marek Marczykowski-Górecki:
>>>>> Looks like this issue:
>>>>> https://github.com/QubesOS/qubes-issues/issues/2514
>
qubenix:
> Marek Marczykowski-Górecki:
>> On Mon, Dec 12, 2016 at 05:10:00PM +, qubenix wrote:
>>> Marek Marczykowski-Górecki:
>>>> Looks like this issue:
>>>> https://github.com/QubesOS/qubes-issues/issues/2514
>>>>
>>>> R
Marek Marczykowski-Górecki:
> On Mon, Dec 12, 2016 at 05:10:00PM +0000, qubenix wrote:
>> Marek Marczykowski-Górecki:
>>> Looks like this issue:
>>> https://github.com/QubesOS/qubes-issues/issues/2514
>>>
>>> Rebuilt package just uploaded to testing re
Marek Marczykowski-Górecki:
> On Mon, Dec 12, 2016 at 12:17:16AM +, a.mcwh...@yandex.com wrote:
>> That means not only me has the same issue with debian-9 template. I've
>> started reinstalling template.
>
>> On December 12, 2016 11:01:00 AM AEDT, qubenix &l
Marek Marczykowski-Górecki:
> On Mon, Dec 12, 2016 at 12:17:16AM +, a.mcwh...@yandex.com wrote:
>> That means not only me has the same issue with debian-9 template. I've
>> started reinstalling template.
>
>> On December 12, 2016 11:01:00 AM AEDT, qubenix &l
kages.
Strangely, my kali template (and AppVM based on it) work normal even
though it was also upgraded at the same time.
```
user@dom0:~$ qvm-run -p d9 gnome-terminal
Unable to init server: Could not connect: Connection refused
Failed to parse arguments: Cannot open display:
```
--
qubenix
GPG: B536
72 matches
Mail list logo
