Re: [Tails-dev] Testing the ISO Verification Extension

[Giorgio Maone]

On 12/11/2015 17:38, sajolida wrote:
> We also published an alpha version of that page on the website, for
> testing purposes as well here:
>
>   https://tails.boum.org/install/download/
>
> But since the time we synced with Giorgio's code we did some changes, of
> course :) They are visible in wiki/src/download.inline.mdwn in our main
> repo (5c97222..926f355) but we'll comment on them here when relevant.
> Giorgio, I wonder how we should do this syncing; as I understand that
> you want to have some test HTML in your repo as well...
Indeed, latest commit (minutes ago) addresses most of your feedback, but
I cannot comment in deep right now.
I will probably do it tomorrow, but in the meanwhile the most important
points are:

1. From now on I'll strictly refer to the HTML at
https://tails.boum.org/install/download/ and send tchou patches if and
only if I actually need the markup to be modified
2. Latest iterations of the extension from git or from
https://maone.net/dev/tails/dave.xpi automatically detect if they're
used on an outdated page (by comaring with #extension-version) and if
they're more up-to-date automatically replace the dave.css stylesheet
with the one from https://maone.net, so while we're still in development
I don't need to actually push it on the site
3. If you want to use the .chrome-unsupported class on
#download-and-verify, rather than on the  element, you just need
to be sure dave.js is loaded after the element exists (e.g. by placing
its 

[Tails-dev] HTTPS-Everywhere missing domain config options

[Anonymous]

In Tails 1.7, when I click on Preferences for the HTTPS-Everywhere
Add-on, I am presented with the screen for the opt-in "Observatory".

What happened to the other section where I could add/edit domains
supported by the plugin? Some sites I would disable because of
cert issues and now I have to disable the plugin in order for this
to work because the domain config option section is now GONE!
___
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] problems with persistence

[elouann]

Hi Oliver,

This is the mailing-list for Tails *development*.

For user support, see https://tails.boum.org/support/

> Everything is saying that my persistence is disabled.

This remind me this:
https://tails.boum.org/doc/first_steps/persistence/upgrade

Cheers,
~ elouann

Oliver Wood  :

> Hi,I currently have tails installed on a usb and just in the last
> hour or so I have booted up tails, logged in with persistence
> (password worked fine) and successfully connected to the Internet
> with a tor network success as well. However none of my persistence
> folders are showing up and I can't use my electrum wallet or PGP
> messaging. Everything is saying that my persistence is disabled.
> Confused to what has gone wrong, im fairly sure i havent visited any
> fishing websites and my computer has no virus's on it that i am aware
> of. (Im assuming this as tails has been working fine with my computer
> since i downloaded it)Your help would be greatly appreciated!Thanks,
> 


signature.asc
Description: PGP 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.

[Tails-dev] [Tails - Feature #5991] Include BitTorrent software

[Spencer]

Hi,



str4d:
If I2P is enabled



The Design section at https://tails.boum.org/contribute/design/I2P/ 
points out some I2P issues.  A new question is, are these concerns 
relevant to the Tor Network as well?


If so, then maybe there can be a "Torrent over I2P :)" consensus based 
on the Tor Project's preference to not support torrenting.




adding the i2p flag to the boot parameters



The Tails documentation on this is not clear to me.

Also, the links https://tails.boum.org/geti2p.net and 
http://127.0.0.1:7657/i2psnark do not load :(




[native application] only usable with I2P



Easy, and I think maybe a good way to go.  Something less usefully 
bloated than Vuze might be more suitable...the I2P documentation has 
some good alternatives.




Perhaps something to this effect could be added to the documentation?



sajolida, what do you think?



Side note: I2P supports UDP traffic, but only really for apps that are
built with I2P support (either native Java, or via the SAM API). Both
I2PSnark and Vuze have DHT support, and IIRC there is a proposal for
implementing uTP. We do also have a SOCKS tunnel that we haven't
finished adding UDP support to, because of a lack of dev
time/funds/incentive...

I2P torrent clients (and apps in general) use a single Destination, so
usually only have two or three tunnels built at any one time. This can
be manually increased up to a maximum of 16, although six is usually
sufficient to see a decent speed increase.



Good to know :)



Tails defaults to hidden mode; then again, the number of people using 
Tails

for I2P torrenting would probably be low, compared to the number of
Vuze nodes (which currently are estimated to make up about 30-40% of
the I2P network).



If people see Tails and I2P as a gateway to torrenting their long-lost 
Where's Wally VHS, that could change.


Wordlife,
Spencer



___
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.