https://groups.google.com/forum/m/#!topic/qubes-users/0N7sLHBRIdk
Here are my notes on this. I was unable to run Android from the qubes virtual
system. But adding a second hdd, manually encrypting it, manually mounting and
unmounting it after boot... Worked.
--
You received this message
Anyone have one of these?
802.11bgn
It recognizes but only sometimes sees WiFi networks. Seems to work better when
I connect the USB after sys-net is started.
It connects to my network but loses service after a minute or two even tho it's
still connected to the network.
I think the Linux
I'm using kde and everything works.
--
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 post to this group, send email
> First, read this. It is very informative.
>
https://groups.google.com/forum/#!topic/qubes-users/hvGX_Q7gv2o
I think about halfway through here a few people mentioned their prospects.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
ok thanks for your input. Ill just reinstall, I suppose. I do have backups!!
Cant
get them unless I boot into rescue because the usb no longer works without my
sys-usb being able to start. I will try to recreate this and see on my second
HDD.
Ill check the dnf log too.
--
You received this
Please share your experience with qubes-builder! I need help. Is that what you
are
doing?
Check out my notes:
I created a Template called Dev. This template is responsible for compiling the
kernel and qubes-builder. Its based on the latest stable Fedora. (FC27?)
Packages
installed include:
where is your email? I will email you.
I too have found many problems.
--
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
The proper way to create an HVM can be found here:
https://www.qubes-os.org/doc/hvm/
HVMs should be created from the terminal in dom0. Open a terminal:
$ qvm-create win7 --class StandaloneVM --property virt_mode=hvm --property
kernel="" --property memory=4096 --property maxmem=4096 --property
I tried to install kali again. Last time I couldnt get it to run, but with your
help, I correctly created an HVM. Now I did something stupid.
When partitioning, you will be shown 3 virtual drives. If you type 'pvs' (or is
it
'lvs'?) into the dom0 terminal, you will see 3 virtual partitions:
I did do that. The problem was that 'misconfigured' file: .rpmmacros.
Apparently you have to edit (or make) the file and add _gpg_dir, _gpg_name and
_signature parameters. This is only half true.
The file that needs to be modified (and possibly bind-dir this file) is not
located in
Yes, thank you. I have read that entire page, as well as a few other good
resources:
github.com/rtiangha/qubes-linux-kernel/blob/devel-4.14-hard/README.md
github.com/0spinboson/qubes-doc/blob/patch-1/managing-os/compiling-your-own-kernel.md
Im running into a problem right at the end.
rpm
Ive been looking at kernel compiling. Ive amounted certain information,
but not enough.
I see 3 git repos with kernels: qubes-linux-kernel, rtiangha and fepitre.
I know I can change versions with $ git checkout *version*
I also know that I can download the sources and build them and I would
Ive been looking at kernel compiling. Ive amounted certain information,
but not enough.
I see 3 git repos with kernels: qubes-linux-kernel, rtiangha and fepitre.
I know I can change versions with $ git checkout *version*
I also know that I can download the sources and build them and I would
I mostly followed this page and the GCC error was due to not having GCC-C++
installed. After that, all was well!
$ sudo yum install gcc-c++
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving
Can someone please point me in the right direction? I don't know where to look.
I've created a standalone Fedora 26 and I'm looking at this page, the qubes
page : working with kernel,
I've installed every Palast I can think of.
Error gcc plug-ins installation does not support plug-ins...
Hi. I think that was only half of the answer. I have had this problem too: of
removing original templates; ie- debian-9, fedora-26.
The documentation;
https://www.qubes-os.org/doc/remove-vm-manually/
is only viable via templates that are not "installed by (system/dom0)".
The GUI gives the
Look at the custom install Qubes page.
Go in the tty3 and format your drive from there according to instructions. Then
go back to GUI and try to install.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
Try doing a search for your template name
$ find / debian-9
Delete everything you find.
$ lvs
$ lvremove debian-9 debian-9-root debian-9-swap #(I think!, double check me)
$ systemctl disable debian-9
--
You received this message because you are subscribed to the Google Groups
"qubes-users"
Open a terminal in dom0 and type
sudo qubes-dom0-update
--
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 post to
Thats awesome! The colors did change, however the files were not persistent.
Im going to try writing a script that overwrites the files on startup.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
> I tried to attach 1 hdd(storage block) to different vm at the same time)
> something like this
>
> qvm-block attach work dom0:sdd --persistent
>
> qvm-block attach personal dom0:sdd --persistent
>
> then if hdd is attached one appvm, it won't work in another appvm(not even
> starting a
The real question now is... why can I not create a Physical Vol out of the
entire
device and is this necessary?
I think it is necessary because if you have x amount of bytes not in PV and
therefore not encrypted then that is enough for a small attack intrusion, right?
--
You received this
I found the qubes.xml file!
I can manually edit the colors and the order of them!
But it doesnt actually do anything.
Is there a way around this? I want to change the colors and order!
I found this:
https://github.com/QubesOS/qubes-issues/issues/2523
which suggests that its... not possible
I think that would do it. Thanks. Ive read *almost* everything in the docs and
it amazes me when I see something like this that I somehow couldnt find
elsewhere!
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group
This became an issue when I have a backup qube called debian-9-1 that will also
not remove.
I have since reinstalled, so no more problem for me at least.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
On Sunday, March 25, 2018 at 7:20:29 AM UTC-4, awokd wrote:
> On Sun, March 25, 2018 3:07 am, sevas wrote:
> > I had qubes installed without it. I wanted to install android. Android
> > didnt recognize the virtual machines. So, I plugged in a 2nd disk. I was
> > able to
On Sunday, March 25, 2018 at 8:14:12 PM UTC-4, vel...@tutamail.com wrote:
> I am trying to harden my Fedora and Debian templates and was hoping for some
> basic help and commands to do the following:
> How would I add a service like Qubes-VM-hardening ?
Look at Tresnor.
> Should I enable
I recommend a dedicated vm(not your vault). I also recommend installing kgpg.
Thats all I have.
--
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
Red Hat says use vgreduce.
vgreduce says theres no space.
Ubuntu says enable discard on root.
Fedora says discard is dangerous to enable.
Qubes says there is no current solution.
Confusious says make qube and dd if=/dev/random and delete qube.
A liar said fallocate would allocate all the
A alternative thought that doesnt require any knowledge on my part would be to
install qubes twice. Once on each device. Then format the 2nd device from
inside
the 1st qubes install. Keeping the LVM and LUKS while maintaining separation.
Then I should be able to mount the device without any
>From my understanding, LVM thin partitioning allows qubes to use 'pools' to
actively change... sizes or something for VMs.
I wasnt sure how to remove the drive before installation. Without having the
PC open while it was running and remove the hard drive after partitioning and
before
I just tried to remove some of them.
Well, actually they were a % of a whole backup system qube and I did not finish
the restore.
$ qvm-remove --force-root qubeVM
# Traceback:
File /bin/qvm-remove, line 5 in
sys.exit (main())
/usr/lib/python3.5/site-packages/qubesadmin/qvm_remove.py, line 47
I have a very slow SSD and a very fast m.2.
I am installing qubes on them together.
Does qubes automatically install dom0 to the m.2?
The boot partition is showing as m.2.
I will be qvm-pci attach-ing the ssd to 1 or two specific qubes.
Everything else should be m.2.
--
You received this
I have managed to install by attaching a 2nd HDD to my PC.
in dom0, qvm-pci attach --persistent --option no-strict-reset=true
00:{myPCIsataDev}.0
Everything seems to be working... except for the mouse, of course. Otherwise,
drive-able. When I shut it down and restarted, it did not boot. I
Im looking into this and Im thinking that if you add a second HDD you can plug
Android into the 2nd HDD and install it.
Im about to 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
Not at all. You should be able to use the GUI, if you choose to do so.
Linux environments tend to be command line environments. You will occasionally
find things that cannot be done via GUI, so its a good idea to learn how to do
things from the client.
--
You received this message because
Im not for dual booting, but it seemed like a maybe. But thinking more on it,
you would be putting your files at risk. If you are running Qubes with the
Windows partition not running but attached, then it would be very vulnerable
with, hypothetically, lots of attack surface.
However if you
debian updates with "sudo apt-get update && sudo apt-get dist-upgrade"
Whonix should be the same, ("apt-get" or "yum"), but Im not entirely sure.
Keep an eye on your logs (journalctl) and your RPC Policy.
Your RPC Policy suggests that Whonix will update through Tor,
$tag:whonix-updatevm
debian updates with "sudo apt-get update && sudo apt-get dist-upgrade"
Whonix should be the same, ("apt-get" or "yum"), but Im not entirely sure.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
Dual booting is only secure if you remove the HDD/SSD with the other operating
system on it.
having two hard drives is essentially, no more or less secure than having one.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from
Templates do not need to connect to anything.
Open a dom0 terminal (xterm/uxterm) and type 'journalctl -f'
then open a fedora-26 terminal and type 'sudo yum update'
then tell us what it says on the dom0 journalctl output.
Type 'sudo vi /etc/qubes-rpc/policy/qubes.UpdatesProxy'
Its going to
Check the RPC Policy; for updates.
/etc/qubes-rpc/policy/qubes.UpdatesProxy
Make sure your sys-net is the correct one.
--
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
vPro = bad.
That GitHub page does not recommend vPro. It states that AEM uses a feature
of vPro to detect if vPro software (BIOS) has been tampered with while you
were away. Then you can throw your computer in the trash when AEM throws up
a red flag.
--
You received this message because you
Tai, I would be interested to hear what you would recommend for a qubes laptop.
I just bought in to the intel blob myself. Is it feasible to build a custom
laptop?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group
I looked at that. Its a pretty cool direction. I had read some article that
said they were teaming up with a provider that offered end-to-end encryption
so you get the whole kit and caboodle. I wanted to install something less
offensive on my galaxy, but it turns out Verizon phones are trash and
I do find that very interesting and Ive saved the website for further
investigation a little later. Thanks for that!
--
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
Im looking around at dom0 memory management.
I found some Xen server stuff that has equations for
figuring your mem mgmt.
Is allocation important?
It must be.
When they say memory, theyre talking about ram, right? Not HDD memory? Thats a
stupid question, of course they are.
dom0_mem = 502
actually... maybe I did. I made a reply to the KDE/Template sec discussion and
it was gone.
--
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
I have not experienced this and you may be right, it wouldnt suprise me from
them these days.
--
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
I did not mean to go so far south with the above statements. So heres my
additions for alternatives...
CopperheadOS is doing a project still early in the making on reawakening
the open source kernel hardening. The GitHub page can be found here:
https://github.com/copperhead/linux-hardened/issues
I did not mean to go so far south with the above statements. So heres my
additions for alternatives...
CopperheadOS is doing a project still early in the making on reawakening
the open source kernel hardening. The GitHub page can be found here:
For those of you who are fresh like myself, Im going to compile some
information Ive found on Qubes Kernel hardening. And for the tech savvy Qubes
junkies, also like myself, lets have another discussion! Of course
anyones welcome to add their 2 cents or drop a dime.
~Things that I think
Oh right. errors too.
# got empty response from qubesd. see journalctl
journal
#protocol error for call b'admin.vm.Create.hvm'+b''
--
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
Been following the docs and I cant get it.
qvm-create --hvm
#No such argument
qvm-create --HVM
#No such argument
qvm-create --class hvm
qvm-create --class=hvm
qvp create --class hardwareVM
you get the picture. I must be missing something. I just want to start an iso
from a VM.
Im
By recommends I assume you mean the questions during install of
kali-packages-full or whatever its called.
I tell it not change anything like
"should this package have root privileges or give users privilege?"
and I say NO!
The only other questions I received were
Do you want to install
I couldve sworn I replied to these... Well, thanks to everyone who put their 2
cents in!
There is some stellar advice in here! Im going to have to go back later and
read this whole thread and write down bullet points...
Heres what I have so far.
Templates 3 catagories.
1) original
Im thinking about installing it on a test qube soon. I dont entirely understand
how kde on a template will make a difference when the desktop is in dom0.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
ok so, I do a Force-Overwrite and then when qubes-packages need to
update, I can do another Force-Overwrite?
Or I could remove the conflicting package, I assume after the install
completes. I noticed that it tries to install grub, macchanger and
probably many others I dont really need in my
May I suggest installing the KDE5 desktop?
In kali, I know that there is an options menu to change the zoom or something.
Its at the very bottom of the settings menu in Kali KDE desktop.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
glad I could help! I just went through this last week.
Even though I changed the settings in qubes manager to
point to custom-sys-net, my RPC policy still said sys-net:
<
# Default rule for all TemplateVMs - direct the connection to sys-net
$type:TemplateVM $default allow,target=sys-net
/>
I
On Friday, March 9, 2018 at 2:53:41 AM UTC-5, sevas wrote:
> I deleted my original sys-net and sys-fw and I received similar errors. What
> I did to fix it was
>
> dom0$ sudo nano /etc/qubes-rpc/policy/qubes-update-policy
>
> and fixed the command which was pointing to
I deleted my original sys-net and sys-fw and I received similar errors. What I
did to fix it was
dom0$ sudo nano /etc/qubes-rpc/policy/qubes-update-policy
and fixed the command which was pointing to the wrong sys-net.
--
You received this message because you are subscribed to the Google
Im reviving this. I get the same errors about conflict of qubes-core-agent.
trying to overwrite '/etc/dconf/profile/user', which is also in
package qubes-core-agent 4.0.20-1+deb9u1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
How do we solve this? Im going to attempt
Been looking through the files and google trying to find out how to make my USB
wireless card work. I didnt try no-strict-reset or permissive mode because it
said something something SECURITY something and so I skipped over it without a
second thought.
After hours and hours of
lol My problem was that I didnt read the date on the paper which was yesterday.
I had already downloaded and installed it before I realized that it was out.
Despite that the article came up on my phone and this post as well came up 24
hours later.
--
You received this message because you are
Can I not change the name of my system installed template names?
I really want to change them.
I want to change them to original-debian-9 - original-fedora-26
I am having trouble remembering not to edit the actual original templates
and I find myself often wanting to revert my changes.
Whoo hoo!
I went to download qvm-dom0-update and it says no new updates available
--
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
I think I *maybe!* had this problem and fixed it.
Im no specialist, but try this. It wont hurt.
qubes-dom0-update --clean
qubes-dom0-update kernel-qubes-vm kernel qubes-core-dom0*
restart.
Probably wont work, but give it a shot.
--
You received this message because you are subscribed to
Thanks! Im making a note!
+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 post to this group, send email to
Cool. That gave me some ideas. Thanks for sharing your setup.
So, another infosec question Im trying to figure out...
Templates Vs AppVMs.
I find myself with, currently, 8 templates and growing.
This is because I am installing different programs in different VMs
and Im not wanting to install
I wasnt going to say anything... lol. But I was leaning towards debian. But
fedora. Thats Red Hat. They are the leading administrative suite as far as I
know. Or were. They must have good security or whos going to throw up a server?
>In particular, Fedora's downfall is that its one of the very
Reference:
https://groups.google.com/forum/#!topic/qubes-users/5eJF__5UBAc
Apparently many people suffer from this problem.
After reinstalling the a few dire programs, everything seems to be working.
Only problem is that the dom0 applications menu is gone.
Possible solution here:
dom0$ qubes-dom0-update --clean #Clean yum repos...
dom0$ qubes-dom0-update qubes-core-dom0*
## find: '/var/lib/qubes/dom0-updates/var/cache/yum': No such file/directory
## Installing *linux-debug *vaio-fixes(1/2)
dom0$ qubes-dom0-update --gui
## xterm: cannot load font
A little more info...
Qubes 4.0 rc4.
Starting Debian-9 returns error that /var/lib/qubes/something doesnt exist.
Is there a keyboard command for opening the dom0$terminal?
This is crazy. Im afraid to work on it now.
dom0$ for VM in `qvm-ls --raw-list`; do qvm-prefs -s $VM kernel 4.14.13-3;
A little more info...
Qubes 4.0 rc4.
Starting Debian-9 returns error that /var/lib/qubes/something doesnt exist.
Is there a keyboard command for opening the dom0$terminal?
This is crazy. Im afraid to work on it now.
--
You received this message because you are subscribed to the Google
dom0$ sudo qubes-dom0-update --action=reinstall qubes-template-debian-9
Now my dom0 menu is gone. No more terminal. No more Qubes Manager. No more...
anything...
I gave up immediately and thought I would reinstall Qubes.
Well, that was a fail too. Qubes installer freezes when I click
Thank you both for this enlightening talk, and especially Yuraeitha for such a
lengthy researched opinion!
We speak of stability. Stability and vulnerability go hand in hand, dont they?
I love the kde plasma desktop and I would like to have it. But it looks like a
complicated GUI that probably
Does choosing a TemplateVM have any tactical advantage to security?
Does installing KDE have any tactical disadvantage to security?
--
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
Yes. My updateVM was set to custom-sys-net. I changed it to
custom-sys-firewall, as you recommended.
I am very unfamiliar with the command-line (thats called bash, right?) tools.
But qubes-prefs updatevm custom-sys-net = yes.
What I actually did:
sys-net$
yum clean all
yum repolist all
#
> Normally you shouldn't have to edit this file. Did you set qubes-prefs
> updatevm custom-sys-net? (And why sys-net instead of sys-firewall)? Might
> also want to clear dnf/yum cache in custom-sys-net.
should it be going through the firewall? The default settings send through
sys-net. Yeah, I
ooh I spoke too soon. Its not working. Its helping! But
journalctl returns:
Template > allowed to sys-net
Fedora template says failed to synchronize cache for repo "updates"
Debian says the same as it did previously.
And next to the "state" entry of the Qubes Manager, they both have a down
ooh I spoke too soon. Its not working. Its helping! But
journalctl returns:
Template > allowed to sys-net
Fedora template says failed to synchronize cache for repo "updates"
Debian says the same as it did previously.
And next to the "state" entry of the Qubes Manager, they both have a down
A forum is a must. It doesnt have to be official. But it needs to happen.
It needs to have a section for
-Questions & -Community Tutorials
at the very least.
The Kali forums is a great example of what a qubes forum should look like.
--
You received this message because you are subscribed
ooh I spoke too soon. Its not working. Its helping! But
journalctl returns:
Template > allowed to sys-net
Fedora template says failed to synchronize cache for repo "updates"
Debian says the same as it did previously.
And next to the "state" entry of the Qubes Manager, they both have a down
That helped.
journalctl -f in dom0 returned a block in the rpc-policy.
dom0: nano /etc/qubes-rpc/policy/qubes-UpdatesProxy
I had to change the name of my primary sys-net to the name I provided my
default sys-net.
Thats what I get for going and changing things around.
Solved. Thanks!
--
I cant seem to update my templates.
In the debian-9 TVM I type:
sudo apt-get update
Ign:1 http://.
Ign:2 http://.
Ign:3 http://.
Err:4
Err:5
Err:6 Connection Failed
E: The repo "http://...; does no longer have a Release File.
N: Updating from such a repo cant be done securely, and
86 matches
Mail list logo
