Re: [Tails-dev] extension specification
Oops, I didn't meant to answer this in private. Answering back to the list... Giorgio Maone: On 07/05/2015 18:12, sajolida wrote: Hi Giorgio, A few days ago we finished a wireframe of the extension that we believe is a good start for you to work on. It might still change slightly as we continue discussing small details of it. See https://labs.riseup.net/code/attachments/download/759/extension-20150430.fodg. Looks great, thank you! I'm glad you like it. We also updated the blueprint with some more implementation information. https://tails.boum.org/blueprint/bootstrapping/extension/ See the sections: - Non goals - User scenario and wireframe - Integration in the web assistant - Initial browser detection - Checksum verification - Data source Regarding initial browser detection, I can also provide the JavaScript for browser sniffing and browser-specific web content provision if needed. Yes, that's what we had in mind :) So I'll try to specify that a bit better once we have a prototype of the page to work on. Does all this sounds reasonable to you? Yes it does. Cool! I think that what we need to work on together now is to specify which HTML tools (div, class, etc.) you will need in the code of those web pages to be able to do your stuff. Then tchou and I will start writing the HTML code for those pages. I'd actually feel more comfortable with you providing the HTML written the way you prefer best from a web authoring standpoint, and me developing my interaction code around the structure you come up with, bending it to my needs only if really necessary (e.g. by adding a missing id or class attribute) Ok, so our next step is to work on a prototype of the page. Before you can start coding for real we'll also need a name for the extension. We'll try to sort this out quickly, see #9295. Feel free to comment on the latest proposals. I cast my vote for Download and Verify Tails: unambiguous and future-proof, in case should the verification process change. Yeah, everybody likes this one. We also want to ask you whether you think we should have some written contract for your work with the specifications, deadlines, conditions, and so on. We don't usually do that when we work amongst ourselves but if you require one we can maybe get something. Informal email exchanges like this and the ones you initially contacted me with will work just fine, thank you. Ok. Otherwise, at least regarding the deadlines we'll have to deliver the web assistant to Hivos by the end of the year but we'll do several iterations before that and it would be great to have something on which we can do user testing let's say before July. Does that sound reasonable to you? I'm currently very busy with the Firefox transition to the Electrolysis multi-process architecture (enhancing security through low-privilege content sandboxing), and specifically with adapting NoScript to it and helping developers of other popular and complex add-ons who are facing the same challenges. Therefore, end of July or beginning of August is more realistic IMO, even though I'll do my best to prototype it ASAP. Yeah, that will work for us too. We wanted to do some user testing at a conference in June but we won't have all the rest perfectly ready neither so we'll just test whatever we have. On the upside, you're guaranteed of being provided with an Electrolysis-ready add-on, rather than testing something earlier which only later is found to cause troubles in multi-process Firefox. Nice. I should inform myself better about Electrolysis :) -- sajolida ___ 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] Build failed in Jenkins: build_Tails_ISO_experimental #2263
See https://jenkins.tails.boum.org/job/build_Tails_ISO_experimental/2263/ -- [...truncated 3808 lines...] 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 90 translated messages, 14 fuzzy translations, 7 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 91 translated messages, 13 fuzzy translations, 7 untranslated messages. .. done. 108 translated messages, 2 fuzzy translations, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 91 translated messages, 13 fuzzy translations, 7 untranslated messages. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 0 translated messages, 111 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. ar: ... done. az: .. done. ca: .. done. cs: .. done. cy: .. done. da: .. done. de: .. done. el: .. done. en_GB: .. done. es: .. done. fa: .. done. fi: .. done. fr: .. done. fr_CA: .. done. hr_HR: .. done. hu: .. done. id: .. done. it: .. done. ja: .. done. km: .. done. ko: .. done. lv: .. done. nb: .. done. nl: .. done. pl: .. done. pt: .. done. pt_BR: .. done. ru: .. done. sk: .. done. sk_SK: .. done. sl_SI: .. done. sq: .. done. sr: .. done. sv: .. done. tr: .. done. uk: .. done. zh: .. done. zh_CN: .. done. zh_TW: .. done. * Current translation support in tails ar: 102 translated messages, 4 fuzzy translations, 5 untranslated messages. az: 102 translated messages, 4 fuzzy translations, 5 untranslated messages. ca: 110 translated messages, 1 untranslated message. cs: 110 translated messages, 1 untranslated message. cy: 90 translated messages, 14 fuzzy translations, 7 untranslated messages. da: 110 translated messages, 1 untranslated message. de: 110 translated messages, 1 untranslated message. el: 102 translated messages, 4 fuzzy translations, 5 untranslated messages. en_GB: 110 translated messages, 1 untranslated message. es: 110
Re: [Tails-dev] [review'n'merge:1.4.1] feature/5623-Installer-should-refuse-empty-device
Thanks!. The branch is ready for QA. El 06/05/15 a las 19:36, sajolida escribió: kurono: Hi, Could you please review the text introduced in the liveusb-creator for this ticket? https://labs.riseup.net/code/issues/5623 The modified branch is here: https://git-tails.immerda.ch/kurono/liveusb-creator/log/?h=feature/5623-Installer-should-refuse-empty-device The string in question is: « The selected device does not have a Tails installation, it is required for the upgrade process. » I'd rather say: « The destination device is not a Tails device. You can only upgrade an already installed Tails device. » We're in the process of rethinking the terminology around Tails devices and the installation process. For example we might stop saying devices at some point. But right now the strings in Tails Installer are quite a mess so let's not be too picky and stick with what's currently used in the code. Thanks for asking for reviews of your user strings. Don't hesitate to do that more often. ___ 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] extension specification
intrigeri: sajolida wrote (07 May 2015 16:12:52 GMT) : The v1 part of the URL corresponds to the version of the extension. I would suggest giving its own versioning to the URL scheme used by the extension, instead of re-using the extension's versioning. Otherwise, we'll have to maintain more parallel copies of the same files on our website, and then it'll require tools and automation, and then someone will have to write the code and review it and make it good enough, and then there will be bugs and maintenance burden, etc., you know the drill = the less often that URL scheme version changes, the better. Five minutes later, on second thought: or perhaps the idea is to only support *one* version of the extension at a given time? If that's the case, then the extension will need to detect when it's not supported anymore (how?), and to tell the user about it, and then it'll have to violate the must not embed any user-visible string in its code principle. Food for thought :) Thanks for pushing this discussion forward. Unfortunately, it seems like we're not there yet... Let's consider that someone, who already has some version of the extension installed, lands on the page to download the ISO image (see the wireframe, our idea was to have all this on a same page = under the same URL). Let's say it's called /download or whatever the website leads to. I can see different cases here: A. The user has the latest version of the extension and the extension works fine with this version of the page. Nothing to do, we should go ahead and show the download button (slide 9 of the latest wireframe): https://labs.riseup.net/code/attachments/download/764/extension-20150505.fodg B. It's not the latest version of the extension. This version is incompatible with the version of the page. We can't go forward or otherwise stuff won't work: - How can we detect that? Through a version number in the URL as you are proposing? Wouldn't a version number in the code of the page be more simple? - Then what do we do once we detected that incompatibility? Redirect to a compatible version of the page that we're keeping on the website for backward compatibility? Let's say /download/v0.5? Why not. We should maybe propose to update the extension to its latest version instead. C. It's not the latest version of the extension. This version is compatible with the version of the page but we did a security upgrade of the extension and we want to force people to update. In that case, we need something on the page that says which version of the extension is expected and asks for an upgrade if it doesn't match. That would be a different version of slide 3 but to update instead of install. This wouldn't break the rule of user-visible string in its code since all those strings are on the page, shown or hidden either by the browser and extension detection code on the page or by the extension itself. I feel like the need for an updated version in case of security issue is maybe even stronger than the need for backward compatibility with previous versions (as Firefox checks for updates once per day). So we need something else on top of the mere URL versioning. We need to be able to enforce a given version of the extension on the page. And then, why not use this same mechanism to only support one version of the extension? I think that the case of Tails Upgrader (where you used URL versioning) is quite different from ours. In the case of Tails Upgrader, the software itself, installed on a USB stick, was deciding which URL to fetch, and expecting to find something compatible there. In the case of the extension, the user, through the website and the assistant, lands on some page. And from there, the extension must be able to do its work. The URL is not hard-coded in the extension and the extension doesn't care about which URL it's running from. Does that make sense? ISO DESCRIPTION FILE Just a semi-random suggestion: perhaps including a link to the release notes would give more flexibility in the future. E.g. it might be nice to point users at the release notes while they're downloading the ISO in order to do a full upgrade. Perhaps that can be handled on the website side. Well, it's cheap to stuff this info to the IDF (!), and doing it now may avoid having to deal with an IDF format change in the future, so if it were me, I would just do it. That's now https://labs.riseup.net/code/issues/9386. My only remaining comment is that the threat model doesn't mention attacks, from inside the browser, on the web page that does the verification. Of course, I know you're still waiting for feedback from security experts in this field, so my suggestion may seem premature. However, it seems to me that the entire design of this new bootstrap process relies on the integrity of web pages retrieved from our web site and displayed in a web browser, so perhaps it's not too early to clarify that we don't try to protect
[Tails-dev] Build failed in Jenkins: build_Tails_ISO_testing #43
See https://jenkins.tails.boum.org/job/build_Tails_ISO_testing/43/changes Changes: [bitingbird] + note about download limited by RAM if no persistence (#9226) [bitingbird] more precise folder name (#9226) [bitingbird] add the keyboard layout workaround to the known issues (#9336) [bitingbird] formatting (nothing else) (#9226) [bitingbird] more specific (longer too) (#9226) [intrigeri] Add reminder to next report. [sajolida] Revert formatting (nothing else) (#9226) [sajolida] We need HTML markup inside of div [sajolida] Be affirmative instead of negative (#9226) [amnesia] updated PO files [sajolida] Make anchor consistent with the others [sajolida] Rewrite known issue (#9336) [amnesia] updated PO files [anonym] Add alpha channel incremental upgrade path from 1.4~rc1 to 1.4. [anonym] Updating trace file after uploading 1.4. [anonym] Add alpha channel incremental upgrade path from 1.3.2 to 1.4. [intrigeri] Yay for GRUB2's syslinux configuration support. [intrigeri] Fix an incomplete sentence in blueprint. -- [...truncated 15270 lines...] P: Deconfiguring file /usr/sbin/initctl P: Begin unmounting /selinux... P: Begin unmounting /proc... P: Begin unmounting /dev/pts... P: Begin unmounting filesystems... P: Setting up cleanup function P: Configuring file /etc/hosts P: Configuring file /etc/resolv.conf P: Configuring file /etc/hostname P: Configuring file /bin/hostname P: Configuring file /etc/apt/sources.list OK OK Hit http://deb.tails.boum.org 1.4 Release.gpg Hit http://ftp.us.debian.org wheezy Release.gpg Hit http://security.debian.org wheezy/updates Release.gpg Hit http://deb.tails.boum.org 1.4 Release Hit http://deb.torproject.org obfs4proxy Release.gpg Hit http://deb.tails.boum.org 1.4/main i386 Packages Hit http://ftp.us.debian.org experimental Release.gpg Hit http://security.debian.org wheezy/updates Release Hit http://ftp.us.debian.org jessie Release.gpg Hit http://security.debian.org wheezy/updates/main i386 Packages Hit http://deb.torproject.org wheezy Release.gpg Hit http://ftp.us.debian.org unstable Release.gpg Hit http://security.debian.org wheezy/updates/contrib i386 Packages Ign http://deb.tails.boum.org 1.4/main Translation-en Hit http://deb.torproject.org sid Release.gpg Hit http://ftp.us.debian.org testing Release.gpg Hit http://security.debian.org wheezy/updates/non-free i386 Packages Hit http://ftp.us.debian.org wheezy-backports Release.gpg Hit http://security.debian.org wheezy/updates/contrib Translation-en Hit http://deb.torproject.org obfs4proxy Release Hit http://ftp.us.debian.org wheezy Release Hit http://security.debian.org wheezy/updates/main Translation-en Hit http://ftp.us.debian.org experimental Release Hit http://deb.torproject.org wheezy Release Hit http://security.debian.org wheezy/updates/non-free Translation-en Hit http://ftp.us.debian.org jessie Release Hit http://deb.torproject.org sid Release Hit http://ftp.us.debian.org unstable Release Hit http://deb.torproject.org obfs4proxy/main i386 Packages Hit http://ftp.us.debian.org testing Release Hit http://ftp.us.debian.org wheezy-backports Release Hit http://deb.torproject.org wheezy/main i386 Packages Hit http://ftp.us.debian.org wheezy/main i386 Packages Hit http://ftp.us.debian.org wheezy/contrib i386 Packages Hit http://deb.torproject.org sid/main i386 Packages Hit http://ftp.us.debian.org wheezy/non-free i386 Packages Hit http://ftp.us.debian.org wheezy/contrib Translation-en Hit http://ftp.us.debian.org wheezy/main Translation-en Hit http://ftp.us.debian.org wheezy/non-free Translation-en Hit http://ftp.us.debian.org experimental/main i386 Packages/DiffIndex Hit http://ftp.us.debian.org experimental/main Translation-en/DiffIndex Hit http://ftp.us.debian.org jessie/main i386 Packages Hit http://ftp.us.debian.org jessie/contrib i386 Packages Hit http://ftp.us.debian.org jessie/non-free i386 Packages Hit http://ftp.us.debian.org jessie/contrib Translation-en Hit http://ftp.us.debian.org jessie/main Translation-en Hit http://ftp.us.debian.org jessie/non-free Translation-en Ign http://deb.torproject.org obfs4proxy/main Translation-en Hit http://ftp.us.debian.org unstable/main i386 Packages/DiffIndex Hit http://ftp.us.debian.org unstable/contrib i386 Packages/DiffIndex Ign http://deb.torproject.org wheezy/main Translation-en Ign http://deb.torproject.org sid/main Translation-en Hit http://ftp.us.debian.org unstable/non-free i386 Packages/DiffIndex Hit http://ftp.us.debian.org unstable/contrib Translation-en/DiffIndex Hit http://ftp.us.debian.org unstable/main Translation-en/DiffIndex Hit http://ftp.us.debian.org unstable/non-free Translation-en/DiffIndex Hit http://ftp.us.debian.org testing/main i386 Packages/DiffIndex Hit http://ftp.us.debian.org testing/contrib i386 Packages/DiffIndex Hit http://ftp.us.debian.org testing/non-free i386 Packages/DiffIndex Hit http://ftp.us.debian.org testing/contrib Translation-en/DiffIndex Hit http://ftp.us.debian.org testing/main
[Tails-dev] Jenkins build is back to normal : build_Tails_ISO_testing #44
See https://jenkins.tails.boum.org/job/build_Tails_ISO_testing/44/changes ___ 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] Build failed in Jenkins: build_Tails_ISO_experimental #2264
See https://jenkins.tails.boum.org/job/build_Tails_ISO_experimental/2264/ -- [...truncated 3805 lines...] 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 90 translated messages, 14 fuzzy translations, 7 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 110 translated messages, 1 untranslated message. ... done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 91 translated messages, 13 fuzzy translations, 7 untranslated messages. .. done. 108 translated messages, 2 fuzzy translations, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. ... done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 91 translated messages, 13 fuzzy translations, 7 untranslated messages. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. .. done. 102 translated messages, 4 fuzzy translations, 5 untranslated messages. .. done. 0 translated messages, 111 untranslated messages. .. done. 110 translated messages, 1 untranslated message. .. done. 110 translated messages, 1 untranslated message. ar: .. done. az: .. done. ca: .. done. cs: .. done. cy: .. done. da: .. done. de: .. done. el: .. done. en_GB: .. done. es: .. done. fa: .. done. fi: .. done. fr: .. done. fr_CA: .. done. hr_HR: .. done. hu: .. done. id: .. done. it: .. done. ja: .. done. km: .. done. ko: .. done. lv: .. done. nb: .. done. nl: .. done. pl: .. done. pt: ... done. pt_BR: .. done. ru: done. sk: .. done. sk_SK: .. done. sl_SI: .. done. sq: .. done. sr: .. done. sv: .. done. tr: .. done. uk: .. done. zh: .. done. zh_CN: .. done. zh_TW: .. done. * Current translation support in tails ar: 102 translated messages, 4 fuzzy translations, 5 untranslated messages. az: 102 translated messages, 4 fuzzy translations, 5 untranslated messages. ca: 110 translated messages, 1 untranslated message. cs: 110 translated messages, 1 untranslated message. cy: 90 translated messages, 14 fuzzy translations, 7 untranslated messages. da: 110 translated messages, 1 untranslated message. de: 110 translated messages, 1 untranslated message. el: 102 translated messages, 4 fuzzy translations, 5 untranslated messages. en_GB: 110 translated messages, 1 untranslated message. es: 110
[Tails-dev] Build failed in Jenkins: build_Tails_ISO_stable #389
See https://jenkins.tails.boum.org/job/build_Tails_ISO_stable/389/ -- [...truncated 5346 lines...] Selecting previously unselected package python-fpconst. Unpacking python-fpconst (from .../python-fpconst_0.7.2-5_all.deb) ... Selecting previously unselected package python-soappy. Unpacking python-soappy (from .../python-soappy_0.12.0-4_all.deb) ... Selecting previously unselected package python-debianbts. Unpacking python-debianbts (from .../python-debianbts_1.11_all.deb) ... Selecting previously unselected package python-reportbug. Unpacking python-reportbug (from .../python-reportbug_6.4.4+deb7u1_all.deb) ... Selecting previously unselected package reportbug. Unpacking reportbug (from .../reportbug_6.4.4+deb7u1_all.deb) ... Selecting previously unselected package telnet. Unpacking telnet (from .../telnet_0.17-36_i386.deb) ... Selecting previously unselected package texinfo. Unpacking texinfo (from .../texinfo_4.13a.dfsg.1-10_i386.deb) ... Selecting previously unselected package time. Unpacking time (from .../archives/time_1.7-24_i386.deb) ... Selecting previously unselected package w3m. Unpacking w3m (from .../archives/w3m_0.5.3-8_i386.deb) ... Selecting previously unselected package wamerican. Unpacking wamerican (from .../wamerican_7.1-1_all.deb) ... Selecting previously unselected package whois. Unpacking whois (from .../whois_5.1.1~deb7u1_i386.deb) ... Selecting previously unselected package openssl. Unpacking openssl (from .../openssl_1.0.1e-2+deb7u16_i386.deb) ... Selecting previously unselected package ca-certificates. Unpacking ca-certificates (from .../ca-certificates_20130119+deb7u1_all.deb) ... Selecting previously unselected package iso-codes. Unpacking iso-codes (from .../iso-codes_3.41-1_all.deb) ... Selecting previously unselected package libsasl2-modules:i386. Unpacking libsasl2-modules:i386 (from .../libsasl2-modules_2.1.25.dfsg1-6+deb7u1_i386.deb) ... Selecting previously unselected package lsb-release. Unpacking lsb-release (from .../lsb-release_4.1+Debian8+deb7u1_all.deb) ... Selecting previously unselected package psmisc. Unpacking psmisc (from .../psmisc_22.19-1+deb7u1_i386.deb) ... Selecting previously unselected package tcpd. Unpacking tcpd (from .../tcpd_7.6.q-24_i386.deb) ... Selecting previously unselected package xauth. Unpacking xauth (from .../xauth_1%3a1.0.7-1_i386.deb) ... Selecting previously unselected package xml-core. Unpacking xml-core (from .../xml-core_0.13+nmu2_all.deb) ... Processing triggers for man-db ... Processing triggers for install-info ... Setting up bash-completion (1:2.0-1) ... Setting up libasprintf0c2:i386 (0.18.1.1-9) ... Setting up libcap2:i386 (1:2.22-1.2) ... Setting up libbsd0:i386 (0.4.2-1) ... Setting up libedit2:i386 (2.11-20080614-5) ... Setting up libevent-2.0-5:i386 (2.0.19-stable-3+deb7u1) ... Setting up libgpm2:i386 (1.20.4-6) ... Setting up libkeyutils1:i386 (1.5.5-3+deb7u1) ... Setting up libkrb5support0:i386 (1.10.1+dfsg-5+deb7u3) ... Setting up libk5crypto3:i386 (1.10.1+dfsg-5+deb7u3) ... Setting up libkrb5-3:i386 (1.10.1+dfsg-5+deb7u3) ... Setting up libgssapi-krb5-2:i386 (1.10.1+dfsg-5+deb7u3) ... Setting up libgssglue1:i386 (0.4-2) ... Setting up liblockfile-bin (1.09-5) ... Setting up liblockfile1:i386 (1.09-5) ... Setting up libmagic1:i386 (5.11-2+deb7u8) ... Setting up libsasl2-2:i386 (2.1.25.dfsg1-6+deb7u1) ... Setting up libldap-2.4-2:i386 (2.4.31-2) ... Setting up libnfsidmap2:i386 (0.25-4) ... Setting up libpci3:i386 (1:3.1.9-6) ... Setting up libpcre3:i386 (1:8.30-5) ... Setting up libtirpc1:i386 (0.2.2-5) ... Setting up libtokyocabinet9:i386 (1.4.47-2) ... Setting up libwrap0:i386 (7.6.q-24) ... Setting up geoip-database (20130213-1) ... Setting up libexpat1:i386 (2.1.0-1+deb7u1) ... Setting up libxau6:i386 (1:1.0.7-1) ... Setting up libxdmcp6:i386 (1:1.1.1-1) ... Setting up libxcb1:i386 (1.8.1-2+deb7u1) ... Setting up libx11-data (2:1.5.0-1+deb7u2) ... Setting up libx11-6:i386 (2:1.5.0-1+deb7u2) ... Setting up libxext6:i386 (2:1.3.1-2+deb7u1) ... Setting up libxml2:i386 (2.8.0+dfsg1-7+wheezy4) ... Setting up libxmuu1:i386 (2:1.1.1-1) ... Setting up openssh-blacklist (0.4.1+nmu1) ... Setting up openssh-blacklist-extra (0.4.1+nmu1) ... Setting up libclass-isa-perl (0.36-3) ... Setting up deb.torproject.org-keyring (2014.08.31+b1) ... OK Setting up dselect (1.16.16) ... Setting up python2.7-minimal (2.7.3-6+deb7u2) ... Linking and byte-compiling packages for runtime python2.7... Setting up mime-support (3.52-1+deb7u1) ... Setting up python2.7 (2.7.3-6+deb7u2) ... Setting up python-minimal (2.7.3-4+deb7u1) ... Setting up python (2.7.3-4+deb7u1) ... Setting up python-support (1.0.15) ... Setting up python-apt-common (0.8.8.2) ... Setting up python-apt (0.8.8.2) ... Setting up ucf (3.0025+nmu3) ... Setting up apt-listchanges (2.85.11) ... Creating config file /etc/apt/listchanges.conf with new version Setting up at (3.1.13-2+deb7u1) ... All runlevel operations denied by policy All
[Tails-dev] Would Like to Get Involved Contribute
Hello, I am a new Tails user and am amazed - big congrats to you all on what's been accomplished so far. I'm interested in getting involved and have a background in frontend web development, online marketing (seo, sem, smm, content and email), user acquistion, transifex translation management and ui/ux (emphasis on landing page design/development and conversion rate optimization). After looking at the contribute page and Redmine, I see there is a bunch of stuff to potentially help out on, but thought it might be a good idea to stop by here and say hello and see where help might be most well received at the moment, based on your opinion(s). What's in need of the most help? Or should I just dive in and try to add value wherever I think I may be able to?? Warm regards, Ok Google ___ 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] VeraCrypt
I see you are looking at tcplay to replace TrueCrypt because it supports TC with additional functionality. I think it's a good idea. How do I add VeraCrypt to the list of candidates? VC is a direct upgrade of TC, completely backward compatible with existing TC volumes/containers, can convert them to VC (except encrypted systems), and provides significantly improved encryption algorithms. Since they're all related (TC, VC, tcplay), I bet it wouldn't be too difficult to suport them all - users love choices. And the zuluCrypt gui could handle all 3. A Tails user ___ 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.
