sajol...@pimienta.org wrote (06 May 2014 19:00:55 GMT) :
> I think that at some point we felt the need to put forward the fact that
> the persistence is encrypted. I tried to do that in branch
> doc/encrypted-persistence. There's only one commit ebcfc87.
Merged, thanks.
Cheers,
--
intrigeri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
On 6-5-2014 11:30, sajol...@pimienta.org wrote:
> Willem van der Poel:
>> I actually had that issue with the ISO. Just didn't like the way
>> I had to use FireFox to verify it.
>
> Can I ask you why? Because you didn't had Firefox installed? O
intrigeri:
> JFTR, as the Tails/Debian relationship is kind of a hot topic lately
> (discussion on debian-project@)
I search on debian-project public archive and couldn't find any subject
about Tails or derivatives. Could you give the name of the thread, or a
link?
Cheers,
BitingBird
_
not sure about pgp authentication. Wasn't able to find anything on it
during a quick search, so am assuming not.
I stand corrected on this point. Chrome is released with the fingerprint
listed on [1], in case people need to double-check.
[1] https://www.google.com/linuxrepositories/
~Griffi
sajol...@pimienta.org wrote:
It took a while for your proposal to mature in my head...
Do you think we could replace Firefox and MD5 Reborned Hasher by Chrome
and your app in our documentation?
That's an interesting question. Firefox/Iceweasel has a lot going for
it outside of a possible h
Griffin Boyce:
> Hi all,
>
>Arma and intrigeri suggested I shoot y'all an email. I built a
> sha256sum generator into a Chrome app, and the code might be portable
> to Firefox. Arma'd indicated that TAILS needs a replacement hash
> generator, since the current one is incompatible with recent
I think that at some point we felt the need to put forward the fact that
the persistence is encrypted. I tried to do that in branch
doc/encrypted-persistence. There's only one commit ebcfc87.
Please tell me what you think. What that worth doing? Shall we do that
in a different way?
--
sajolida
hi,
a core developer added some VirtualBox/UEFI compatibility notes in
commit 349ebfe82. Thanks!
The thing is, these reports are about an ISO built from a commit
I made on May 3rd; and, I only uploaded on the very same day a version
of liveusb-creator that merged the latest changes in stable/deve
Hi,
Please review and merge the branch bugfix/7166-vagrant-memory-checks
into the devel branch, which fixes #7166 [1]. I've optimistically
assigned the ticket to Kill Your TV since s/he did the previous testing.
This time, a successful test means that you can build Tails in RAM like
this, which sh
Hi,
#7096 was fixed in a way that duplicates a logo picture. This is not
needed anymore, since this file is now included in the static website
shipped in the ISO. To avoid future discrepancies, in commit f068011,
I have patched "About Tails" to use the file that is already included,
and dropped th
Alan wrote (06 May 2014 14:31:23 GMT) :
> As intrigeri mentionned I think we have a plan to have that working at
> least in Tails.
JFTR, as the Tails/Debian relationship is kind of a hot topic lately
(discussion on debian-project@), it was fixed in wheezy-backports
*before* it was fixed in Tails'
I stumbled upon this project a while ago and have been looking over it for
a while. That's why i decided to look into it more closely and pretty much
love your work. I am a lead integrating developer for Chamelephon, which is
a company that specializes in securing android handsets for privacy-lovin
Hi,
sajol...@pimienta.org wrote:
> Alan:
> > Hi,
> >
> > Please review and merge
> > feature/6763-include-nautilus-gtkhash into devel.
>
> Maybe I missed something but I can't find that branch.
>
It should be there now.
>
> If that's the only diff then you're missing the documentation. I'm not
06/05/14 12:03, sajol...@pimienta.org wrote:
> Sorry for the short notice, but the next public Tails developers meeting
> is scheduled for
>
> Thursday May 8, on #tails-dev (OFTC) 8pm UTC (10pm CEST)
It's seems the time of the meeting actually is an hour earlier, i.e. 7pm
UTC (9pm CEST), but that
intrigeri:
> sorry for breaking the thread, I have deleted the original message,
> and this list has no archive (on purpose).
Now I'm bouncing it to tails-dev since my answer goes beyond user support :)
> I got someone to a bluetooth keyboard with Tails, and here are the
> results:
>
> * by defa
Sorry for the short notice, but the next public Tails developers meeting
is scheduled for
Thursday May 8, on #tails-dev (OFTC) 8pm UTC (10pm CEST)
Every one interested in contributing to Tails is welcome.
Feel free to propose and prepare discussion topics. Please raise them in
this thread so tha
David Grant:
> Please make it clear that when you click "Download Tails 1.0" what you get
> is not (or may not be?) a version of Tails 1.0 that is ready to load onto a
> USB thumb drive and use to boot a computer into Tails. What I got was a
> Roxio-ready program that burned a DVD-R that can be us
intrigeri:
> Daniel Kahn Gillmor wrote (02 May 2014 20:43:39 GMT) :
>> The ThinkCentre M82 boots fine with a Tails 1.1 beta generation USB
>> stick in both UEFI and "legacy" BIOS mode.
>
> Thanks for the report!
I added that to the list of problematic hardware. The description of the
issue might
Willem van der Poel:
> I actually had that issue with the ISO.
> Just didn't like the way I had to use FireFox to verify it.
Can I ask you why? Because you didn't had Firefox installed? Or because
you didn't like the idea of using a web browser to do that?
> Instead I just used some common sense
19 matches
Mail list logo
