[Tails-dev] wiki, stream_isolation page broken link
Hi, there is a broken link in: https://tails.boum.org/contribute/design/stream_isolation/ diff --git a/wiki/src/contribute/design/stream_isolation.mdwn b/wiki/src/contribute/design/stream_isolation.mdwn index a8b8edd..08623b9 100644 --- a/wiki/src/contribute/design/stream_isolation.mdwn +++ b/wiki/src/contribute/design/stream_isolation.mdwn @@ -77,7 +77,7 @@ Implementation == A few SOCKS ports are configured -in [[!tails_gitweb chroot_local-includes/etc/tor/torrc]]: +in [[!tails_gitweb config/chroot_local-includes/etc/tor/torrc]]: * default system-wide `SocksPort` (9050): `IsolateDestAddr` and `IsolateDestPort` enabled Alex ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] BitTorrent download section in website
Hi all, some days ago a friend contacted me as she was a bit confused with torrent downloading section in https://tails.boum.org/download/index.en.html User was not able to fully understand the "Additionally, you can verify the signature of the Torrent file itself before downloading it." wondering how one can verify something before downloading it. Obviously the "it" refers to the "Torrent" in the previous sentence, meaning the ISO and the sig. I know this is a tiny issue but maybe referring explicitly to the ISO would help? diff --git a/wiki/src/download.html b/wiki/src/download.html index 77426b3..d2c99e8 100644 --- a/wiki/src/download.html +++ b/wiki/src/download.html @@ -91,7 +91,7 @@ share it without restriction. Additionally, you can verify the signature of - the Torrent file itself before downloading it. + the Torrent file itself before downloading the ISO. Seed back! or perhaps the (torrent) content is more accurate? diff --git a/wiki/src/download.html b/wiki/src/download.html index 77426b3..49e148b 100644 --- a/wiki/src/download.html +++ b/wiki/src/download.html @@ -91,7 +91,7 @@ share it without restriction. Additionally, you can verify the signature of - the Torrent file itself before downloading it. + the Torrent file itself before downloading the content. Seed back! Greetings signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [doc] signing key expriy date needs <3
On 01/05/2015 01:31 PM, u wrote: > Hi, > > I just saw that the expiry date of the signing key on > https://tails.boum.org/doc/about/openpgp_keys/index.en.html needs to be > updated as it expired 2 days ago. > > I am pretty busy today, so I can't commit to do that right now, but if > nobody else works on it, I can take care of it at a later point in time. > > Cheers > u. Hi, I assume you're referring to 0x1D2975EDF93E735F If so, there is a patch attached updating expiration date for primary key and subkey. Greetings From 60dbb70b5809163751a7fdbabe9449fcb4955ad5 Mon Sep 17 00:00:00 2001 From: irregulator Date: Thu, 8 Jan 2015 18:03:36 +0200 Subject: [PATCH] Update expiration date for 0x1D2975EDF93E735F --- wiki/src/doc/about/openpgp_keys.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/wiki/src/doc/about/openpgp_keys.mdwn b/wiki/src/doc/about/openpgp_keys.mdwn index 65f48f9..309eaa7 100644 --- a/wiki/src/doc/about/openpgp_keys.mdwn +++ b/wiki/src/doc/about/openpgp_keys.mdwn @@ -41,12 +41,12 @@ key pair is managed in a less safe way than our signing key. Key details --- -pub 4096R/0x1D2975EDF93E735F 2009-08-14 [expires: 2015-01-03] +pub 4096R/0x1D2975EDF93E735F 2009-08-14 [expires: 2016-12-27] Key fingerprint = 09F6 BC8F EEC9 D8EE 005D BAA4 1D29 75ED F93E 735F uid Tails developers (Schleuder mailing-list) uid Tails list (schleuder list) uid Tails list (schleuder list) -sub 4096R/0xD843C2F5E89382EB 2009-08-14 [expires: 2015-01-03] +sub 4096R/0xD843C2F5E89382EB 2009-08-14 [expires: 2016-12-27] How to get the public key? -- -- 2.1.4 signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [review] Run a HTTP server as an Hidden Service insideTails.
On 01/20/2015 08:45 PM, matsa wrote:
>
> Hi,
>
> Tails can be used to run a HTTP server, nginx, as an Hidden Service.
>
> The documentation is available here:
> http://repo.or.cz/w/tails/matsa.git/blob/refs/heads/7879-http-server-with-nginx:/wiki/src/doc/advanced_topics/http_server_with_nginx.mdwn
>
Hello,
thanks for writing this.
Two thoughts:
a) I think 'server_tokens off;' option could be set in the suggested
nginx configuration:
server {
listen 127.0.0.1:8080 default_server;
server_name localhost;
server_tokens off;
root /var/www;
index index.html index.htm;
location / {
allow 127.0.0.1;
deny all;
}
}
This disables emitting nginx version in error messages and in the
“Server” response header field. [1]
In terms of anonymity, this differentiates nginx behavior from the
default one, so one could argue it minimizes the anonymity set. On the
other hand, hiding nginx's version may prevent someone from trivially
guessing the operating system the hidden service runs on. I would add
it's a pretty common choice even in non-onion web services.
b) I observe commands in initial setup and configuration sections repeat
in the "setup after restart" section. I'm wondering if apart from the
explicit citation of the commands in this guide, it would be worth
bundling them in a bash script.
One could argue that advanced users would script the commands one way or
another, but this guide is an advanced topic already, right?
Cheers
[1] http://nginx.org/en/docs/http/ngx_http_core_module.html#server_tokens
signature.asc
Description: OpenPGP digital signature
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] chromium in Tails
On 02/02/2015 09:36 PM, sycamoreone wrote: > Sina S: >> Has anyone considered switch from Firefox to Chromium in Tails? >> [...] > > Tails doesn't really include Firefox but a slightly modified Tor Browser > Bundle, which is based on Firefox. > > In theory one could do something like TBB for Chromium and (for the > reasons you mentioned) people actually looked into this, but there is a > long list of technical problems: > > > https://trac.torproject.org/projects/tor/wiki/doc/ImportantGoogleChromeBugs > > There are other reason not to switch too, like the fact that the TBB > developers are by now very familiar with the Mozilla code base. > Also check the "Why not Google Chrome?" (final) part in Mike Perry's blog post: https://blog.torproject.org/blog/isec-partners-conducts-tor-browser-hardening-study ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
