On Wed, Jan 27, 2016, at 04:22 PM, flapflap wrote:
> Hi all,
>
> I get a certificate warning when visiting https://git.tails.boum.org,
> issued by immerda.ch.
Same here (Firefox 44.0 on an Ubuntu derivative)
"git.tails.boum.org uses an invalid security certificate.
The certificate is not
Hi,
I'll be the release manager for Tails 2.2, which is a major release
scheduled for 2016-03-08. Note that there will be no Tails 2.1; for the
curious I suggest reading up on our versioning scheme:
https://tails.boum.org/contribute/release_schedule/#index4h1
The list of tickets targeting Tails
Hi all,
I get a certificate warning when visiting https://git.tails.boum.org,
issued by immerda.ch.
I don't know how complex this is to do, but what about using letsencrypt
to get rid of the warning (which might confuse less skilled
users/contributors)?
Cheers,
~flapflap
signature.asc
sycamoreone wrote (26 Jan 2016 22:03:00 GMT) :
> sajolida:
>> intrigeri:
> I am also for keeping D separately. But the blueprint should document
> the use-cases A, B, C, and E that Pidgin and its potential replacement
> should address. And also the use-case D that it need not.
Yes. I see that
Tyler Durden:
> To whom it may concern:
>
>
> The PGP key used for signing the Tails download releases is expired.
> Just fyi there.
No, it isn't. The key was created in 2015 and had an expiration date
for 2016. Since the key was not compromised and is still valid, its
expiration date was
on the signing key transition page
(https://tails.boum.org/news/signing_key_transition/) the 'full
description' of the (then) new signing key still mentions the old
expiration date. i'm not sure if we should change that, but at least one
user was confused by that...
Based on commit
the desktop screenshot on the upgrade page still shows a wheezy gnome, i
replaced the desktop.png with a screenshot of a tails 2.0.
Based on commit ef6b6c0e3b2f49c232c7ef7bd2d1e6f8f436fe12:
Revert "Try to force our website to update the torrent link."
(2016-01-27 02:46:57 +0100)
i created a
Hi,
Ah, it's that time of the release cycle again! I would like everyone to
take a careful look at their own Redmine view, grouped and ordered by
Target version:
https://labs.riseup.net/code/projects/tails/issues?query_id=128
At the time of writing, there are 82 open tickets still targeting
