Commit 26606f62 authored by sajolida's avatar sajolida
Browse files

Merge remote-tracking branch 'origin/master' into doc/15660-usb-images

parents cf316d15 79377246
......@@ -43,6 +43,7 @@ add_plugins:
- pagetemplate
- passwordauth
- po
- prettydate
- shortcut
- sidebar
- tag
......@@ -421,3 +422,6 @@ tag_autocreate_commit: 1
# extra underlay directories to add
add_underlays:
- /home/amnesia/Persistent/Tails/promotion-material
# prettydate plugin
prettydateformat: '%Y-%m-%d'
......@@ -40,6 +40,7 @@ add_plugins:
- mirrorlist
- pagetemplate
- po
- prettydate
- shortcut
- sidebar
- tag
......@@ -398,3 +399,6 @@ tag_autocreate_commit: 1
# extra underlay directories to add
add_underlays:
- /home/amnesia/Persistent/Tails/promotion-material
# prettydate plugin
prettydateformat: '%Y-%m-%d'
[[!meta title="Tails September 2018 report"]]
[[!toc levels=2]]
This report covers the activity of Tails in September 2018.
Everything in this report is public.
# A. VeraCrypt support in GNOME
## A.3 Write automated tests
## A.5 Add VeraCrypt support to GNOME Disks
## A.6 Add VeraCrypt support to GNOME Files
## A.9 Fix bugs and UX issues
## A.10 Port to the latest version of GNOME
# B. Additional software
## B.2 Write technical design documentation
## B.3 Write automated tests
We wrote a number of automated tests to ensure we notice important
regressions in the _VeraCrypt_ support introduced in Tails 3.9.
We have specified the [high-level behavior in
Gherkin](https://gitlab.com/Tails/tails/blob/test/14471-veracrypt/features/veracrypt.feature)
then implemented the corresponding steps. All this work is now pending
our internal code review and should be merged by the end of October
([[!tails_ticket 14471]], [[!tails_ticket 14469]], [[!tails_ticket
15238]], [[!tails_ticket 15239]]).
## B.8 Fix bugs and UX issues
- We have investigated and fixed a regression introduced in Tails 3.9:
the _Persistence Configuration_ was displayed full screen in some
specific screen resolutions, which made the software harder to use.
([[!tails_ticket 15894]])
# C. Deliver new features
## C.1 Major release including objective A
## C.2 Major release including objective B
## C.4 Server hardware
<div class="caution">
Some of this blueprint is obsolete.
</div>
[[!toc levels=2]]
# Rationale
......
......@@ -241,6 +241,8 @@ Structured explanation
- <https://icloak.me/>
- <https://www.apple.com/apple-watch-series-3/>
- <https://www.tunnelbear.com/>
- <https://duckduckgo.com/> <https://duckduckgo.com/about>
- <https://mullvad.net/>
Post-summit
-----------
......
Documentació per a la traducció del Tails al Català
===================================================
[[!toc levels=2]]
Com puc ajudar a traduir el Tails al català?
--------------------------------------------------
1. Si voleu ajudar a traduir el Tails, el primer que hauríeu de fer és subscriure-us a la llista de correu dels traductors al Català del Tails:
- <https://mailman.boum.org/listinfo/tails-l10n-ca>
- Presenteu-vos a la llista i us posarem al dia de l'estat de la traducció.
2. En segon lloc us hauríeu de familiaritzar amb els [recursos per a traductors de Softcatalà](https://www.softcatala.org/recursos/), especialment:
- [La Guia d'estil de softcatalá](https://www.softcatala.org/guia-estil-de-softcatala)
A partir d'aquí podreu triar entre traduir el programari especialitzat del Tails o el seu web, que són els dos recursos bàsics que hi ha per traudir.
* El Tails és un Debian especialment configurat. La major part del seu programari, doncs, forma part d'aquesta distribució de Linux i la seva traducció no la gestiona la comunitat del Tails, sinó la de Debian. En canvi, però, sí que podem traduir el programari específic del Tails. Per això fem servir la plataforma Transifex i trobareu més instruccions a [[*Translate Tails using Transifex*|contribute/how/translate/with_Transifex]].
* Per a la traducció del contingut del web (per ara, la nostra prioritat) es poden usar dues eines diferents:
* git
* plataforma weblate
Traducció del web oficial de Tails amb git
------------------------------------------
Per a traduir el web amb git heu de seguir les instruccions a [[*Translate Tails and its website using Git*|contribute/how/translate/with_Git]], tenint en compte que en el punt *1. Set up your own repository*, que indica que us creeu el vostre repositori, ja tenim creat un repositori per als traductors de Català, que el trobareu a <https://gitlab.com/tails-ca/tails>, i que hauríeu de fer servir.
En aquest repositori hi trobareu una branca *master* que conté el codi oficial de git. La branca *catalan* conté el codi amb la traducció al català. Hi ha altres branques *translate/xxxx* per a cada secció del web de Tails que estem traduïnt i que després incorporem a la branca *catalan*. Quan tinguem un mínim de traducció llesta podrem demanar que l'activin. Aquestes son les pàgines que hem de traduir en primer lloc: [[arxius del nucli a traduir|contribute/l10n_tricks/core_po_files.txt]]
Mitjançant la llista de correu ens coordinem per repartir-nos la traducció d'aquestes pàgines.
Traducció del web oficial de Tails amb Weblate
----------------------------------------------
Si ho preferiu, podeu traduir el web del Tails mitjançant una plataforma web que s'està provat:
<https://translate.tails.boum.org/>
L'equip de traducció al Català encara no l'hem utilitzat i no hem establert, per tant, una operativa per a traduir amb Weblate. Però si la voleu fer servir, parlem-ne a la llista de correu i ens coordinem.
Consells de traducció
---------------------
A part de seguir les guies de traducció de softcatalà, cal tenir en compte que el web de Tails funciona amb [[ikiwiki]] i que aquest inclou un sistema de marcatge que cal traduir convenientment. Cal revisar com funcionen el [[enllaços wiki|ikiwiki/wikilink]] i les [[directives|ikiwiki/directive]], especialment els *!inline*.
### Enllaç ikiwiki: [ [ paraula ] ]
Els enllaços d'ikiwiki es corresponen a rutes d'URL. Per exemple:
[ [ Security ] ]
enllaça a la pàgina [[Security]].
Si volem traduir el text de l'enllaç, haurem de traduir l'enllaç ikiwiki de la següent manera:
[ [ Seguretat|Security ] ]
per tenir l'enllaç a [[Seguretat|Security]] traduït.
La primera part abans del **|** es el text de l'enllaç, i la segona és l'enllaç en si mateix, en forma de ruta URL, que no canvia respecte l'original. Si l'enllaç corresponent en català existeix, l'ikiwiki ens hi portarà. Sinó, enllaça amb la versió en anglès.
(Per cert, en aquests exemples hi ha espais entre [ [ i ] ] i dins mateix, entre el text i els [ i ]. En la traducció s'ha de fer **sense espais**. Aquí hi són perquè sinó l'ikiwiki no mostra el codi com a exemple correctament.)
### Directiva *!inline*: [ [ !inline pages="xxxxxxx" raw="yes" sort="age" ] ]
Ens podem trobar amb aquesta directiva d'ikiwiki en alguns textos. És una forma d'incloure contingut des d'un altre arxiu. Dels *!inline* hem de traduir-ne la ruta a l'arxiu. Per exemple, aquesta directiva *!inline*:
[ [ !inline pages="support/talk/languages.inline" raw="yes" sort="age" ] ]
L'hauríeu de traduir així:
[ [!inline pages="support/talk/languages.inline.ca" raw="yes" sort="age"] ]
És a dir, afegir un *.ca* al final del nom de l'arxiu que s'incrustarà. Us heu d'assegurar que traduïu també l'arxiu corresponent, que hauríeu de trobar al sistema de fitxers, en aquest cas a *wiki/src/support/talk/*.
......@@ -45,6 +45,6 @@ designate themselves beforehand.
| July 2018 | sajolida | u |
| August 2018 | sajolida | segfault |
| September 2018 | muri | intrigeri |
| October 2018 | | |
| October 2018 | muri | |
| November 2018 | intrigeri | |
| December 2018 | | |
......@@ -91,6 +91,7 @@ Template
\[[!meta title="Tails report for MONTH, YEAR"]]
\[[!meta date="`date --rfc-2822` eg. Thu, 08 Feb 2018 07:21:15 +0000"]]
\[[!pagetemplate template="news.tmpl"]]
\[[!toc]]
......
[[!meta title="Tails report for September, 2018"]]
[[!meta date="Tue, 10 Apr 2018 01:23:45 +0000"]] XXX: adjust date
[[!pagetemplate template="news.tmpl"]]
[[!toc]]
......@@ -27,6 +28,19 @@ XXX: If you feel like it and developers don't do it themselves,
Release section (for example, the changes being worked on for
the next version).
- We successfully collaborated with the _Tor Browser_ team to fix
a severe issue with _Tor Browser_ 8.0 in Tails, that was discovered
shortly before the Tails 3.9 release. Thanks a lot for everyone
who helped!
- We fixed a number of regressions that were introduced in Tails 3.9, such as:
- Fix the update of *Additional Software*. ([[!tails_ticket 15978]])
- Fix opening VeraCrypt file containers using the **Open With Unlock VeraCrypt
Volumes** of *GNOME Files*. ([[!tails_ticket 15954]])
- Fix the display of the **General** tab in the preferences of *Tor Browser*.
([[!tails_ticket 15917]])
- Fix displaying the help of *GNOME Videos*. ([[!tails_ticket 15841]])
Documentation and website
=========================
......@@ -65,9 +79,39 @@ XXX: Report only if more scenarios have been written and add the diff from the p
- Our test suite covers SCENARIOS scenarios, DIFF more that in May.
- We started planning the migration of our Redmine to [[!tails_ticket
15918 desc="a different hostname"]] and [[!tails_ticket 15919
desc="a new VM"]].
- We wrote a number of automated tests to ensure we notice important
regressions in the _VeraCrypt_ support introduced in Tails 3.9.
- We completed our [[!tails_ticket 14585 desc="investigation"]] of
Dogtail's long-term viability. Our conclusion is that we can keep
using it, should start contributing to the maintenance of the
package in Debian, but invest as little as possible into Dogtail
for now as our long-term concerns are not fully addressed.
- We investigated what prevented us from giving more Tails developers
access to our Jenkins CI platform so far. We've identified
a [[!tails_ticket 11344 desc="few"]] [[!tails_ticket 15981
desc="blockers"]], resolved them, and started giving such access
more liberally, which should make Tails development work more
pleasurable and efficient for a few more people.
- The Tails sysadmin team discussed hiring a new team member, the
profile of the person we will be looking for, and how we could share
our work with them.
- We made great progress towards [[!tails_ticket 14588 desc="hosting
our website on our own infrastructure"]]. The final steps and migration
should happen by the end of the year.
Funding
=======
- We published our [[finances for 2017|doc/about/finances#2017]].
XXX: The fundraising team should look at the fundraising Git.
git log --patch --since='1 December' --until='1 January' origin/master
......@@ -80,6 +124,8 @@ Outreach
Past events
-----------
- A few of us attended the Tor meeting in Mexico City.
Upcoming events
---------------
......
[[!meta title="Tails report for October, 2018"]]
[[!meta date="Tue, 10 Apr 2018 01:23:45 +0000"]] XXX: adjust date
[[!pagetemplate template="news.tmpl"]]
[[!toc]]
......
[[!meta title="Tails report for November, 2018"]]
[[!meta date="Tue, 10 Apr 2018 01:23:45 +0000"]] XXX: adjust date
[[!pagetemplate template="news.tmpl"]]
[[!toc]]
......
[[!meta title="Tails report for December, 2018"]]
[[!meta date="Tue, 10 Apr 2018 01:23:45 +0000"]] XXX: adjust date
[[!pagetemplate template="news.tmpl"]]
[[!toc]]
......
......@@ -15,9 +15,9 @@ Modules not included in standard library follow:
Was migrated to Python3 as part of WhisperBack (see below).
## config/chroot_local-includes/usr/local/bin/lc.py
## ~~config/chroot_local-includes/usr/local/bin/lc.py~~
Should be migrated to Python3: [[!tails_ticket 10088]]
Was migrated to Python3 as part of [[https://labs.riseup.net/code/projects/tails/repository/revisions/2b2b6c76d10db733905fad978340150da3c920a4]] ([[!tails_ticket 10088]])
## ~~config/chroot_local-includes/usr/local/bin/shutdown_helper_applet~~
......@@ -26,9 +26,9 @@ We will not use this applet in Tails/Jessie, so there is nothing to do.
- `gtk`: deprecated, replaced by `python3-gi` and `gir1.2-gtk-3.0`
- `gnomeapplet`: deprecated, replaced by `python3-gi` and `gir1.2-panelapplet-4.0`
## config/chroot_local-includes/usr/local/bin/tails-about
## ~~config/chroot_local-includes/usr/local/bin/tails-about~~
Should be migrated to Python3: [[!tails_ticket 10083]]
Was migrated to Python3 in Tails 2.6: [[!tails_ticket 10082]]
- `gtk`: deprecated, replaced by `python3-gi` and `gir1.2-gtk-3.0`
......@@ -36,21 +36,21 @@ Should be migrated to Python3: [[!tails_ticket 10083]]
Ported to Python3.
## config/chroot_local-includes/usr/local/lib/boot-profile
## ~~config/chroot_local-includes/usr/local/lib/boot-profile~~
Should be migrated to Python3: [[!tails_ticket 10084]]
Was migrated to Python3 in Tails 2.6: [[!tails_ticket 10083]]
* `pyinotify`: OK, `python3-pyinotify`
## config/chroot_local-includes/usr/local/sbin/tails-additional-software
## ~~config/chroot_local-includes/usr/local/sbin/tails-additional-software~~
Should be migrated to Python3: [[!tails_ticket 15067]]
Was migrated to Python3 as part of [[!tails_ticket 15198]] in [[https://labs.riseup.net/code/projects/tails/repository/revisions/2abe4abbf69f5c6cde80de6bcc3134734860ca13]]: [[!tails_ticket 15067]]
* `posix1e`: OK, `python3-pylibacl`
# Tails Greeter
# ~~Tails Greeter~~
Should be migrated to Python3: [[!tails_ticket 5701]]
Was migrated to Python3 in Tails 3.0: [[!tails_ticket 5701]]
* `pycountry`: OK, `python3-pycountry`
* `icu`: OK, `python3-icu`
......
......@@ -332,6 +332,22 @@ After a new Tails release is out
### If you just put out a final release
If the release was a major one, then:
1. [[Hard reset the `stable` APT suite to
the state of the `testing` one|APT_repository/custom#workflow-reset]].
2. Empty `config/APT_overlays.d` in the `stable` branch:
git checkout stable && \
if [ $(find config/APT_overlays.d -maxdepth 1 -type f | wc -l) -gt 1 ]; then
git rm config/APT_overlays.d/* && \
git commit config/APT_overlays.d/ \
-m "Empty the list of APT overlays: they were merged"
fi
In any case:
* [[merge `stable` or `testing` into
`devel`|APT_repository/custom#workflow-merge-main-branch]]
* increment the version number in `devel`'s `debian/changelog` to match
......@@ -358,18 +374,6 @@ After a new Tails release is out
git commit debian/changelog \
-m "Add dummy changelog entry for ${NEXT_PLANNED_MINOR_VERSION:?}."
If the release was a major one, then:
1. [[Hard reset the stable APT suite to
the state of the testing one|APT_repository/custom#workflow-reset]].
2. Empty `config/APT_overlays.d` in the `stable` branch:
git checkout stable && \
git rm config/APT_overlays.d/* && \
git commit config/APT_overlays.d/ \
-m "Empty the list of APT overlays: they were merged"
### Else, if you just released a RC
* increment the version number in `debian/changelog` on the branch
......
......@@ -105,7 +105,7 @@ a specific set of APT repository snapshots must be used:
git checkout devel && \
./auto/scripts/apt-snapshots-serials thaw && \
git commit \
-m "Thaw APT snapshots after Tails $VERSION was released." \
-m "Thaw APT snapshots." \
config/APT_snapshots.d/*/serial
<a id="bump-expiration-date"></a>
......@@ -160,11 +160,11 @@ e.g. after we release Tails based on a new Debian, we need to stop
including it in new snapshots, and to remove all corresponding
time-based snapshots and the packages that are not referenced anymore.
1. In puppet-tails, remove the bits about the distribution you want to
1. In `puppet-tails`, remove the bits about the distribution you want to
stop tracking from the reprepro configuration templates:
`templates/reprepro/snapshots/time_based/*/*`.
2. In puppet-tails, remove references to the distribution you want to
2. In `puppet-tails`, remove references to the distribution you want to
stop tracking from the `tails::reprepro::params` class.
3. Commit, push and deploy on the system that hosts our time-based
......@@ -276,18 +276,17 @@ having to deal with 80GB+ Berkeley DB databases.
## Garbage collection and Valid-Until
We expire snapshots older than 10 days in order to save disk space,
and to avoid the reprepro database to grow too much.
and to prevent the reprepro database from growing too much.
To ensure that garbage collection doesn't delete a snapshot we still
need, e.g. the one currently referenced in the frozen `testing`
branch, we rely on the `Valid-Until` field found in `Release` files:
the way to express "I want to keep a given snapshot around" is to
the way to express "I want to keep this specific snapshot around" is to
postpone its expiration date; i.e. we don't differentiate "keep
a given snapshot around" from "keep a given snapshot usable", which
seems to make sense.
a given snapshot around" from "keep a given snapshot usable".
See [[above|time-based_snapshots#bump-expiration-date]] for how we
can manage `Valid-Until` manually, whenever needed.
manage `Valid-Until` manually.
One advantage of this design is that we don't have to regularly update
`Valid-Until` fields, and the corresponding signatures: we only do
......@@ -300,12 +299,11 @@ In practice, the main use case for keeping a given time-based APT
repository snapshot around and valid is when it's being used by
a release branch:
- `testing`: while it's frozen, that is during 5-10 days most of the
time;
- `testing`: while it's frozen, that is for 5-10 days generally;
- `stable`: that's a corner case, since `stable` generally uses the
set of tagged snapshots of the latest Tails release; if and when we
set of snapshots frozen during the last Tails freeze; if and when we
decide to manually point `stable` to a different set of snapshots,
then we can as well deal with `Valid-Until` manually.
then we bump `Valid-Until` manually.
In passing, note that we ship an empty `/var/cache/apt/lists/` in the
ISO ⇒ modifying `Release` and `Release.gpg` files on our APT
......
......@@ -4,18 +4,21 @@ All times are referenced to Berlin and Paris time.
## 2018Q3
* 2018-09-04: Build and upload tentative 3.9 ISO image — intrigeri
## 2018Q4
* 2018-09-05: Test and **release 3.9** (Firefox 60.2, major release) — intrigeri is the RM
- includes VeraCrypt support + major Additional Software Packages improvements
* 2018-10-02: Build and upload tentative 3.9.1 ISO image — anonym
## 2018Q4
* 2018-10-03: Test 3.9.1
* 2018-10-03, 19:00: [[Contributors meeting|contribute/meetings]]
* 2018-10-05: **release 3.9.1** (Firefox 60.2.1, bugfix release) — anonym is the RM
* 2018-10-15: 14:00: Additional Software meeting (wrap up)
* 2018-10-23: **Release 3.10** (Firefox 60.3, bugfix release)
* 2018-10-22: Build and upload tentative 3.10 ISO image — kibi
* 2018-10-23: Test and **release 3.10** (Firefox 60.3, bugfix release) — kibi is the RM
* 2018-11-06, 19:00: [[Contributors meeting|contribute/meetings]]
......
[[!meta title="Additional software packages design documentation"]]
[[!meta title="Additional software packages"]]
[[!toc levels=2]]
......@@ -78,8 +78,9 @@ empty. It is a oneshot service that executes
`tails-additional-software install` reads `live-additional-software.conf` which
contains a package name per line and install these packages with `apt-get`
(using `DEBIAN_PRIORITY=critical` and the command line options `--yes` and
`--option DPkg::Options::=--force-confold`).
(using options prevent questions being asked to the user, see
`install_additional_packages` and `_launch_apt_get` in
[[!tails_gitweb config/chroot_local-includes/usr/local/sbin/tails-additional-software]]).
In the beginning of the process, the user is notified through desktop
notifications that additional software is being installed:
......@@ -107,7 +108,7 @@ if the configuration file
`/live/persistence/TailsData_unlocked/live-additional-software.conf` is not
empty.
[[!tails_gitweb config/chroot_local-includes/usr/local/sbin.tails-additional-software]]
[[!tails_gitweb config/chroot_local-includes/usr/local/sbin/tails-additional-software]]
`update` saves a copy of apt lists, then starts `apt-get update` and launches the
installation process again, triggering an upgrade if necessary.
......@@ -164,7 +165,7 @@ When *Add To Persistent Storage* is clicked,
`AdditionalSoftware` preset. The new additional packages are then added
atomically to the `live-additional-software.conf` configuration file
(this logic is handled by
[[!tails_gitweb submodules/pythonlib/tailslib/additionalsoftware/config.py]])
<https://git-tails.immerda.ch/pythonlib/plain/tailslib/additionalsoftware/config.py>)
#### Without persistent storage
......@@ -178,7 +179,7 @@ automatically enabled. The new additional packages are then added to the
`live-additional-software.conf` configuration file, which is in this
case mounted to `/media/tails-persistence-setup/TailsData` instead of
`/live/persistence/TailsData_unlocked` (this logic in handled by
[[!tails_gitweb submodules/pythonlib/tailslib/persistence.py]]).
<https://git-tails.immerda.ch/pythonlib/plain/tailslib/persistence.py>).
The systemd service
[[!tails_gitweb config/chroot_local-includes/lib/systemd/system/tails-synchronize-data-to-new-persistent-volume-on-shutdown.service]]
......@@ -214,7 +215,7 @@ too much.
When *Remove* is clicked, the packages are removed atomically from the
`live-additional-software.conf` configuration file (this logic is
handled by
[[!tails_gitweb submodules/pythonlib/tailslib/additionalsoftware/config.py]]).
<https://git-tails.immerda.ch/pythonlib/plain/tailslib/additionalsoftware/config.py>).
Additional Software configuration window
----------------------------------------
......@@ -255,7 +256,7 @@ When clicking on the delete cross, a confirmation dialog is displayed:
<img src="https://git.tails.boum.org/ux/plain/additional software/png/additional software - remove.png"/>
The privileged helper
[[!tails_gitweb config/chroot_config/chroot_local-includes/usr/local/sbin/tails-additional-software-remove]]
[[!tails_gitweb config/chroot_local-includes/usr/local/sbin/tails-additional-software-remove]]
is called through *pkexec* to remove the software from the
`live-additional-software.conf` configuration file (see
[[!tails_gitweb config/chroot_config/chroot_local-includes/usr/share/polkit-1/actions/org.boum.tails.additional-software.policy]]
[[!tails_gitweb config/chroot_local-includes/usr/share/polkit-1/actions/org.boum.tails.additional-software.policy]]
......@@ -336,34 +336,7 @@ Additional software packages
The `tails-additional-software` script installs a list of
additional software packages stored in persistence.
To this aim, the persistent volume root directory may contain
a `live-additional-software.conf` file that holds the list of packages to install
(from persistence, since they were cached already).
`live-persist` guarantees that this file, and its parent directory,
have correct access rights: owned by
`tails-persistence-setup:tails-persistence-setup`, and not be writable
by anyone else than the `tails-persistence-setup` user.
First, those additional software packages are installed offline by a systemd
user unit triggered by desktop.target. It starts a system unit of the same
name, which itself calls Additional Software Packages installation.
Then, once connected to the network, a NetworkManager dispatcher hook triggers
a systemd system unit which looks for upgrades if additional software were
activated (`apt update`, then `apt install` the additional software packages).
For some packages (e.g. already running software) the change will only be
effective at next boot but hopefully a outdated version won't be used too long
in the meantime. To ensure that the upgrade started by a NetworkManager hook is
not racy with the installation, systemd unit is ordered after the installation,
and waits for its state file to appear.
- [[!tails_gitweb config/chroot_local-includes/usr/lib/systemd/user/tails-additional-software-install.service]]
- [[!tails_gitweb config/chroot_local-includes/lib/systemd/system/tails-additional-software-install.service]]
- [[!tails_gitweb config/chroot_local-includes/lib/systemd/system/tails-additional-software-upgrade.service]]
- [[!tails_gitweb config/chroot_local-includes/etc/NetworkManager/dispatcher.d/70-upgrade-additional-software.sh]]
- [[!tails_gitweb config/chroot_local-includes/usr/local/sbin/tails-additional-software]]
For details see [[additional_software_packages]].
<a id="security"></a>
......
......@@ -80,7 +80,7 @@ Anyone can check it out like this:
Developers with write access to the repositories should instead:
git clone boum_org_amnesia@webmasters.boum.org:wiki.git
torsocks git clone gitolite@d53ykjpeekuikgoq.onion:tails
And then, in any case, in your new Git clone's directory:
......@@ -191,7 +191,7 @@ Anyone can check it out like this:
Developers with write access to the repositories should instead:
git clone boum_org_amnesia@webmasters.boum.org:promotion-material.git
torsocks git clone gitolite@d53ykjpeekuikgoq.onion:promotion-material
We have a [web interface](https://git-tails.immerda.ch/promotion-material/)
available for the promotion material repository.
......@@ -370,12 +370,5 @@ Troubleshooting
First, check with your team-mates: in some cases they can help you
troubleshoot your problem, and confirm whether the problem is on your
side or on the server side. If that is not enough, read on.
* For repositories hosted at `git-tails.immerda.ch` (aka.
`git.tails.boum.org`) or at `git.puppet.tails.boum.org`: get in
touch with
[[Tails system administrators|about/contact#tails-sysadmins]].
* For repositories hosted at `webmasters.boum.org`: get in touch with
<root@boum.org>.
side or on the server side. If that is not enough, get in touch with
the [[Tails system administrators|about/contact#tails-sysadmins]].
[[!meta date="Tue, $DAY $MON $YEAR 12:34:56 +0000"]]
[[!meta title="Tails $VERSION is out"]]
[[!pagetemplate template="news.tmpl"]]
[[!tag announce]]
This release fixes [[many security
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment