Re: [Tails-dev] [tor-qa] Tor Browser 5.0 is ready for testing!
Mike Perry: > https://people.torproject.org/~mikeperry/builds/5.0-build2/ > > This release is our first stable release based on Firefox 38-ESR. We've > done a lot of work to ensure that this release is minimally disruptive > in terms of changes to the UI/UX, but some hacks were needed, especially > to ensure the "Tiles" feature was disabled, and to clean up the NoScript > whitelist. > > The current Firefox 31-ESR is end-of-life on Tuesday, August 11th, so we > need to switch all users to 5.0 for them to pick up security updates. As > such, extra testing would be appreciated! FWIW: One thing we already found and which unfortunately makes a build3 necessary is the incompatibility with the localized language packs. I was under the impression (wrongly as it turns out) that Mozilla fixed their versioning scheme we get with the git checkouts starting with their esr38 cycle and forgot to doublecheck that. Georg > > Here is the complete changelog since 4.5.3: > * All Platforms >* Update Firefox to 38.2.0esr >* Update OpenSSL to 1.0.1p >* Update HTTPS-Everywhere to 5.0.7 >* Update NoScript to 2.6.9.34 >* Update meek to 0.20 >* Update Tor to 0.2.6.10 with patches: > * Bug 16674: Allow FQDNs ending with a single '.' in our SOCKS host name > checks. > * Bug 16430: Allow DNS names with _ characters in them (fixes > nytimes.com) > * Bug 15482: Don't allow circuits to change while a site is in use >* Update Torbutton to 1.9.3.2 > * Bug 16731: TBB 5.0 a3/a4 fails to download a file on right click > * Bug 16730: Reset NoScript whitelist on upgrade > * Bug 16722: Prevent "Tiles" feature from being enabled after upgrade > * Bug 16488: Remove "Sign in to Sync" from the browser menu (fixup) > * Bug 16268: Show Tor Browser logo on About page > * Bug 16639: Check for Updates menu item can cause update download > failure > * Bug 15781: Remove the sessionstore filter > * Bug 15656: Sync privacy.resistFingerprinting with Torbutton pref > * Bug 16427: Use internal update URL to block updates (instead of > 127.0.0.1) > * Bug 16200: Update Cache API usage and prefs for FF38 > * Bug 16357: Use Mozilla API to wipe permissions db > * Bug 14429: Make sure the automatic resizing is disabled > * Translation updates >* Update Tor Launcher to 0.2.7.7 >* Bug 16730: Prevent NoScript from updating the default whitelist >* Bug 16715: Use ThreadsafeIsCallerChrome() instead of IsCallerChrome() >* Bug 16572: Verify cache isolation for XMLHttpRequests in Web Workers >* Bug 16884: Prefer IPv6 when supported by the current Tor exit >* Bug 16488: Remove "Sign in to Sync" from the browser menu >* Bug 16662: Enable network.http.spdy.* prefs in meek-http-helper >* Bug 15703: Isolate mediasource URIs and media streams to first party >* Bug 16429+16416: Isolate blob URIs to first party >* Bug 16632: Turn on the background updater and restart prompting >* Bug 16528: Prevent indexedDB Modernizr site breakage on Twitter and > elsewhere >* Bug 16523: Fix in-browser JavaScript debugger >* Bug 16236: Windows updater: avoid writing to the registry >* Bug 16625: Fully disable network connection prediction >* Bug 16495: Fix SVG crash when security level is set to "High" >* Bug 13247: Fix meek profile error after bowser restarts >* Bug 16005: Relax WebGL minimal mode >* Bug 16300: Isolate Broadcast Channels to first party >* Bug 16439: Remove Roku screencasting code >* Bug 16285: Disabling EME bits >* Bug 16206: Enforce certificate pinning >* Bug 15910: Disable Gecko Media Plugins for now >* Bug 13670: Isolate OCSP requests by first party domain >* Bug 16448: Isolate favicon requests by first party >* Bug 7561: Disable FTP request caching >* Bug 6503: Fix single-word URL bar searching >* Bug 15526: ES6 page crashes Tor Browser >* Bug 16254: Disable GeoIP-based search results. >* Bug 16222: Disable WebIDE to prevent remote debugging and addon > downloads. >* Bug 13024: Disable DOM Resource Timing API >* Bug 16340: Disable User Timing API >* Bug 14952: Disable HTTP/2 >* Bug 1517: Reduce precision of time for Javascript >* Bug 13670: Ensure OCSP & favicons respect URL bar domain isolation >* Bug 16311: Fix navigation timing in ESR 38 > * Windows >* Bug 16014: Staged update fails if meek is enabled >* Bug 16269: repeated add-on compatibility check after update (meek > enabled) > * Mac OS >* Use OSX 10.7 SDK >* Bug 16253: Tor Browser menu on OS X is broken with ESR 38 >* Bug 15773: Enable ICU on OS X > * Build System >* Bug 16351: Upgrade our toolchain to use GCC 5.1 >* Bug 15772 and child tickets: Update build system for Firefox 38 >* Bugs 15921+15922: Fix build errors during Mozilla Tryserver builds >* Bug 15864: rename sha256sums.txt to sha256sums-unsigned-build.txt > > >
Re: [Tails-dev] [review] Update on the documentation to build the wiki offline within Tails
elouann: > Dear all, > > the documentation to build the wiki offline within Tails was > outdated[1], please review the following draft: > > http://git.tails.boum.org/elouann/tails/tree/wiki/src/contribute/build/website.mdwn?h=build-the-wiki-offline-within-tails&id=120ee6d7a5d865ce69f24a0c3cf7609c0a2fac5d > > Repository: http://git.tails.boum.org/elouann/tails/ > Branch: build-the-wiki-offline-within-tails Woh! Thank you so much for taking this over! I see that you have no Redmine account so I can't send my review there. Please consider creating yourself one so I can move my nitpicking away from everybody's mailbox :) First of all, I pushed some stuff on doc/9081-build-website-in-tails. So please fetch origin and maybe rename your branch this way (git branch -m doc/9081-build-website-in-tails). It's closer to the way we usually name branches and might prevent you some problems. There here are my comments: * The instructions would look better with numbering as we usually do for steps. Can you try that? Then feel free to do this as well in the Linux section that would benefit from a bit of refreshing. You're allowed to improve the phrasing there as well as an extra exercise! * I prefer small and shorter steps to bigger and more complicated one. Here for example, what about saying, in step 2, to run two commands (apt-get update, then apt-get install), instead of one with &&? That's a detail of course :) * Ah, and in the same step, why not use `sudo` instead of introducing the concept of "running commands as root". We're in Tails so we know how this behaves and this would save you the `exit`. * Please use Docbook-style markup for things like file names. In this case "Persistent" and "ikiwiki.setup". See https://tails.boum.org/contribute/how/documentation/guidelines#index3h1. In the case of the contribute section, I tolerate using the markdown equivalent (`). But beware: not everybody in the doc team might do so :) * Let's replace all occurrences of "wiki" by "website" shall we? It's a shame that the script is still called "build-wiki" (this could be fixed by the way...) but the idea that our website is a wiki is confusing for many as you can't actually interact with it as a wiki... * I'm wondering whether the concepts of "offline" or "local" would be more appropriate to explain what's special about this version of the website. The built version is equally relevant whether you are offline or online and the real difference is that it's built on your computer and only you sees it. But yes, that makes it an version accessible "offline". I have no strong opinion and let you decide on this one. * As a consequence, I feel like this page needs an intro. We're saying "build the website" but I feel like we need to explain people why. What is the result (maybe "a working copy of our website that you can navigate and modify from your computer", "offline" or "locally")? And that this is useful for people writing documentation or translators to verify the result of their change before sending a patch. I would write something about this at the very top of the page. * Avoid saying "easy" and let people decide by themselves whether what we propose is easy. In the case of "easy access to this page", I would myself need to understand the use of it to be able to propose a better phrasing. How do *you* use this link? I personally don't have one and use bookmarks in Tor Browser. * Other than that I added a bunch of simplifications with commits 120ee6d..be707e0. Please check whether you are fine with them. * Also note that you mixed up unrelated commits in your branch. Namely commits 114ec4f, a078471, b3a98c2, and 4d05f2d but hey, I'm so laid-back that I won't even bother you about this :) ___ 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] Fwd: Creating a persistent volumn
Hi, I'm forwarding this to our user support team on tails-b...@boum.org who will take care of your request. NB: This is the development mailing list. Forwarded Message Subject: [Tails-dev] Creating a persistent volumn Date: Sat, 8 Aug 2015 22:26:47 - From: chicc...@sigaint.org Reply-To: The Tails public development discussion list To: tails-dev@boum.org Problem in creating persistent volumn on usb drive Installed and running tails on on usb drive. Now once in tails trying to create a persistent volumn on second usb drive. (Note the second drive had files which were copied to external drive and deleted from second drive) Problem Choose Applications > Tails > Configure Persistent Volumn and then received Error message Error Device /dev/sdb was not created using Tails Installer. What do I do now? Thank you. ___ 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.
