it mainly seems to be around either updating a vm, vm shutting down, and once
copying something to another vm. I tried to make sense of the logs, something
about a writing to a read only config file. I'm using 3.2
--
You received this message because you are subscribed to the Google Groups
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-09-10 16:12, 3n7r0...@gmail.com wrote:
> On Wednesday, August 17, 2016 at 12:43:27 AM UTC, Andrew David Wong wrote:
>>
>> So, as Marek said, in this particular case, the updated package has already
>> been
>> uploaded to the testing repo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-09-10 09:42, Jodie wrote:
> Here it is, as lovely as that photo is. Thanks!
>
> On Friday, September 9, 2016 at 6:46:03 PM UTC-4, Andrew David Wong wrote:
> On 2016-09-09 13:48, Jodie wrote:
Version 3.1. What's annoying me is that I
On Wednesday, August 17, 2016 at 12:43:27 AM UTC, Andrew David Wong wrote:
>
> So, as Marek said, in this particular case, the updated package has already
> been
> uploaded to the testing repo for 3.2. If you're on R3.2, and if you're willing
> to test this package (and you're certainly under no
On Sat, Sep 10, 2016 at 03:23:54PM -0400, Chris Laprise wrote:
> That also misses the point.
yes, somewhat - thanks for making "the point" clearer! :-)
> Xen is far smaller and simpler than the kernels that protect Windows and
> Linux, and it has fewer vulnerabilities as a result. Its also
Here is the redhat help page for yum errno 256:
https://access.redhat.com/solutions/203603
It looks like yum either cannot access or validate the rpm file shown
(fedora template). Maybe a read error... What type of media did you
create, and what is the capacity?
You could try booting with
Hey everyone,
I finally got around to setting up Qubes OS 3.1 onto an old laptop of mine - an
Acer Aspire V3-571. The installation went smoothly, allowing the installer to
set up all the default settings (and setting up the partitions so it allocated
all space to the new OS, wiping the old
On 09/10/2016 07:31 AM, Holger Levsen wrote:
Hi,
On Sat, Sep 10, 2016 at 04:08:53AM -0700, neilhard...@gmail.com wrote:
Qubes is insecure due to Xen exploits.
[...]
Considering that Snowden is literally advertised on the Qubes home page, I would suggest
the answer is "Yes" The NSA is
[First, a rant. I hate mailing lists. How am I supposed to attribute quotes
from earlier posts in the thread not contained in the previous post?]
nishi:
>Any advices on how to set up Qubes to have a VPN + sys-whonix working together
>(or VPN + a TorVM proxy) in a good anonymous way would be
I've seen some dispute that a Linux browser exploit even exists.
Like, could you take Chrome or Firefox to a page, and then have a remote shell,
that loads a file onto the hard drive to monitor everything?
I can do this with Metasploit on Windows, but I've actually seen a lot of
people saying
How are you today, is my pleasure to come
in contact with you, please i have an urgency
that i will like to share with you as soon as
possible, i will be happy to read from you as
soon as i can.
Best regard
Conima.
--
You received this message because you are subscribed to the Google
Le samedi 10 septembre 2016 04:57:17 UTC+2, Chris Laprise a écrit :
> On 09/08/2016 04:41 AM, nishiwak...@gmail.com wrote:
> > Hello,
> >
> > I am struggling to have VPN work while using it with Tor, I can't have both
> > work.
> >
> > I tried first to follow Mrs. Rutkowska's tutorial on setting
Qubes is insecure due to Xen exploits.
Qubes tends to quickly patch the exploits, but we know how it works in the real
world... nation states and other people buy up the exploits before they can get
to the market.
I would also suggest that if you are using Qubes, this may even be a flag at
On Friday, 9 September 2016 09:56:36 UTC+1, neilh...@gmail.com wrote:
> the problem with Qubes, of course, is all the Xen exploits which make it
> insecure.
Off-topic here but is Qubes really insecure? Should I be worried?
--
You received this message because you are subscribed to the Google
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> https://github.com/rustybird/qubes-split-dm-crypt
If anyone has been using this already, please update to version 0.1.1
which contains a security bugfix.
Rusty
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Andrew!
>> https://github.com/rustybird/qubes-split-dm-crypt
> This looks great, Rusty! Thank you!
I actually took the modern luksFormat parameters from your writeup at
https://www.qubes-os.org/doc/encryption-config/. The 5 sec iteration
time
16 matches
Mail list logo
