Re: [Tails-dev] (no subject)
this: I want to help translate TAILS Hello: Thanks for your interest in helping Tails. Please read here for how to translate: https://tails.boum.org/contribute/how/translate/ emmapeel ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Proposal: Core Workers are responsible for simplified Monthly Reports
ignifugo: - gitlab change alone the formatting of some issues links - I have the suspect that the flavour of the markdown is different from ikiwiki (who have to publish and have problem, tell me that maybe I can help) I published a couple of reports with this new format, and after fighting with the gitlab formatting issues, I decided to write the reports in a local instance of the website, building it to see the changes and correct errors. Once I was happy with the results, I copied my file on gitlab. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] QR code maker/scanner built in Tails OS
Eirik Slettebø: That would be useful to copy text to and from Tails OS out of the box without a network connection. There is python3-qr to generate QRcodes. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Preparing the next monthly report
emma peel: OK, I am curating the report. Please add your information until Feb. 8, as I want to publish it on Feb.10 Here the link: https://gitlab.tails.boum.org/tails/blueprints/-/wikis/monthly_report/report_2021_01 OK, the report is ready for review'n'merge at https://gitlab.tails.boum.org/tails/tails/-/merge_requests/346 It would be nice to have it published today. It builds ok in local. I hope I didnt forgot to add anything important! emmapeel ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Preparing the next monthly report
OK, I am curating the report. Please add your information until Feb. 8, as I want to publish it on Feb.10 Here the link: https://gitlab.tails.boum.org/tails/blueprints/-/wikis/monthly_report/report_2021_01 If you don't feel like adding the bits yourself, you can send me a private email or ping me on XMPP and I will add them for you. Thanks! ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Preparing the next monthly report
sajolida: Tails: I volunteered to curate the January report some weeks ago but I withdraw myself today. I'm seriously overworked with the UX sprint until February 15 and in Tails in general. I've curated ⅔ of reports since 2017 but I won't curate them anymore. I can curate January's report. Sometimes I have looked at the list of reports to curate some, but it was always full. This monthly report dynamics has been recurrently frustrating for me. What I envisioned as a way of communicating within the project, connecting with the rest of the world, and celebrating our achievements, has felt broken for me for years. I've put a lot of energy in the past to try to change this but I don't have this energy anymore. I'll find elsewhere the information that I need from them. Thanks for curating all those reports, I am sorry you felt that way. Your reports rocked, btw. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] gitlab: more privileges! (please)
I like the gitlab interface, and I think I am starting to feel comfortable on
it.
But I must say that I find uncomfortable the lose of the privileges I have
since moving from Redmine.
I have noticed I am a 'reporter' in gitlab. Is there a reason I am not a
'developer' anymore, like in Redmine? ('Don't it always seem to go, that you
don't know what you've got till it's gone?')
Thing I used to be able to do in Redmine and I cannot do now are:
Editing titles and descriptions of tickets from other people:
-
Sometimes there are tickets that start with not much information, and after
debugging for a while, the problem gets better understood and can be defined.
In Redmine, when this happened I used to edit the tickets title or description
and this made the ticket more understandable without going through the whole
list of comments, and it was also better for when the ticket was on a list.
I feel that we are now duplicating tickets just because we cannot edit them.
Moving tickets from one component to the other
--
I have opened at least one ticket in tails/tails, that I would like to move to
tails/sysadmin: https://gitlab.tails.boum.org/tails/tails/-/issues/17870
But I cannot do it, and is a ticket I opened. I would like to have this
privilege.
Assign tickets to other people
--
I used to be able to assign tickets to sajolida for review or triaging, should
I now do that as a mention? I like to assign because while doing frontdesk I
triage new tickets, and if I assign them to somebody, I get them out of the
'unassigned' pool.
Apologies if this has been already discussed, and thanks for giving me that new
notebook feeling when starting the school year.
signature.asc
Description: OpenPGP digital signature
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Fixing Torrent files for 4.9
intrigeri: > Hi, > > Cyril Brulebois (2020-07-29): >> Maybe we should make sure downloading over bittorrent finishes, and >> not only starts? > > This would make the manual testing session start a bit later (with "a > bit" being more or less long depending on the RM's Internet > connection). What about adding the full Torrent download to the manual > testing session instead? I think it would be easy to start the torrent at the start of the manual testing session, and check if its finished after the other tests have finished. I used to add the torrents to my seedbox while testing, but I haven't done it consistently the last year (as I didn't found any problems in a long time, being only useful a couple of times when the RM already had doubts about the torrent working). This would also give one more seeder to spread the torrents when we actually release. signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Fixing Torrent files for 4.9
Cyril Brulebois: > I'm not sure which part(s) might need some signing, but anything related > to signatures is flashing red alarms here, since it could invalidate > some reproducibility properties (our release process highlights that > once a given point is reached, the GPG hardware token must be stowed > away and never touched back). And I'm also not sure whether publishing > the new Torrent files with similar names but different contents could be > an issue (I'm no Torrent/DHT master). I am not a master (no logs, no masters!) but: In my experience you can - download a torrent to a location - stop it (without deleting the contents) - start another torrent with the same file names That will resume your files, **if they are the same file**. It will at least work for skipping the images download, although the people currently seeding will not be able to seed the whole iso until they download it, and you need to stop-cancel the first torrent without deleting its contents before downloading the second. I think this may be a problem for automated systems like the one we suggest for the Tails mirrors I have tried adding the files to my torrent download folder with scp, but when rehashing i could not convince the app they were the correct file. signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [Tails-project] Call for feedback: *test* migration to GitLab
intrigeri: > Hi, > > we have completed a *test* migration to GitLab: > > https://gitlab.tails.boum.org > > Please play with that GitLab instance and give us feedback. > > The workflow to contribute to Tails remains unchanged until we do the *final* > migration to GitLab: everything you do on GitLab will be lost at some point. > > What was migrated > = > > We have migrated: > > - all information from Redmine, such as issues, milestones, and user accounts > > - a few of our public Git repositories I like that I can easily see all the repos, I find it easier than the old git. > > How to test > === > > To test our upcoming GitLab workflow: > > 1. Activate your GitLab user account > >Follow the "Activate your GitLab user account" section in > > https://salsa.debian.org/tails-team/tails/-/blob/feature/15878-gitlab/wiki/src/contribute/working_together/GitLab/transition.mdwn#L8 > I followed this instructions, but then I got a bit stuck because the system asked me for a confirmation email and didnt show me where to ask it, after following those steps. Finally I saw the 'resent confirmation email' link (this was after I activated my account and decided on a new password) and got a second link to click on, and now I am a confirmed email user. Question: If I make changes on the gitlab repo, for example if i answer to a comment, will this be used later, or I should comment stuff on redmine still? signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] DEDA - Tracking Dots Extraction, Decoding and Anonymisation toolkit
Paul Wise: > I haven't yet seen any evidence of interest in adding it to Debian. > I only just heard about it today and immediately thought of Tails, > presuming that the Tails folks who are Debian members would be able to > bring it to Tails via Debian. It has seen relatively few commits in the > last year so might not need much maintenance. I have opened https://redmine.tails.boum.org/code/issues/17507 so we don't forget about such a pertinent tool, and maybe give ideas to Debian developers that want to help Tails (hint! hint!) Thanks again for keeping Tails on your head! signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] DEDA - Tracking Dots Extraction, Decoding and Anonymisation toolkit
Paul Wise: > Hi folks, > > I recently found out about DEDA, a tool for dealing with the yellow > tracking dots that printers add to printed documents. The dots > anonymisation and customisation features of DEDA seem like something > that some Tails users would appreciate. > > https://github.com/dfd-tud/deda > https://web.archive.org/web/20190805123707/http://www.seeingyellow.com/ ey mr. Wise, thanks for the suggestion! Do you know if there will be a Debian package soon? Adding to Tails software which is not in Debian will imply an additional workload that could compromise the sustainability of the project. On top of that, being in Debian brings many advantages: * It is included in the Debian process for security updates and new versions. * It is authenticated using OpenPGP signatures. * It is under the scrutiny of the Debian community and its many users and derivatives, including Ubuntu. ref. https://tails.boum.org/support/faq/#software signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Why do not all dotfiles/folders get saved in Persistent storage?
Teqleez Motley: > Hi all, something that puzzles me, and also means wasted time again and again: > Please send next emails to tails-support@, this is the development channel. > With persistent storage enabled and functional (restoring extra sofware, > etc.)..; > > - terminal profile settings are not persistent > - wallpaper change and power settings are not persistent > - theme changes and other settings made with dconf-editor are not persistent > - (and several more) > > Why is that? This is really awkward, illogical and wasting time while also > constantly being an annoyance. No good to have such a factor of negativity > that keeps nagging at you each time Tails is restarted. We are working on making some of this settings persistent, see https://redmine.tails.boum.org/code/issues/5979 and related. > > (PS. I have ticked the option to save dotfiles in persistency, and this has > been going on like this across many Tails versions now, both with upgraded > USB sticks and new installations.) Ticking the dotfiles option will not automatically save all your dotfiles. That will likely create troubles along different releases. You have to save copy them to a directory, see instructions at: https://tails.boum.org/doc/first_steps/persistence/configure/#dotfiles signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] [review'n'merge] another typo
ey there, a user reported this typo, please merge if you fancy: https://git-tails.immerda.ch/emmapeel/tails/commit/?h=another_typo&id=60829a0ad8a5c1f597b0f99255191dcde08c1736 thanks, and thanks to the user that reported. signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Do you read the changelog?
anonym: > Hi, Tails contributors! > > As release managers, one of the things we produce is the changelog (i.e. > debian/changelog; we are *not* talking about the release notes). We have the > following questions for you, potential users of this file: > > - Do you read the changelog at all? > - If so, what do you use it for? now that you mention it, i think i read the release notes more than the changelog signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] [review'n'merge] typo on unlock_veracrypt_volumes
ey there!
So, here a small patch to fix the lack of space between two phrases in the
veracypt mounter. thanks to translators for spotting this!
(have a look, maybe you wanted the phrases to appear in two different lines
instead)
emmapeel
From a08bcba8186c9aba721f04781925c90bad75bd28 Mon Sep 17 00:00:00 2001
From: emma peel
Date: Sun, 14 Apr 2019 08:14:27 +
Subject: [PATCH] typo
---
.../python3/dist-packages/unlock_veracrypt_volumes/volume_manager.py| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config/chroot_local-includes/usr/local/lib/python3/dist-packages/unlock_veracrypt_volumes/volume_manager.py b/config/chroot_local-includes/usr/local/lib/python3/dist-packages/unlock_veracrypt_volumes/volume_manager.py
index f6c54bd8b1..f5c46c9daf 100644
--- a/config/chroot_local-includes/usr/local/lib/python3/dist-packages/unlock_veracrypt_volumes/volume_manager.py
+++ b/config/chroot_local-includes/usr/local/lib/python3/dist-packages/unlock_veracrypt_volumes/volume_manager.py
@@ -161,7 +161,7 @@ class VolumeManager(object):
body=_("The file %s does not seem to be a VeraCrypt container.") % path)
else:
self.show_warning(title=_("Failed to add container"),
- body=_("Could not add file container %s: Timeout while waiting for loop setup."
+ body=_("Could not add file container %s: Timeout while waiting for loop setup. "
"Please try using the Disks application instead.") % path)
def _wait_for_loop_setup(self, path: str) -> Union[Volume, None]:
--
2.11.0
signature.asc
Description: OpenPGP digital signature
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
[Tails-dev] frontdesk report weeks 7/8 2019
ey there! A quick report of my last shift, finished on Feb 18th. - Many users are asking how to update electrum... it is getting a bit boring :S They also report on our bug tracker, were there are many duplicated tickets about Electrum upgrade. - I guess this is not news, but the fact that we are having two different images creates problems for users, they use the images for one process to do the other, so I have received reports of 'Not possible to make persistent folder' because the user has installed the ISO with Etcher instead of using the .img, users wiping up their Persistence because of using Etcher to upgrade Tails, and similar. I suspect this two image situation will increase frontdesk workload and frustrate users. - Many users try to verify with GPG without much knowledge about how GPG works, and as the messages they receive are not the ones we show on the docs, they freak out and write to support. I think they don't realize this step is optional. - With the help of TheNerdyAnarchist and other contributor we are trying to take care of the abandoned Tails reddit forum, where I am a moderator now. I thought reddit was similar to stackoverflow, but apparently asking already answered questions is normal in reddit. I was quite disheartened by that! That's it for now, thanks for reading! signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] [ready to publish] January monthly report
ey there! I think that the January report can be published. Thanks to thenerdyanarchist for the help! emmapeel PS: maybe we can add new blueprints for next months? At least the February one? cf. https://tails.boum.org/blueprint/monthly_report/ signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [review'n'merge] Fix additional_software links
intrigeri: > Hi, > > xin: >> Hello, please review and merge. > >> Repo: https://git-tails.immerda.ch/xin/tails/ >> Branch: additional_software_links >> Last Commit: f5e6979b256298691aa07258bc60ffa664adb42b > > Indeed, in commit d21aacde010ed0b7871791016e4a880179ce26e3 > we renamed that page without updating links accordingly, > and no rewrite rule was added. That's annoying, sorry... I thought I had grepped the hell out of the wiki! But yeah the rewrite rule could have been a nice safety measure. Will take that into account next time. signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] [request] catalan translation
Ey there! Could somebody create a blueprint for the new Catalan translators to document their work? It should be called blueprint/l10n_Catalan/ as the other language wikis. Thanks in advance! 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] installing a package with double click
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 intrigeri: > emma peel: >> Would it be possible to install, for example, gdebi, so users can > >> - double-click on a .deb file on Nautilus >> - get asked the admin password >> - install the debian package > > The major problem I have with this (manual) approach is: users won't > get any kind of upgrade for the installed software unless they > consciously and manually go somewhere to check for upgrades. Bug-free, > fully translated software that never needs to be upgraded is > pretty rare. The package will also add a repo where said package is also located and add it to additional-software.conf, so it should be updated automatically when there is a new version on the repo, right? > The approach we support currently is adding new APT sources in > a persistent manner (perhaps in the future we'll support Flatpak > remotes similarly but we're not there yet). I don't know how well this > support works in practice (due to lack of feedback). But setting up and > maintaining an APT repo may not be that much less work than having the > software in Debian proper. YMMV :) The idea is to have a debian package that adds a Debian repository, apart of a graphic interface to install and enable the other apps. Devs wanted to make the bootstrap process easier for non-technical users, so that is why the gdebi idea. But sajolida's suggestion is OK, users can install gdebi through synaptic and not even persist it, and then the rest of the packages can be installed from the repo. The main package will also be on this repo, so it will be easily updated. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuIXY3OAXO0KkAgIfNk4d6ixPiDUFAlth4Y4ACgkQNk4d6ixP iDVd4hAAj3PN+7owTFIvxhFNsbEM1+fUldk0XxpJ9DjAbOOHzVBLcuqknXDq+G6J DKEAJYnDc5D9qA3XgZGKyG+GllsbaViouIIdZq/ToszK8MRNBpauFmci/81CdqeA RJ3cxRmTDJEn/hnV7kWmopORfnqlKWbBp03cJl1YspacDOI4sZDNliCCRl7xFY64 NJ3JQjGsWF3BBU/4OuDHR2ODcf/rMpLQLsTrWH+2XskezZNt6C4W63N2z0sGGk9K 12QX58RjqlQ8vjp+Ao/eTQJ3809GJsDtbBkp1c5iSnbhrlb4wdKUyBeLWdrdxroz D2tPI5lEmULHSs+GIAlwjdZVA81RFUxt9d/xGRcef6OLCTp1pDDi1ILBaAEm3BTN pRAwypVg2r3YwLBHkc14gmIkUYi8yshow+zQUmZVFJ7/c0p7WW8HPzSl34nWF5pN BYJq4zI11dY3NzPqyEPdebNsVvazwfjY04T0g+OeMlY0IfDw5Nfwlok9wZA4UOjH PXvrHTXlqIlghEBWzM5+jaB4YSfplZyuyyhW2V5ChGnTmgHY/xxBKpiP/VnENdv0 vDFlXG57nN/Wg36ZWUStrRgjM12WFeaGHgkXlyxmWIXjtnVuusO7gyWFZCHhk1Dx t5ZIQp8w8S+yfP9BKygj6q5Ub79TtTYdm2AWKcss0FzCpigZa9o= =apIN -END 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.
Re: [Tails-dev] installing a package with double click
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 sajolida: >> I'm not sure if we should make it easy for users to install software >> from untrusted sources. > > Same here especially given that people will be able to install gdebi > using Additional Software. Would this work for these people? > Yeah that was the other option and the one that will probably be used. Thanks! -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuIXY3OAXO0KkAgIfNk4d6ixPiDUFAltdcewACgkQNk4d6ixP iDXaFxAAk6YkbgHETzj4XDgGJRF0DFI7f+92dQnAWFz0CdLKi673NXV+dtqEmv/W 4jSFDLCNs/+Ubgt88AG64FsHpG1cGP8IGy894MtF21O9BsUF4Gh8dmYr5AAGckQH Xg13loSH6oWdyo2cs7vX4Kou57L86JA/hpS9p2l5MBC/PFeTIm/OQ0N9PoMLoXY9 TRuLhVeOkyY2+cUAyIJPGxmhDHhsOdh/WjOjx1Dm3LVgjzB3/mSO0iMlaRjQVsdF p5q4LSmvnVXSsZkvaQZwubbWiVvCCaE7fc+fqMY9RgtBlPqhqY2ZMwgLevPNXDXM NHyq9uqLST1FAzOi57WxyvTWNlroTEFXZfurxcjUhfVkoV9QgtLvPMPtyFM4ILuv obd4mNzDl53IMiKToD+qP6O6S4WZE4w0gMOkuJFtYDoH3Y9fVVM+5FXM2cXQ2ahO lYD0VfAmrv7fXWyLKk/U71dO65Fre+MduuEvKJiH7pszTR4JpWFoqgnmGCgJYGtx X+bj4LHAsO6Q9dt0qAP+Tq5HrtMwt/e1yCKMy1pIHfANS1i3599/ZIwJQVHdTBG6 qEKvF0JtuyQMF0M0MLLxoI/vxaeYzp9YKkvGR8oLw34wRv7SEdKmFK4zGMOcCF6v IdmT0S7CgLxipZZo7JX36ydv9++ICW8LYlBpMg3RfPKVITRjEJg= =9azj -END 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.
Re: [Tails-dev] installing a package with double click
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > gdebi is 169 kB when installed. oops... actually, it is quite more: 11,5 MB Se instalarán los siguientes paquetes adicionales: gconf-service gconf2 gconf2-common gdebi-core gir1.2-vte-2.91 gksu libgconf-2-4 libgksu2-0 python3-apt python3-debian Se instalarán los siguientes paquetes NUEVOS: gconf-service gconf2 gconf2-common gdebi gdebi-core gir1.2-vte-2.91 gksu libgconf-2-4 libgksu2-0 python3-apt python3-debian Se necesita descargar 3.397 kB de archivos. Se utilizarán 11,5 MB de espacio de disco adicional después de esta operación. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuIXY3OAXO0KkAgIfNk4d6ixPiDUFAltcbwwACgkQNk4d6ixP iDW3fw/+NW91+VxKvYn5mQtfKxK0fBvWI/2f3k1j1RaKitSYAvQpCnWTS3IrhRoC abd70Upc0SLoHRTVPkebW+x+O23ZM/T0BFkQtJSbZEURtehW4CNLtDHlUfTlpiVf CJmyhS6cbIGS9uVX/qZGZkQ13owv3uaYwQkth75f264R9tIfQipsMc1EMG3Q8wHe nqnwQbyEPHZA9+pYZjFYH/PJLFED/XHrzqlW6dQexnrAkWCRLLSuxvd7vnEA2ZH1 rj6gmCSJO9bR0GbeqiTDKF/S6Eet2owbcnZ1XUFitMRe+WbUBLEIB1kSAO0DTJPh QXz2Mv3rNgCy8b5vkLbvp78euZO8j48MbMAB28XZzF98adqFsHhaYxWYhxpYgZKp jFUK5R8MOcQkn3ArE7sann2kC2lVxx8GNK0/+StIQ5aMD6ZjW3fJ4AQt9EmcoajQ JevS8pZHbCEC7/zei7UFtdBo95Vmrsz2K9d6V2K8ecuRnffsnaqzUKvdwcLkCjNz lluk3IWeLUNNrKpOlvCrOZKU9uaW4+bIwI1pBMdzvyRuRXHZ5faFjnXJYk0yasFC PzO6d7w2WnX/l1kqdhYn+8bZC4bC0FuwpPkm6uEGoMbs4i3Y5WoVLlcQ6k5+gD+6 pUR7OpzgXepAxY5nsH1XMjXMumG7eyAW1ocbNIY2Kx3qTkacqg0= =YfMH -END 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] installing a package with double click
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 hello: as now we are having so many possibilities with the new Additional Software feature coming, with some friends we are working on some apps that can be used in Tails. We have a nice .deb package for newbie users to be able to install a small catalogue of tools, but we dont fin a way to bootstrap it nicely. Would it be possible to install, for example, gdebi, so users can - - double-click on a .deb file on Nautilus - - get asked the admin password - - install the debian package it is quite straighforward once you have installed it. or maybe there is a way to add a MIME type for Nautilus that will trigger some fancy thing? gdebi is 169 kB when installed. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuIXY3OAXO0KkAgIfNk4d6ixPiDUFAltcW90ACgkQNk4d6ixP iDXEOQ//XFBDF835PTl3Fz4AXeRUHgLhuQGCg9h/fGATj2xY9O3Vzn2tYSChRK++ N51hhNLfJ6xj35Bb8qQYgeIurWLfTV/Ew6bzXCC+OtqCIHCRK4noNkgVvypFvdfO GwrTXrXNL0clEmspcYwAYzWyoZPlfdcFGXbCvdv7smmdGHstXWMAPftea4hSXg2G DccSSgIERgcMEzVZS1f/2xO8dZ+tEkp+aWRZVnnfsuRFQl5A4aEE2+ZEsK7K3E69 2M88F897UuhDKEpWl+DxdqV6Bww1/7za79Y8iOnHLaaH0MnD/pirGWGSVyltNhis EVh1GXhnXIk1Kd00wXOQxPK9kFiHTA9RfAf+LUmnNIPpuM0KoIYWGU7S6hRlwZXa +bHwPOwkR48/7IH1t+PVgwWh2iSeHqHnxyb4DFjtL8N4r9Kfz8briyFTwE9JXnhW yaQ7L/zEZ6ABKtv+gZLj8ARCRJNnhnpPJRrOgPyfbTmU0GkeMzmLD4bL9jSS2LjZ mO07DxMHZwxSSnnUnnKGGUgBgSAVsw603jiapTxA8pyth5aLaC0n8areVdRm4QlI 1YGI2PGoLOLnQEDEdf1jWuRs1aXxq4vRhmlfQvn8EdlJrQFWh3M2OpwNgh8vvxj/ b/2Ya2gNeSP2FBENakLVUocIPKpCZcQGRDhia2LV89ujbKQg6dI= =2LuF -END 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] [review'n'merge] web: force list layout on news/test_asp-beta/ page
a small branch with two commits for the translations to be layed out in a list on the Known issues section at: https://tails.boum.org/news/test_asp-beta/index.es.html and other languages that are not the default. Currently the list layout is not being parsed. It passes check_po, and now the list is rendered. Please review: git.tails.boum.org:emmapeel/tails * [new branch]news-force_list 5af6dc7847 associated changes on .po files 65836f3c4c actual mdwn change git diff --stat tails/master.. wiki/src/news/test_asp-beta.de.po | 7 +-- wiki/src/news/test_asp-beta.es.po | 7 +-- wiki/src/news/test_asp-beta.fa.po | 7 +-- wiki/src/news/test_asp-beta.fr.po | 7 +-- wiki/src/news/test_asp-beta.it.po | 7 +-- wiki/src/news/test_asp-beta.mdwn | 4 ++-- wiki/src/news/test_asp-beta.pt.po | 7 +-- 7 files changed, 32 insertions(+), 14 deletions(-) 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'n'merge] grammar correction for whisperback
intrigeri: > intrigeri: >> emma peel: >>> please review this patch with a grammar correction for WhisperBack. > >> Thanks, this looks good to me. I'll apply this once bertagaz has >> pushed […] > > I've now applied this patch even though it's debatable whether this is > a grammar correction: > > https://en.wikipedia.org/wiki/Serial_comma Any native speakers around? I want to add the 'or' but I have no preferences regarding the comma... 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.
[Tails-dev] [review'n'merge] core files
ey there: please review and merge this super tiny commit: [afef14bd10] remove install/os from core_files Available at git.tails.boum.org:emmapeel/tails * [new branch]corefiles_update I take out the deleted page install/os from the core_files.txt, as it makes `wiki/src/contribute/l10n_tricks/language_statistics.sh` fail. 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.
[Tails-dev] [review'n'merge] report april
ey there: please review/publish the monthly report, i think it is ready: https://tails.boum.org/blueprint/monthly_report/report_2018_04/ 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.
[Tails-dev] bits for the April report anyone?
Hello! Next Monday 7th is the deadline to add things to our April report: https://tails.boum.org/blueprint/monthly_report/report_2018_04/ Add them yourself, or send them to me if you want. Thanks! 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.
[Tails-dev] [review'n'merge] grammar correction for whisperback
ey there:
please review this patch with a grammar correction for WhisperBack.
thanks to kingu at trasifex that spotted it.
From dc00cd0c6c8a63db56f7ffb4308008c1a30b02a0 Mon Sep 17 00:00:00 2001
From: emma peel
Date: Fri, 27 Apr 2018 11:52:50 +
Subject: [PATCH] small grammar correction. thanks kingu@transifex
---
whisperBack/exceptions.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/whisperBack/exceptions.py b/whisperBack/exceptions.py
index 29e0401..2286e99 100644
--- a/whisperBack/exceptions.py
+++ b/whisperBack/exceptions.py
@@ -39,7 +39,7 @@ class MisconfigurationException(WhisperbackException):
def __init__(self, variable):
WhisperbackException.__init__(self,
_("The %s variable was not found in any of the configuration files "
-"/etc/whisperback/config.py, ~/.whisperback/config.py, ./config.py")
+"/etc/whisperback/config.py, ~/.whisperback/config.py, or ./config.py")
% variable)
# Used in encryption.py
--
2.11.0
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.
[Tails-dev] [review'n'merge] changing the distro on the docs
Today a user reported that the additional software repositories doc still mentions jessie instead of stretch. Here a little patch with also the changes in the translation files. Please review and merge if suitable! From be3948da7796b9ff2db9060f7980de8cb64e153d Mon Sep 17 00:00:00 2001 From: emma peel Date: Wed, 25 Apr 2018 06:49:03 + Subject: [PATCH] update distribution in docs after user report --- wiki/src/doc/advanced_topics/additional_software.de.po | 6 +++--- wiki/src/doc/advanced_topics/additional_software.es.po | 12 ++-- wiki/src/doc/advanced_topics/additional_software.fa.po | 6 +++--- wiki/src/doc/advanced_topics/additional_software.fr.po | 12 ++-- wiki/src/doc/advanced_topics/additional_software.it.po | 6 +++--- wiki/src/doc/advanced_topics/additional_software.mdwn | 6 +++--- wiki/src/doc/advanced_topics/additional_software.pt.po | 6 +++--- 7 files changed, 27 insertions(+), 27 deletions(-) diff --git a/wiki/src/doc/advanced_topics/additional_software.de.po b/wiki/src/doc/advanced_topics/additional_software.de.po index 276d24178b..0f37d2d6fe 100644 --- a/wiki/src/doc/advanced_topics/additional_software.de.po +++ b/wiki/src/doc/advanced_topics/additional_software.de.po @@ -236,9 +236,9 @@ msgstr "" #. type: Plain text #, no-wrap msgid "" -" deb tor+http://ftp.us.debian.org/debian/ jessie non-free\n" -" deb tor+http://ftp.us.debian.org/debian/ jessie-backports non-free\n" -" deb tor+http://security.debian.org/ jessie/updates non-free\n" +" deb tor+http://ftp.us.debian.org/debian/ stretch non-free\n" +" deb tor+http://ftp.us.debian.org/debian/ stretch-backports non-free\n" +" deb tor+http://security.debian.org/ stretch/updates non-free\n" msgstr "" #. type: Plain text diff --git a/wiki/src/doc/advanced_topics/additional_software.es.po b/wiki/src/doc/advanced_topics/additional_software.es.po index c3c011619c..dcedea5c82 100644 --- a/wiki/src/doc/advanced_topics/additional_software.es.po +++ b/wiki/src/doc/advanced_topics/additional_software.es.po @@ -251,13 +251,13 @@ msgstr "" #. type: Plain text #, no-wrap msgid "" -" deb tor+http://ftp.us.debian.org/debian/ jessie non-free\n" -" deb tor+http://ftp.us.debian.org/debian/ jessie-backports non-free\n" -" deb tor+http://security.debian.org/ jessie/updates non-free\n" +" deb tor+http://ftp.us.debian.org/debian/ stretch non-free\n" +" deb tor+http://ftp.us.debian.org/debian/ stretch-backports non-free\n" +" deb tor+http://security.debian.org/ stretch/updates non-free\n" msgstr "" -" deb tor+http://ftp.us.debian.org/debian/ jessie non-free\n" -" deb tor+http://ftp.us.debian.org/debian/ jessie-backports non-free\n" -" deb tor+http://security.debian.org/ jessie/updates non-free\n" +" deb tor+http://ftp.us.debian.org/debian/ stretch non-free\n" +" deb tor+http://ftp.us.debian.org/debian/ stretch-backports non-free\n" +" deb tor+http://security.debian.org/ stretch/updates non-free\n" #. type: Plain text #, no-wrap diff --git a/wiki/src/doc/advanced_topics/additional_software.fa.po b/wiki/src/doc/advanced_topics/additional_software.fa.po index 788d5494fb..ce47ce9e35 100644 --- a/wiki/src/doc/advanced_topics/additional_software.fa.po +++ b/wiki/src/doc/advanced_topics/additional_software.fa.po @@ -233,9 +233,9 @@ msgstr "" #. type: Plain text #, no-wrap msgid "" -" deb tor+http://ftp.us.debian.org/debian/ jessie non-free\n" -" deb tor+http://ftp.us.debian.org/debian/ jessie-backports non-free\n" -" deb tor+http://security.debian.org/ jessie/updates non-free\n" +" deb tor+http://ftp.us.debian.org/debian/ stretch non-free\n" +" deb tor+http://ftp.us.debian.org/debian/ stretch-backports non-free\n" +" deb tor+http://security.debian.org/ stretch/updates non-free\n" msgstr "" #. type: Plain text diff --git a/wiki/src/doc/advanced_topics/additional_software.fr.po b/wiki/src/doc/advanced_topics/additional_software.fr.po index 265b51adb3..eaeee98797 100644 --- a/wiki/src/doc/advanced_topics/additional_software.fr.po +++ b/wiki/src/doc/advanced_topics/additional_software.fr.po @@ -244,13 +244,13 @@ msgstr "" #. type: Plain text #, no-wrap msgid "" -" deb tor+http://ftp.us.debian.org/debian/ jessie non-free\n" -" deb tor+http://ftp.us.debian.org/debian/ jessie-backports non-free\n" -" deb tor+http://security.debian.org/ jessie/updates non-free\n" +" deb tor+http://ftp.us.debian.org/debian/ stretch non-free\n" +" deb tor+http://ftp.us.debian
[Tails-dev] [review'n'merge] new link for enigmail howto
hello! The Enigmail Howto link at 'OpenPGP encryption with Enigmail' is broken in: https://tails.boum.org/doc/anonymous_internet/thunderbird/ I have replaced it with another Quick Start Guide, I hope it was the same. Please review: repo: https://git-tails.immerda.ch/emmapeel/tails/ branch: new_enigmail_howto Two commits: first is the change, second the .PO refresh and unfuzzy. https://git-tails.immerda.ch/emmapeel/tails/log/?h=new_enigmail_howto 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] New support page /support/known_issues/graphics
Ey! Nice page! It makes it much more clear than now, I think. I answer questions inline here: sajolida: > I'm sending here for review a draft of a new page of known issues only > for graphics cards. > > This is related to the restructuring of our support pages that we > proposed with Cody on https://tails.boum.org/blueprint/support_page/ > and triggered by the new error message when GDM fails to start (#14521). > > You can see the structure here: > > https://git.tails.boum.org/tails/diff/wiki/src/support/known_issues/graphics.mdwn?h=doc/15399-gdm-debugging > > I'd like the Foundations team and Help desk to have a look and comment > before I start migrating all the data we currently have in > /support/knowns_issues.mdwn. > > For example, I'm wondering: > > - Shall we advertise people to try the "Troubleshooting Mode"? Does it > help with graphics cards? > It helps to boot on some cards when the driver is not working. But those users maybe can use a specific boot option to solve their hardware support problem. > - Does it make sense to link to Redmine tickets? For example, #11095 for > Radeon HD was closed because we had nothing else to do but the problem > still exist. > > Is it worth making this information visible to users? Yes, hopefully we could fix old issues maybe, or close them as resolved.> > Is it helpful to keep it hidden in an HTML comment like I did? > I didn't saw that. > - Is it worth keeping track of when each issue has been updated last? > Here I'm proposing to keep this information in an HTML comment. This would be a great information to have. Sometimes I look at the Tails version on the issue to have a similar information. > This is information that we can get from the Git history (I tried and > it takes a couple of minutes) but I thought that it might help > cleaning the page from now and then. I thought about doing this for > the other known issues pages as well. > > - It would be good to have names and IDs of graphics cards exactly as > they are displayed to people. Right now I bet that it's not the case > but the page will get better as people report errors. Yes. I agree. > Are their ways for Technical writers and Help desk to complete or > verify this information? For example, could we answer questions like: > > - « How can I know the ID of "Radeon HD 8790M"? » I ask users many times to give me the output of lspci, and it also comes on WhisperBack > - « What name is displayed to the users of "Radeon HD 8790M"? » I look this up on the Internet but sometimes it is difficult, specially when users tell you a 'laptop model' with several probable graphic cards. > > - Is the "(rev XXX)" part of the graphics card description relevant? > > If so I'll have to talk about "name, ID, and revision" instead of only > "name and ID". I don't know, I guess yes. I think it may be a different card then. Are you sure it is said 'graphics card'? I always thought it was 'graphic card'/'graphic cards'. 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.
[Tails-dev] [review'n'merge] small patch fixing the date
hello: my local wiki builds are failing because of a bad date, here a patch to review and merge. From a2d71afa39d0c45625e430f0b84ac06fb002a71e Mon Sep 17 00:00:00 2001 From: emma peel Date: Sun, 11 Mar 2018 11:44:13 + Subject: [PATCH] rfc-2822 cmpliant date --- wiki/src/news/report_2018_02.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/src/news/report_2018_02.mdwn b/wiki/src/news/report_2018_02.mdwn index e477ff65a6..f23ad38b02 100644 --- a/wiki/src/news/report_2018_02.mdwn +++ b/wiki/src/news/report_2018_02.mdwn @@ -1,5 +1,5 @@ [[!meta title="Tails report for February, 2018"]] -[[!meta date="Tue Mar 6 12:34:56 2018)"]] +[[!meta date="Tue, 6 Mar 2018 12:34:56Z"]] [[!toc]] -- 2.11.0 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.
[Tails-dev] [review'n'merge] another grammar correction
Another little grammar error, this time with the unfuzzied PO files on the second patch. Please merge if you fancy From 60cfd5ef3e2f406c2bac2a2fed53f2779f7a6321 Mon Sep 17 00:00:00 2001 From: emma peel Date: Mon, 26 Feb 2018 11:48:54 + Subject: [PATCH 1/2] small grammar correction --- wiki/src/support/faq.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/src/support/faq.mdwn b/wiki/src/support/faq.mdwn index 73e29e9560..6ffed7e427 100644 --- a/wiki/src/support/faq.mdwn +++ b/wiki/src/support/faq.mdwn @@ -331,7 +331,7 @@ including Debian and Ubuntu, when installing a regular system. Currently the default cipher is `aes-cbc-essiv:sha256` with a key size of 256 bits. -To understand better how persistence work, see our [[design +To understand better how persistence works, see our [[design document|contribute/design/persistence]]. -- 2.11.0 From 7ff756c67c5cef3556be4f416b00bc231c129899 Mon Sep 17 00:00:00 2001 From: emma peel Date: Mon, 26 Feb 2018 11:54:13 + Subject: [PATCH 2/2] Updates to PO files --- wiki/src/support/faq.de.po | 2 +- wiki/src/support/faq.es.po | 2 +- wiki/src/support/faq.fa.po | 3 +-- wiki/src/support/faq.fr.po | 2 +- wiki/src/support/faq.it.po | 2 +- wiki/src/support/faq.pt.po | 2 +- 6 files changed, 6 insertions(+), 7 deletions(-) diff --git a/wiki/src/support/faq.de.po b/wiki/src/support/faq.de.po index 0ec76c781b..0b3e119f37 100644 --- a/wiki/src/support/faq.de.po +++ b/wiki/src/support/faq.de.po @@ -688,7 +688,7 @@ msgstr "" #. type: Plain text msgid "" -"To understand better how persistence work, see our [[design document|" +"To understand better how persistence works, see our [[design document|" "contribute/design/persistence]]." msgstr "" diff --git a/wiki/src/support/faq.es.po b/wiki/src/support/faq.es.po index 64599f44a0..456f921665 100644 --- a/wiki/src/support/faq.es.po +++ b/wiki/src/support/faq.es.po @@ -735,7 +735,7 @@ msgstr "" #. type: Plain text msgid "" -"To understand better how persistence work, see our [[design document|" +"To understand better how persistence works, see our [[design document|" "contribute/design/persistence]]." msgstr "" diff --git a/wiki/src/support/faq.fa.po b/wiki/src/support/faq.fa.po index 957f8a2d77..939d8028ae 100644 --- a/wiki/src/support/faq.fa.po +++ b/wiki/src/support/faq.fa.po @@ -865,9 +865,8 @@ msgid "" msgstr "" "در Øا٠Øاضر ساÛÙر Ù¾ÛØ´âÙرض `aes-cbc-essiv:sha256` با ÛÚ© Ú©ÙÛد ۲۵۶بÛØªÛ Ø§Ø³Øª." -#. type: Plain text msgid "" -"To understand better how persistence work, see our [[design document|" +"To understand better how persistence works, see our [[design document|" "contribute/design/persistence]]." msgstr "" "Ø¨Ø±Ø§Û Ø¯Ø±Ú© بÙتر ÙØÙÙ٠ع٠Ùکرد ٠اÙا [[سÙد طراØÛ|contribute/design/persistence]] " diff --git a/wiki/src/support/faq.fr.po b/wiki/src/support/faq.fr.po index a6ca215137..5a526d9ac7 100644 --- a/wiki/src/support/faq.fr.po +++ b/wiki/src/support/faq.fr.po @@ -873,7 +873,7 @@ msgstr "" #. type: Plain text msgid "" -"To understand better how persistence work, see our [[design document|" +"To understand better how persistence works, see our [[design document|" "contribute/design/persistence]]." msgstr "" "Pour mieux comprendre comment fonctionne la persistance, voir notre " diff --git a/wiki/src/support/faq.it.po b/wiki/src/support/faq.it.po index 3598e8e83f..871a2a284d 100644 --- a/wiki/src/support/faq.it.po +++ b/wiki/src/support/faq.it.po @@ -823,7 +823,7 @@ msgstr "" #. type: Plain text msgid "" -"To understand better how persistence work, see our [[design document|" +"To understand better how persistence works, see our [[design document|" "contribute/design/persistence]]." msgstr "" "Per comprendere meglio come lavora il volume di persistenza, consulta il " diff --git a/wiki/src/support/faq.pt.po b/wiki/src/support/faq.pt.po index 0766cb00df..76f0cf3424 100644 --- a/wiki/src/support/faq.pt.po +++ b/wiki/src/support/faq.pt.po @@ -857,7 +857,7 @@ msgstr "" #. type: Plain text msgid "" -"To understand better how persistence work, see our [[design document|" +"To understand better how persistence works, see our [[design document|" "contribute/design/persistence]]." msgstr "" "Para entender melhor como a persistência funciona, veja nosso [[documento de " -- 2.11.0 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.
[Tails-dev] [review'n'merge] small typo on the FAQ
Hello: Please review this patch for a typo on the FAQ page Only one char! From 246e6aded1dee1c2036dc6425b7bd369fc892dd4 Mon Sep 17 00:00:00 2001 From: emma peel Date: Sun, 25 Feb 2018 12:04:28 + Subject: [PATCH] typo --- wiki/src/support/faq.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/src/support/faq.mdwn b/wiki/src/support/faq.mdwn index 5e88e4c173..73e29e9560 100644 --- a/wiki/src/support/faq.mdwn +++ b/wiki/src/support/faq.mdwn @@ -325,7 +325,7 @@ the one we recommend for [[creating and using encrypted volumes|doc/encryption_and_privacy/encrypted_volumes]] in general. LUKS is a very popular standard for disk encryption in Linux. LUKS is the -default technique for full-disk encryption proposed by many distribution, +default technique for full-disk encryption proposed by many distributions, including Debian and Ubuntu, when installing a regular system. Currently the default cipher is `aes-cbc-essiv:sha256` with a key size of 256 -- 2.11.0 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] [Tails-project] Tails contributors meeting: Tuesday March 06
sajolida: > The next Tails contributors meeting is scheduled for: > > Saturday 03 March > tails-dev on conference.riseup.net (XMPP) I think it is going to be the 6th, as it falls in a weekend. 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.
[Tails-dev] [review'n'merge] small patch for language_statistics.sh
yo!
here I add Spanish to the
wiki/src/contribute/l10n_tricks/language_statistics.sh script that makes the
numbers of translation files each month.
1 file changed, 1 insertion(+), 1 deletion(-)
easy peasy!(famous last words)
please review
From 002e2ce2821294cd07cb800a03a5028bd58211ee Mon Sep 17 00:00:00 2001
From: emma peel
Date: Sat, 17 Feb 2018 06:46:55 +
Subject: [PATCH] add Spanish to the language statistics script
---
wiki/src/contribute/l10n_tricks/language_statistics.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/wiki/src/contribute/l10n_tricks/language_statistics.sh b/wiki/src/contribute/l10n_tricks/language_statistics.sh
index 35e5ce0b7a..75fb40d2c6 100755
--- a/wiki/src/contribute/l10n_tricks/language_statistics.sh
+++ b/wiki/src/contribute/l10n_tricks/language_statistics.sh
@@ -6,7 +6,7 @@ set -e
set -u
set -o pipefail
-LANGUAGES=${@:-de fa fr it pt}
+LANGUAGES=${@:-de es fa fr it pt}
count_msgids () {
cat | grep -E '^msgid\s+' | wc -l
--
2.11.0
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.
[Tails-dev] [review'n'merge] small typo
Hello: Here a low priority typo fix, can be reviewed on attached patches and also at https://git-tails.immerda.ch/emmapeel/tails/log/?h=doc/typo-greeter-docs From 161c3805ecc38226df9676865be7b5ecbb713eaa Mon Sep 17 00:00:00 2001 From: emma peel Date: Thu, 27 Apr 2017 11:02:28 + Subject: [PATCH 1/2] small typo fix --- wiki/src/doc/first_steps/startup_options.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/src/doc/first_steps/startup_options.mdwn b/wiki/src/doc/first_steps/startup_options.mdwn index 6ff7077120..c958db1c0f 100644 --- a/wiki/src/doc/first_steps/startup_options.mdwn +++ b/wiki/src/doc/first_steps/startup_options.mdwn @@ -47,7 +47,7 @@ Using Tails Greeter Tails Greeter is the set of dialogs that appear after the Boot Loader Menu, but before the -GNOME Desktop appears. This is how to first +GNOME Desktop appears. This is how the first screen of Tails Greeter looks like: [[!img tails-greeter-welcome-to-tails.png link=no alt="Welcome to Tails. More -- 2.11.0 From 2d20f35bc2e769795140a9956f76e22295a93631 Mon Sep 17 00:00:00 2001 From: emma peel Date: Thu, 27 Apr 2017 11:02:57 + Subject: [PATCH 2/2] corresponding changes for .po files --- wiki/src/doc/first_steps/startup_options.de.po | 11 --- wiki/src/doc/first_steps/startup_options.fa.po | 13 - wiki/src/doc/first_steps/startup_options.fr.po | 17 - wiki/src/doc/first_steps/startup_options.it.po | 13 - wiki/src/doc/first_steps/startup_options.pt.po | 13 - 5 files changed, 44 insertions(+), 23 deletions(-) diff --git a/wiki/src/doc/first_steps/startup_options.de.po b/wiki/src/doc/first_steps/startup_options.de.po index f159e6a56a..f606505504 100644 --- a/wiki/src/doc/first_steps/startup_options.de.po +++ b/wiki/src/doc/first_steps/startup_options.de.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: 2017-02-25 15:24+0100\n" +"POT-Creation-Date: 2017-04-27 10:59+\n" "PO-Revision-Date: 2017-04-17 16:53+0100\n" "Last-Translator: spriver \n" "Language-Team: \n" @@ -141,11 +141,16 @@ msgid "Using Tails Greeter\n" msgstr "Benutzung des Tails Greeter\n" #. type: Plain text -#, no-wrap +#, fuzzy, no-wrap +#| msgid "" +#| "Tails Greeter is the set of dialogs that\n" +#| "appear after the Boot Loader Menu, but before the\n" +#| "GNOME Desktop appears. This is how to first\n" +#| "screen of Tails Greeter looks like:\n" msgid "" "Tails Greeter is the set of dialogs that\n" "appear after the Boot Loader Menu, but before the\n" -"GNOME Desktop appears. This is how to first\n" +"GNOME Desktop appears. This is how the first\n" "screen of Tails Greeter looks like:\n" msgstr "" "Als Tails Greeter werden mehrere Dialoge bezeichnet,\n" diff --git a/wiki/src/doc/first_steps/startup_options.fa.po b/wiki/src/doc/first_steps/startup_options.fa.po index b777d79ef3..4a9d36c0af 100644 --- a/wiki/src/doc/first_steps/startup_options.fa.po +++ b/wiki/src/doc/first_steps/startup_options.fa.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: tails-l...@boum.org\n" -"POT-Creation-Date: 2017-02-25 15:24+0100\n" +"POT-Creation-Date: 2017-04-27 10:59+\n" "PO-Revision-Date: 2015-10-10 06:50+\n" "Last-Translator: sprint5 \n" "Language-Team: Persian <http://weblate.451f.org:8889/projects/tails/"; @@ -167,7 +167,7 @@ msgstr "استÙاد٠از Ø®Ùشا٠دگÙÛ ØªÛ msgid "" "Tails Greeter is the set of dialogs that\n" "appear after the Boot Loader Menu, but before the\n" -"GNOME Desktop appears. This is how to first\n" +"GNOME Desktop appears. This is how the first\n" "screen of Tails Greeter looks like:\n" msgstr "" "Ø®Ùشا٠دگÙÛ ØªÛÙز ٠ج٠ÙعÙâØ§Û Ø§Ø² ÙÙشتÙâÙا است Ú©Ù\n" @@ -252,13 +252,16 @@ msgstr "" #, fuzzy #~| msgid "" -#~| "Here is a list of options that you can add to the boot\n" +#~| "Here is a list of options that you can add to the boot\n" #~| "menu:\n" #~ msgid "" -#~ "Here is a list of options that you can add to the Boot\n" +#~ "Here is a list of options that you can add to the Boot\n" #~ "Loader Menu:\n" #~ msgstr "" -#~ "اÛÙâجا ÙÙØ±Ø³ØªÛ Ø§Ø² گزÛÙÙâÙاÛÛ Ù ÛâبÛÙÛد Ú©Ù Ù ÛâتÙاÙÛد ب٠ÙÙرست Ù ÙÙ\n" +#~ "اÛÙâجا ÙÙØ±Ø³ØªÛ Ø§Ø² گزÛÙÙâÙاÛÛ Ù ÛâبÛÙÛد Ú©Ù Ù ÛâتÙاÙÛد ب٠ÙÙرست Ù ÙÙ\n"
[Tails-dev] [review'n'merge] december report
Hello: please review the December report and merge if suitable. thanks! ta...@git.tails.boum.org:emmapeel/tails de1295b..95d9e4c web/December_report -> web/December_report 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.
[Tails-dev] December report
Hallo! So, vacations are over and I want to finish the December report: https://tails.boum.org/blueprint/monthly_report/report_2016_12/ I noticed I have the "what"s, but I am mostly missing the "why"s in this report. If you are working on some of the topics maybe you can add a comment about why is this important for Tails etc. if you feel something else is missing, please add! you can also mail me some info and i add it with links etc. Deadline is: Sunday 29 23:00 UTC thanks! 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.
[Tails-dev] [review'n'merge] january contributors meeting - notes
hello: here the notes for the monthly meeting, sorry for the delay! please merge! From 21815d629936e2bf3c166539ab42962a53ecbdb5 Mon Sep 17 00:00:00 2001 From: emma peel Date: Mon, 23 Jan 2017 19:13:15 + Subject: [PATCH] january contributors meeting notes --- wiki/src/contribute/meetings/201701.mdwn | 42 1 file changed, 42 insertions(+) create mode 100644 wiki/src/contribute/meetings/201701.mdwn diff --git a/wiki/src/contribute/meetings/201701.mdwn b/wiki/src/contribute/meetings/201701.mdwn new file mode 100644 index 000..93c58fb --- /dev/null +++ b/wiki/src/contribute/meetings/201701.mdwn @@ -0,0 +1,42 @@ +[[!meta title="January 2017 online meeting"]] + +[[!toc levels=1]] + +# Availability for next month: + +- u will be available and will try to close tickets in January, and + work on a Debian backport for Tails Installer. +- spriver will keep at [[!tails_ticket 9833 desc="Replace AdBlock Plus with uBlock Origin"]] + and work on her other tickets. +- anonym will come back to his "office hours" in two days and will work on [[!tails_ticket 7870 desc="Include OnionShare"]] + + test suite stuff + Tails 2.10 release management + mentoring spriver for #9833. +- emmapeel will not have much time, she will do the December report. + +# Holes on the roof + +- anonym has one assigned + +# Volunteers to handle important tickets flagged for next release, but without assignee + +- All the tickets for Tails 2.10 were already assigned! + +# Tickets discussed + +## [[!tails_ticket 6972 desc="Create a 'Sponsors' page"]] + +- We discussed for a while about the pros and cons of a sponsor page. +- We agreed easily on no sponsors on the homepage, although on a separated page + it would be nice. +- We don't publish the minimum amount needed to be there, as it can change. +- Many other questions arise: + - We renovate the page each year, like the press page? + - Should past sponsors be listed? + - How should we communicate to interested sponsors (have a public policy)? + +We want somebody to write a text that can be sent to possible sponsors +explaining how this works. + +## [[!tails_ticket 12076 desc="Have a sponsor per release"]] + +We discussed it a bit, in general we didn't liked the idea, but we didn't +reach a proper conclusion. -- 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.
[Tails-dev] [review'n'merge] Meeting minutes, Tails contributors meeting Dec 3 2016
Hello world! Here I attach a patch for the meeting minutes for December... please review and merge if suitable. From 137557ac826cc453a1be1e5f4db90608e8804bd0 Mon Sep 17 00:00:00 2001 From: "emma.peel" Date: Thu, 22 Dec 2016 14:52:37 + Subject: [PATCH] meeting minutes --- wiki/src/contribute/meetings/201612.mdwn | 64 1 file changed, 64 insertions(+) create mode 100644 wiki/src/contribute/meetings/201612.mdwn diff --git a/wiki/src/contribute/meetings/201612.mdwn b/wiki/src/contribute/meetings/201612.mdwn new file mode 100644 index 000..17ca38a --- /dev/null +++ b/wiki/src/contribute/meetings/201612.mdwn @@ -0,0 +1,64 @@ +[[!meta title="December 2016 online meeting"]] + +[[!toc levels=1]] + +# Holes on the roof + +Alant is working on the Greeter, so [[!tails_ticket 5318]] is for him. + +# Volunteers to handle important tickets flagged for next release, but without assignee + +After some looking we got 3 tickets assigned: + +- [[!tails_ticket 12015 desc="Upgrade Tor to 0.2.8.10"]] for intrigeri +- [[!tails_ticket 7700 desc="Have a distribution mechanism for the revocation + certificate of our signing key"]] and [[!tails_ticket 11920 desc="Remove + the FAQ on commercial SSL certificate once boum.org has Let's Encrypt"]] for + sajolida + +# Availability for next month: + +- intrigeri: as usual; plans: a Stretch sprint, 1 invoicing round, and helping + people give good input to sajolida for next SponsorS proposal. And attend 60% + of the reproducible builds summit! +- spriver: probably attending CCC, work a bit on #11669 again, and on #11822 +- sajolida: availability: continue with the donation campaign and prepare the + OTF concept note +- alant: I'll be randomly available as usual, but I'll participate to the next + Stretch sprint to include the revamped greeter in it, plus help on other + topics I'm knowledgeable about +- emmapeel will have some time for docs + +# Tickets discussed + +## [[!tails_ticket 11884 desc="Document using Tor bridges to work around missing entry guards"]] + +The proposal has some sense, but then we will be providing the information only +for power users, not for the majority of Tails users. +As in some months we will actually be able to provide entry guards, then we +decided to give it a low priority and suggest to put it in "Confirmation +attacks" on doc/about/warning, mentioning the risk/benefit decision one must +make about location tracking. + +## [[!tails_ticket 11969 desc="Revisit scrolling settings, Stretch edition"]] + +We decided to rather drop our customisation (as most of the OS are doing natural +scrolling now) and let GNOME+libinput do what they think is best, i.e. natural +scrolling in most cases. + +This way we keep reducing our delta with upstream. + +## [[!tails_ticket 12003 desc="Set a warning message in RCs and alpha releases from Tails 3.0 on"]] + +We realised that we were maybe exaggerating when giving ISO images for testing +to the users, at least for Tails 3.x, and that the ISOs could sometimes have +bugs and glitches but they are passing all the security tests, at least on the +Release Candidates (RC) or for example Tails 3.0~alpha1. + +So maybe there are some bugs but not security issues. + +We decided to change the background to grey and add a warning saying: + +"Hey, you are running Tails 3.0 alpha. It is safe to use but might still be +broken in many ways. Report any problems to tails-test...@boum.org" and a grey +background. -- 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.
[Tails-dev] [review'n'merge] Meeting minutes, Tails contributors meeting Dec 3 2016
Hello world! Here I attach a patch for the meeting minutes for December... please review and merge if suitable. From 137557ac826cc453a1be1e5f4db90608e8804bd0 Mon Sep 17 00:00:00 2001 From: "emma.peel" Date: Thu, 22 Dec 2016 14:52:37 + Subject: [PATCH] meeting minutes --- wiki/src/contribute/meetings/201612.mdwn | 64 1 file changed, 64 insertions(+) create mode 100644 wiki/src/contribute/meetings/201612.mdwn diff --git a/wiki/src/contribute/meetings/201612.mdwn b/wiki/src/contribute/meetings/201612.mdwn new file mode 100644 index 000..17ca38a --- /dev/null +++ b/wiki/src/contribute/meetings/201612.mdwn @@ -0,0 +1,64 @@ +[[!meta title="December 2016 online meeting"]] + +[[!toc levels=1]] + +# Holes on the roof + +Alant is working on the Greeter, so [[!tails_ticket 5318]] is for him. + +# Volunteers to handle important tickets flagged for next release, but without assignee + +After some looking we got 3 tickets assigned: + +- [[!tails_ticket 12015 desc="Upgrade Tor to 0.2.8.10"]] for intrigeri +- [[!tails_ticket 7700 desc="Have a distribution mechanism for the revocation + certificate of our signing key"]] and [[!tails_ticket 11920 desc="Remove + the FAQ on commercial SSL certificate once boum.org has Let's Encrypt"]] for + sajolida + +# Availability for next month: + +- intrigeri: as usual; plans: a Stretch sprint, 1 invoicing round, and helping + people give good input to sajolida for next SponsorS proposal. And attend 60% + of the reproducible builds summit! +- spriver: probably attending CCC, work a bit on #11669 again, and on #11822 +- sajolida: availability: continue with the donation campaign and prepare the + OTF concept note +- alant: I'll be randomly available as usual, but I'll participate to the next + Stretch sprint to include the revamped greeter in it, plus help on other + topics I'm knowledgeable about +- emmapeel will have some time for docs + +# Tickets discussed + +## [[!tails_ticket 11884 desc="Document using Tor bridges to work around missing entry guards"]] + +The proposal has some sense, but then we will be providing the information only +for power users, not for the majority of Tails users. +As in some months we will actually be able to provide entry guards, then we +decided to give it a low priority and suggest to put it in "Confirmation +attacks" on doc/about/warning, mentioning the risk/benefit decision one must +make about location tracking. + +## [[!tails_ticket 11969 desc="Revisit scrolling settings, Stretch edition"]] + +We decided to rather drop our customisation (as most of the OS are doing natural +scrolling now) and let GNOME+libinput do what they think is best, i.e. natural +scrolling in most cases. + +This way we keep reducing our delta with upstream. + +## [[!tails_ticket 12003 desc="Set a warning message in RCs and alpha releases from Tails 3.0 on"]] + +We realised that we were maybe exaggerating when giving ISO images for testing +to the users, at least for Tails 3.x, and that the ISOs could sometimes have +bugs and glitches but they are passing all the security tests, at least on the +Release Candidates (RC) or for example Tails 3.0~alpha1. + +So maybe there are some bugs but not security issues. + +We decided to change the background to grey and add a warning saying: + +"Hey, you are running Tails 3.0 alpha. It is safe to use but might still be +broken in many ways. Report any problems to tails-test...@boum.org" and a grey +background. -- 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 and merge feature/7752-keyringer
On Sat, 31 Jan 2015 09:42:46 + sajolida wrote: > Ticket: https://labs.riseup.net/code/issues/7752 > Branch: feature/7752-keyringer into devel > Milestone: 1.3 > > The doc is ready now, so please have a look and merge. > At the end of the documentation it says: Make sure to update your *dotfiles* each time you use the **init**, **teardown**, **destroy**, or **preferences** command of *keyringer*. But I don't really understand from this phrase what is it I have to do to update. Do I have to run the previous command? If so, I would change it for Make sure you do this to update your *dotfiles* each time you use the **init**, **teardown**, **destroy**, or **preferences** command of *keyringer*. (but English is not my language, maybe there is a nicer version) 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.
Re: [Tails-dev] Windows camouflage for Jessie/GNOME shell
On Sat, 06 Dec 2014 21:25:03 +0100 intrigeri wrote: > Hi, > > Griffin Boyce wrote (06 Dec 2014 20:02:55 GMT) : > > I work with lots of end-users who actually use the windows > > camouflage feature, so I'd like to press for its inclusion if at > > all possible. > > I guess we'll blog about it as soon as it's clear what needs to be > done, and how to help -- that'll be the best way to press for its > inclusion :) > > Still: it would be truly good to have more info wrt. what are the > exact use cases that this feature is currently covering. > Users like the camouflage to be in the Library, or in the University. Actually there were some complaints when we switched to Windows 8 because many Windows computers (between which you want to camouflage) are not so new. I agree with asking for external help, but I think not having Windows camouflage will create some users a problem... 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.
Re: [Tails-dev] keeping up with transports
On Wed, 19 Nov 2014 12:50:12 +0100 intrigeri wrote: > I'm not sure what problem you're trying to solve here. Let me try > harder. > > If it's about "users always ask if $PT is supported and we need to be > able to point them to some already written answer", then the list of > bridges/PT types we support is maintained on > https://tails.boum.org/doc/first_steps/startup_options/bridge_mode/. > Other bridges/PT types are not supported. Maybe we need a FAQ entry > about "Is $PT supported in Tails?" that simply points to the > corresponding doc. > This is exactly what I wanted to say. There are many users that want to test the last transports, they always want to have the new Barbie or they are interested on testing more private things on Tails. We should spend some time writing documentation like the one we have about VPN and Tor and similar ones, even if it is just linking to the Tor documentation pages. From the frontdesk POV, it would be great to have access to reasoning regarding this problems with an official tone, even if its to say 'we are never going to do that, is crazy!', that's why I hijacked this thread and asked about proxychains and obfs3 bridges. cheers 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.
Re: [Tails-dev] using meek with Tails
X-RESEND: On Tue, 11 Nov 2014 16:31:14 +0100 intrigeri wrote: > Hi, > > Emma Peel wrote (11 Nov 2014 15:14:39 GMT) : > >> Still, the landscape of pluggable transports is quickly evolving, > >> and indeed we have a hard time staying on top of things in this > >> area. We already had #7909 (Support scramblesuit bridges, almost > >> done, and on my plate for 1.3) and #7980 (Support obfs4 bridges), > >> and I've just created #8243 (Support meek bridges). > >> > > And what about 'flash proxies'? > > Another user is asking for them, > > Yes, Flashproxy is yet another option, in case this landscape wasn't > confuging enough. No idea if it would work in the context of Tails, > and no idea if the package that's in testing/sid would work on Wheezy. > > > and saying that obsf3 bridges are not so available... is this true? > > What do you mean exactly with "not so available"? Many of them are offline, he claims. Another user is asking for 'proxychains' in Tails. Maybe we can have a nice page mapping the different fancy new transports and their tickets? I see many issues tracked from https://labs.riseup.net/code/issues/7980 but just the ones we are planning to add so far. Maybe we can add all this under https://tails.boum.org/support/faq/#networking ? Cheers 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.
Re: [Tails-dev] using meek with Tails
On Sat, 08 Nov 2014 10:12:50 +0100 intrigeri wrote: > > AFAIK, obfs3 bridges still work in China as well, and they do work > just fine in Tails. > > Still, the landscape of pluggable transports is quickly evolving, and > indeed we have a hard time staying on top of things in this area. > We already had #7909 (Support scramblesuit bridges, almost done, and > on my plate for 1.3) and #7980 (Support obfs4 bridges), and I've just > created #8243 (Support meek bridges). > And what about 'flash proxies'? Another user is asking for them, and saying that obsf3 bridges are not so available... is this true? > It's entirely unclear to me which ones we should prioritize. > Assuming we add support for Scramblesuit in Tails 1.3, then what > usecases won't we be supporting, that we could support better with > obfs4 or meek? > > Cheers, 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.
Re: [Tails-dev] Jessie!
On Tue, 16 Sep 2014 21:05:54 -0700 intrigeri wrote: > Hi, > > Emma Peel wrote (16 Sep 2014 15:49:02 GMT) : > > I could test, though my machine doesn't think she is old...(Thinkpad > > X60s). > > This would be a perfect machine to run this test on :) > > > Is this image available at > > http://nightly.tails.boum.org/build_Tails_ISO_feature-jessie/ ? > > Nope: the idea is to test GNOME Shell, and our Jessie images still use > GNOME Flashback. So you'll need to get a Debian Jessie or sid system > to boot on this machine, and try running GNOME Shell. Looks doable? > hmmm well i cannot see live images for Jessie... just for stable, here: https://www.debian.org/CD/live/ do you know if there is a place for jessie's lives? i guess there is also no link for a sid one: https://labs.riseup.net/code/issues/6350 ___ 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] Jessie!
On Sun, 14 Sep 2014 21:30:19 -0700 intrigeri wrote: > > Yay. So, only testing on slightly older hardware that we *might* want > to go on supporting when migrating to Jessie (e.g. ThinkPad X32, > ThinkPad X60) is missing. Once we have test results on such a machine, > I'll formally propose that we ship GNOME Shell with the Classic set > of extensions. > I could test, though my machine doesn't think she is old...(Thinkpad X60s). Is this image available at http://nightly.tails.boum.org/build_Tails_ISO_feature-jessie/ ? Cheers 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.
Re: [Tails-dev] calendar
On Thu, 11 Sep 2014 23:06:51 + BitingBird wrote: > > The calendar doesn't give the next low-hanging fruits sessions and > contributors meetings. Since we decided to have fixed dates, this > should maybe be written at the top or the bottom of the page ? > > https://tails.boum.org/contribute/calendar/ > > low-hanging fruits sessions every 12th of the month > contributors meetings every third day of the month on #tails-dev at > 9pm CEST or CET (7pm or 8pm UTC). > > Every Tails contributor is welcome to attend. > https://tails.boum.org/contribute/meetings/ > > Cheers, > Here a patch for https://tails.boum.org/contribute/calendar/ From 6bfceba9e1b8d9844bc48360ccd054396f28f74d Mon Sep 17 00:00:00 2001 From: Tails developers Date: Fri, 12 Sep 2014 08:53:51 + Subject: [PATCH] added contributors meetings and low hanging fruit sessions --- wiki/src/contribute/calendar.mdwn | 31 +-- 1 file changed, 21 insertions(+), 10 deletions(-) diff --git a/wiki/src/contribute/calendar.mdwn b/wiki/src/contribute/calendar.mdwn index a61b932..2128192 100644 --- a/wiki/src/contribute/calendar.mdwn +++ b/wiki/src/contribute/calendar.mdwn @@ -1,18 +1,29 @@ [[!meta title="Calendar"]] -* 2014-09-02: Release Tails 1.1.1. intrigeri does the first ~half of - the RM duty, anonym takes over around 2014-08-20. +* 2014-10-14: Release *Tails 1.2*. anonym is RM. -* 2014-09-03, 7pm UTC (9pm CEST): Tails contributors meeting - (`#tails-meeting` on `irc.indymedia.org` / `h7gf2ha3hefoj5ls.onion`) +* 2014-11-25: Release *Tails 1.2.1*. anonym is RM. -* 2014-10-14: Release Tails 1.2. anonym is RM. - -* 2014-11-25: Release 1.2.1. anonym is RM. - -* 2015-01-06: Release 1.2.2. anonym is RM. If Mozilla decides to send +* 2015-01-06: Release *1.2.2*. anonym is RM. If Mozilla decides to send their employees on vacation, delaying the Firefox ESR release for a week or two, anonym can still be RM. -* 2015-02-17: Release 1.3. Still undecided who will be RM, but anonym +* 2015-02-17: Release *1.3*. Still undecided who will be RM, but anonym probably can do it. + + +Monthly: + + + * Low Hanging Fruit sessions are held every 12th of the month + * [[Contributors meetings|contribute/meetings]] every third day of the month + +on #tails-dev at 9pm CEST or CET (7pm or 8pm UTC). + +Every Tails contributor is welcome to attend. + +As OFTC is blocking Tor lately, we temporarily gather in `#tails-dev` +on `irc.indymedia.org` instead of `irc.oftc.net`. + + + -- 1.7.10.4 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] Next Low hanging fruit session tomorrow!
Ey there! Tomorrow at 19 UTC we have our monthly Low Hanging Fruit session. Friday, September 12, on #tails-dev (indymedia.org/h7gf2ha3hefoj5ls.onion) at 19:00 UTC (21:00 CEST) The idea is to spend a while together on many small tasks that take less than 2 hours each. Not only these sessions are very useful to make Tails better, but we were happy to see new people join these parties recently. We hope to see even more of that in the future: these sessions are great times to start contributing to Tails! For newcomers, the list of "easy" tickets should be a great place to start: https://tails.boum.org/contribute/easy_tasks/ See you there tomorrow! ps: No kittens have been wrongfully used to make a point on this announcement. Oh, wait... ___ 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] patch submission feature #7512
El Sat, 02 Aug 2014 13:25:30 +0200 intrigeri escribió: > Hi, > > [No need to Cc me, I do read the list. Thanks!] > > emma peel wrote (02 Aug 2014 10:34:11 GMT) : > > I will dive on git and come back with a cleaner patch based in > > devel > > Note that Kill Your TV already submitted an updated patch on the list: > Message-Id: <20140801135706.B5F97AE1D2@smtp.postman.i2p> > I've not looked at it yet. > ok i think it is a wonderful patch! thanks kill your TV! ___ 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] patch submission feature #7512
El Fri, 01 Aug 2014 14:50:03 +0200 intrigeri escribió: > Hi, > > intrigeri wrote (14 Jul 2014 10:38:47 GMT) : > > Also, I would find it good to be even closer to duraconf's gpg.conf: > > e.g. > > > * we could plausibly take the "algorithm and ciphers" section as-is > > * the no-honor-keyserver-url keyserver-options could be split out > > > Ideally, a diff of our gpg.conf and duraconf's would only show a few > > added/changed lines, for easier auditing and maintenance. What do > > you think? > > Ping? (If you don't intend to work on this branch any further, no > problem, just tell us :) ok reading riseup's document on best practices i was covinced about the no-honor-keyserver-url option to be set. https://help.riseup.net/en/security/message-security/openpgp/best-practices#ensure-that-all-keys-are-refreshed-through-the-keyserver-you-have-selected ¨This is useful because (1) it prevents someone from designating an insecure method for pulling their key and (2) if the server designated uses hkps, the refresh will fail because the ca-cert will not match, so the keys will never be refreshed. Note also that an attacker could designate a keyserver that they control to monitor when or from where you refresh their key.¨ and i dont really know enough about cyphers to have an opinion on the cyphers. but yea, now that you mention it, i realise that regarding releases and changes it is better to stick more to duraconf, or in any case try to convince the riseup people I will dive on git and come back with a cleaner patch based in devel cheers > > Cheers, ___ 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] patch submission feature #7512
intrigeri wrote: > Hi, > > intrigeri wrote (14 Jul 2014 10:38:47 GMT) : >> Also, I would find it good to be even closer to duraconf's gpg.conf: >> e.g. > >> * we could plausibly take the "algorithm and ciphers" section as-is >> * the no-honor-keyserver-url keyserver-options could be split out > >> Ideally, a diff of our gpg.conf and duraconf's would only show a few >> added/changed lines, for easier auditing and maintenance. What do >> you think? > > Ping? (If you don't intend to work on this branch any further, no > problem, just tell us :) > sorry i had some issues with the git and then the release came so i thought i had some time... i will go back to you on this stuff > Cheers, > ___ 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] patch submission feature #7512
Hello devs: I know I said I wanted to help on translating, but I could not help to make a little patch (you know, girls...) I did a new branch and commited to it a .gnupg/gpg.conf that is working on my stable tails, with the name of the feature #7512 reported by intrigeri: https://git-tails.immerda.ch/emmapeel/tails/commit/?h=feature/7512-Make-GnuPG-config-closer-to-duraconf this is my first patch so BEWARE OF SLOPPY STUFF ps: already linked by DrWhax on https://labs.riseup.net/code/issues/7512 binzCaarS77dM.bin Description: application/pgp-encrypted binn6xp9do7F6.bin Description: Binary data 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.
