Re: [Tails-dev] Testing the ISO Verification Extension
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] [Tails - Feature #5991] Include BitTorrent software
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.
[Tails-dev] Testing the ISO Verification Extension
This week I was really excited to be able to play with the first versions of the ISO verification extension for Firefox written by Giorgio. Congrats! For those of you who didn't follow this, development versions are available on: https://maone.net/dev/tails/download.html We tested it with tchou and here are some comments. I thought it would be easier to process all this by email than on Redmine (we don't have a strict policy regarding this). I'll flag issues as belonging to either :maone: or :tchou: just to make sure people agree with what's on their plate. Feel free to counterargument. 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... 1. We tested the browser detection code on various browser and it seems to behave fine. I heard that intrigeri had some issue with his but I'll double-check and report. 2. The extension is great because it preserves its state even if you close the tab. You can open it again and the result of the verification is still there. Still, I think we should reset its state in some cases: - When the download is finished and the user clicks on the "next" button. :maone: - We might add a "Download again" button as a minor option below the "next" button, with a link back to the same page. :tchou: 3. Regarding resetting the state of the extension, we were wondering how this interacts with the Private Browsing of Firefox. Is is reseted when going in and out of Private Browsing? 4. We looked at the SSL information embedded in the code (conf.json) and there's the fingerprint of the certificate for tails.boum.org. According to the specification on https://tails.boum.org/blueprint/bootstrapping/extension/#index5h2 it should instead include "root certificate of the authority expected to sign the certificate of https://tails.boum.org/";. We don't want the extension to break when boum.org renew their certificates. :maone: 5. In 2cf4737 you added a class to the tag. We can't really do that in ikiwiki. So is it possible to move this somewhere else in the code? Maybe on #download-and-verify? :maone: 6. We changed the user-visible strings about the supported browser in 0e7d362. I hope this didn't break anything. 7. We added an alternative display between outdated Firefox versions and unsupported browser vendor in 67f4e01. Giorgio: do you think you can adjust the sniffer accordingly? 8. We'd like to change the display of progress information: - download speed from Kb/s to KB/s - downloaded size from MB to MiB - displayed ETA to adjust to "1 minute" and "seconds" (keeping in mind that all user-facing strings should be in our HTML so that people can translate them) Giorgio: is that possible? I guess we need to embed "minutes", "minute", "seconds", and "second" in the HTML. 9. There's no way of going back to the previous steps using the "Back" button of the browser. That was no specified in the wireframe and we're wondering whether that's needed at all but apparently, in other such scenarios of step-by-step processes inside a single page, sometime the "Back" button of the browser is mapped to going back to the previous step. For example, right now, as the extension remembers its state, there's no way of canceling the download once it started (you can only "pause" it). But this particular case can be solved differently maybe. 10. Our wireframe didn't include a display of the hash itself at the end of the verification. We're not convinced that's useful and will probably remove it from the HTML. :tchou: 11. Once the download is over it should go from #download-button to #download-text. :maone: 12. The "Verify ISO image" is a button but should not be. :tchou: 13. The #download-button-size is updated with the download URL once clicked; but on the wireframe the ISO size remains displayed. Granted, now that we have more complete progress indicators that would be a duplicate information. Maybe we can empty this completely then? :maone: 14. When clicking the download button, we're proposed an alternative between "Open with [Archive Manager (default)]" and "Save File". I understand that this corresponds to the Content-Type sent by the HTTP server. But in our scenario it doesn't make sense to open the ISO image with any other application (as we want people to verify it before doing anything, and then mostly likely to install it on a USB with special instructions). So Giorgio, since you have very special powers on web browers, could we do something to propose saving only? Maybe overriding the MIME type or jumping straight to
Re: [Tails-dev] problems with persistence
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] HTTPS-Everywhere missing domain config options
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.
