SGX is unsecure
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
On 2/9/23 19:24, Ashutosh Pandey wrote:
does tails use SGX??
I don't think so.
--
boyska
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
Hi,
My name is Ashutosh Pandey I've been using tails for the past 2-3 months
and most of the time it works fines but for the past 2 days it shows me a
message at boot time that Intel SGX is disabled in BIOS even though I
haven't made any changes to BIOS my BIOS doesn't even have the option for
Hi folks,
ok, I have understood, that it is not easy to install a windowmanager looking
like MacOS or Windows.
Also, you told me, you are using Gnome.
Well, thinking about this, please allow me a very personal feedback:
1. The choice of using Gnome is IMO not very lucky. Gnome is big, Gnome
All,
A quick follow-up to suggest that clearing the Tails screen saver/slide show
require the key-press combination used to invoke it. A passer-by could
otherwise restore the screen and reveal Tails with a single key press.
This should perhaps be the case even when an admin password is set,
All,
I believe hiding Tails' UI would prove too resource intensive and ultimately
futile. It just can't be done and maintained well enough to fool sharp-eyed
observers. After all, the first thing a passer-by does is study your screen.
It's human nature and very hard to resist.
Tails users
Hello,
Hans:
> Dear list,
>
> I am wondering, why tails no more get an undercover mode. IMO it is very
> dangerous for users, if their window manager is not looking like the normal
> window manager used everywhere, especially in countries, where any "strange"
> desktop might cause attention
Dear list,
I am wondering, why tails no more get an undercover mode. IMO it is very
dangerous for users, if their window manager is not looking like the normal
window manager used everywhere, especially in countries, where any "strange"
desktop might cause attention on authorities.
This
Hi,
Aryeh Pechet:
> Hello, I have a question about the electrum wallet built into tail. When
> accessing or creating a wallet does electrum record your home ip to the tor
> ip?
This is the list for Tails *development*.
As this is a support question, I am forwarding your email to
Hi Aryeh,
I'm forwarding your question to our user support list:
tails-supp...@boum.org where it's more suited.
Forwarded Message
Subject: [Tails-dev] question
Date: Sat, 23 Jan 2016 21:54:27 -0500
From: Aryeh Pechet <pechetar...@gmail.com>
Hello, I have a question
Hi,
Romeo Papa wrote (18 Aug 2015 23:26:10 GMT) :
When working on my own git topic branch, what do I do when rebasing
patches? Do I create a new topic branch and push the rebased commit to
it, or do I just write over my original topic branch?
My rule is to never rewrite already published Git
Hi,
When working on my own git topic branch, what do I do when rebasing
patches? Do I create a new topic branch and push the rebased commit to
it, or do I just write over my original topic branch?
I'll give you a practical example: I have pushed a series of patch on a
clone of the repo on
On 05/24/2015 01:09 AM, anonym wrote:
On 05/23/2015 10:15 AM, Adam Burns wrote:
Hi anonym,
On 05/23/2015 09:09 AM, anonym wrote:
On 05/22/2015 01:31 PM, Adam Burns wrote:
I've taken a very quick look at this.
As the ticket #8086 suggests, it is an issue in the way Rake is used
with a
On 05/23/2015 10:15 AM, Adam Burns wrote:
Hi anonym,
On 05/23/2015 09:09 AM, anonym wrote:
On 05/22/2015 01:31 PM, Adam Burns wrote:
I've taken a very quick look at this.
As the ticket #8086 suggests, it is an issue in the way Rake is used
with a Monkey-patched Vagrant to build TAILS.
On 05/22/2015 01:31 PM, Adam Burns wrote:
I've taken a very quick look at this.
As the ticket #8086 suggests, it is an issue in the way Rake is used
with a Monkey-patched Vagrant to build TAILS.
The monkey patch is against *Vagrant*, and has nothing to do with Rake.
IIRC newer versions of
Hi anonym,
On 05/23/2015 09:09 AM, anonym wrote:
On 05/22/2015 01:31 PM, Adam Burns wrote:
I've taken a very quick look at this.
As the ticket #8086 suggests, it is an issue in the way Rake is used
with a Monkey-patched Vagrant to build TAILS.
The monkey patch is against *Vagrant*, and
I've taken a very quick look at this.
As the ticket #8086 suggests, it is an issue in the way Rake is used
with a Monkey-patched Vagrant to build TAILS.
Although the devs are keen to move to some other tech (Docker was
mentioned), I'm looking at removing Rake (and thus the Vagrant library
calls)
I followed this manual:
https://tails.boum.org/contribute/build/
Beforehand I just had upgraded from Wheezy to Jessie.
At the end I had the same error described here:
https://mailman.boum.org/pipermail/tails-dev/2014-July/006258.html
https://labs.riseup.net/code/issues/8086
Many thanks
On
kurono,
During the meanwhilst, you may want to take a look at this
https://labs.riseup.net/code/issues/8304 to get your build working with
a suitable Vagrant version.
On 05/22/2015 01:31 PM, Adam Burns wrote:
I've taken a very quick look at this.
As the ticket #8086 suggests, it is an issue
It works indeed thanks!
El 22/05/15 a las 13:37, Adam Burns escribió:
kurono,
During the meanwhilst, you may want to take a look at this
https://labs.riseup.net/code/issues/8304 to get your build working with
a suitable Vagrant version.
On 05/22/2015 01:31 PM, Adam Burns wrote:
I've
OR, worse scenario, they already are and are the owners of the TAILS
process, and have total ability to capture all data?
Just a concern that all participants need to be informed of THANK YOU !
*-Ernie*
* (864) 610-8021Greenville, SC USA*
Mike Rising wrote (13 Jan 2015 14:44:25 GMT) :
OR, worse scenario, they already are and are the owners of the TAILS
process, and have total ability to capture all data?
Just a concern that all participants need to be informed of THANK YOU !
Nothing prevents adversaries to contribute to
22 matches
Mail list logo
