Commit 533c1b1b authored by sajolida's avatar sajolida
Browse files

Rename 'Tails Greeter' to 'Welcome Screen' in order to be more plain (#15122)

parent 6faaafe3
......@@ -167,7 +167,7 @@ using the usual communication channels.
- *OpenPGP Applet* (Perl): nodens
- Persistence setup (Perl): intrigeri, kurono
- Sysadmin: [[contact|contribute/how/sysadmin/#contact]]
- *Tails Greeter* (Python): alan, intrigeri
- Welcome Screen (Python): alan, intrigeri
- *Tails Installer* (Python): alan, kurono, u
- *Tails Upgrader* (Perl): intrigeri
- *Tails Verification* (JavaScript): sajolida, anonym
......
......@@ -1005,7 +1005,7 @@ We only modify this Tor Browser installation slightly:
We add a mandatory signing exception for this add-on.
* We use the myspell/hunspell dictionaries provided by Debian.
* We ship all langpacks and select the UI language depending on
the locale chosen by the user in our *Greeter*.
the locale chosen by the user in our Welcome Screen.
* Tails does not install the Tor Launcher extension as part of the
browser. Instead we extract Tor Launcher from the bundled .xpi and
make it available as a stand-alone XUL application for Tor
......
......@@ -350,7 +350,7 @@ The current implementation leaves the OUI part unchanged, and only spoofs the
last three bytes of any network device's MAC address immediately after
it is added by udev. Furthermore, to deal with potential network leaks
before the user has chosen whether to enable MAC spoofing or not, the
addition of network devices is delayed until after Tails Greeter knows
addition of network devices is delayed until after the Welcome Screen knows
the user's final decision.
## Network blocking
......@@ -361,7 +361,7 @@ whether to enable MAC spoofing or not. The way we do this is by
generating a list of all network device modules during build time, and
add these to a `modprobe.d`-type blacklist. An implication of this is
that in-kernel drivers and modules installed after build time will not
be in the blacklist and hence are not supported. In Tails Greeter's
be in the blacklist and hence are not supported. In the Welcome Screen's
post-login script (when we know the user's decision) we unblock the
network by simply removing that list, and then we have udev "re-probe"
for network devices and load their modules.
......@@ -461,7 +461,7 @@ that some devices are pretty much only used in some geographical
areas. Note that collecting such data probably is orders of magnitude
harder than `macchiato`'s current quest, and that the user interface
would be further complicated (in Tails we'd have to ask for the
current geographical location in Tails Greeter, or similar). The real
current geographical location in the Welcome Screen, or similar). The real
impact of this should be evaluated; it's very likely that the benefits
still outweigh this risk.
......
......@@ -33,7 +33,7 @@ The following is the complete list of the applications allowed to use
the clearnet DNS configuration:
* the `tor` process itself, but only if the user requested to
configure Tor's network settings in Tails Greeter; in this case
configure Tor's network settings in the Welcome Screen; in this case
`tor` being able to resolve hostnames is convenient (e.g. hostnames
are human-readable, IP addresses not as much) or even necessary
(e.g. for the Meek pluggable transport):
......
......@@ -29,12 +29,12 @@ these options before Tor tries to connect to the public Tor network.
# Implementation
In Tails Greeter the "Network Configuration" section contains a
In the Welcome Screen the "Network Configuration" section contains a
non-default option called "My Internet Connection is
censored...". When activated, the following deviations from normal
Tails behaviour occur, in order:
0. Tails Greeter adds `DisableNetwork 1` to torrc so Tor will not
0. The Welcome Screen adds `DisableNetwork 1` to torrc so Tor will not
connect to the network without user intervention.
0. The `tor` process is configured to not use the system resolver
......
......@@ -223,7 +223,7 @@ detecting an encrypted Debian Live persistent volume). This is why we
have decided, back when we were implementing persistence support and
a graphical USB installer in 2012, to initialize Tails boot devices
with a GPT. Since then, we have made great use of this feature in
Tails Persistent Volume Assistant, Incremental Upgrader and Greeter.
Tails Persistent Volume Assistant, Incremental Upgrader and the Welcome Screen.
Despite a few painful consequences we discovered along the way, all
caused by buggy firmware implementations, we think that picking GPT at
......
......@@ -255,7 +255,7 @@ Persistence settings changes are taken into account at next boot.
Choosing between various persistence modes is one of the reasons why
we've written a graphical [[!tails_ticket 5528 desc="boot menu"]]:
[[!tails_ticket 5496 desc="TailsGreeter"]].
the [[!tails_ticket 5496 desc="Welcome Screen"]] (aka. *tails-greeter*).
#### Design
......
......@@ -5,7 +5,7 @@
<div class="note">
This is about the main Tails Git repository. Other repositories, such
as the ones for the Greeter and other custom software, are not affected.
as the ones for the Welcome Screen (aka *tails-greeter*) and other custom software, are not affected.
</div>
......
......@@ -34,7 +34,7 @@ The words
- the beginning of the said phase.
* **Help desk** (formerly: **Front desk**): see the
[[definition of this shifting role|contribute/working_together/roles/help_desk/]]
* **Greeter**: the startup menu
* **Welcome Screen**: the startup menu, aka *tails-greeter*
* **IUK**: Incremental Upgrade Kit, see
[[contribute/design/incremental_upgrades]]
* **known issues**: issues that we are aware of and don't need being
......
......@@ -60,8 +60,8 @@ Use the equivalent of DocBook tags
to style your documentation using CSS.
- <span class="code">span.application</span> for application names, for example:
- Code: `<span class="application">Tails Greeter</span>`
- Result: <span class="application">Tails Greeter</span>
- Code: `<span class="application">Welcome Screen</span>`
- Result: <span class="application">Welcome Screen</span>
- <span class="code">span.button</span> for button names, for example:
- Code: `the <span class="button">Login</span> button`
- Result: the <span class="button">Login</span> button
......
......@@ -294,11 +294,11 @@ the progressive or perfect tense.
coordinating conjunction (usually *and* or *or*) in a series of three
or more terms.
<a id="tails-greeter"></a>
<a id="welcome-screen"></a>
- **<span class="application">Tails Greeter</span>**
- **Welcome Screen**
Without an article. Not *the Greeter*. Note the formatting as an application.
With an article. Not *Tails Greeter* or *the Greeter*.
<a id="update"></a>
......
......@@ -45,7 +45,7 @@ Things he dislikes:
- His hardened X60 has a 32-bit processor and he won't be able to run
Tails 3.0 on it anymore.
- He finds it painful not to have the keyboard for his language listed
in the short list of keyboards in Tails Greeter.
in the short list of keyboards in the Welcome Screen.
- He had troubles trying to install additional packages in Tails and
instead reinstalled them every time. He wanted to use `scantailor`, a
post-processing tool for scanned pages, and `tesseract-ocr`, an
......
......@@ -100,7 +100,7 @@ My life is called "patience".
**T: Let's do some tests!**
The USB is Kingston. It takes 3:30 minutes to
get to *Tails Greeter*, 5 seconds to unlock the Persistence, 50 to open
get to the Welcome Screen, 5 seconds to unlock the Persistence, 50 to open
the desktop, 7 to connect to the Wi-Fi, 30 to connect to Tor, more than 1
minute to open *Tor Browser*. It seems like it's a problem with the
computer indeed.
......
......@@ -60,7 +60,7 @@ See also:
- Lines are issues.
- Columns are testers.
- See these examples rainbow tables from testing
[*Tails Greeter*](https://tails.boum.org/blueprint/greeter_revamp_UI/rainbow_-_greeter_-_20151105.ods)
the [Welcome Screen](https://tails.boum.org/blueprint/greeter_revamp_UI/rainbow_-_greeter_-_20151105.ods), aka "Tails Greeter"
and the [*Installation Assistant*](https://redmine.tails.boum.org/code/attachments/download/1245/ux-testing-20151120.ods)
- Compact information.
- Don't modify your design yet!
......
......@@ -573,7 +573,7 @@ SquashFS file order
1. Shut down this Tails.
1. Boot this USB stick **on bare metal** again.
1. Add `profile` to the kernel command-line.
1. Login with the default settings in the Greeter (e.g. do not configure
1. Login with the default settings in the Welcome Screen (e.g. do not configure
an _Administration Password_).
1. Wait for the "Tor is ready" notification.
1. Start *Tor Browser*.
......
......@@ -232,7 +232,7 @@ at the application level:
2. Start from that USB stick.
3. Set an administration password in the _Greeter_.
3. Set an administration password in the Welcome Screen.
4. Upgrade to the version we're testing:
......@@ -290,7 +290,7 @@ of files in the SquashFS, which might make them boot somewhat slower.
1. Boot this USB stick on bare-metal a first time to trigger re-partitioning.
2. Boot this USB stick a second time, measuring the boot time (from the
syslinux menu until the GNOME desktop is ready -- quickly press
ENTER in the Greeter).
ENTER in the Welcome Screen).
3. Compare with the boot time of the previous Tails version. The new
one should not be significantly slower to start.
......
......@@ -106,7 +106,7 @@ Requirements on the guest (the remote shell server):
firewall exceptions; actually we don't want any network traffic at
all from it, but this kind of follows from the previous requirement
any way)
* must start before Tails Greeter. Since that's the first point of
* must start before the Welcome Screen. Since that's the first point of
user interaction in a Tails system (if we ignore the boot menu), it
seems like a good place to be able to assume that the remote shell
is running.
......@@ -217,11 +217,11 @@ This step:
* verifies that we see the boot menu
* adds any boot options added via `I set Tails to boot with options ...`
* makes sure that Tails Greeter starts
* makes sure that the Welcome Screen starts
* makes sure that the remote shell is up and running
Note that the "I set sudo password ..." step has to be run before the
other Tails Greeter option steps as it relies on keyboard navigation.
other option steps of the Welcome Screen as it relies on keyboard navigation.
And I set sudo password "asdf"
......
......@@ -3,7 +3,7 @@
1. Start Tails and [[set up an administration password
|doc/first_steps/startup_options/administration_password]].
Do not enable the persistent volume in <span class="application">Tails Greeter</span>.
Do not enable the persistent volume in the Welcome Screen.
1. Open <span class="application">Disks</span> from the menu
<span class="menuchoice">
......
......@@ -14,7 +14,7 @@ To start the persistent volume assistant, choose
The error message <span class="emphasis">Error, Persistence partition is not
unlocked.</span> means that the persistent volume was not enabled from
<span class="application">Tails Greeter</span>. So you can not configure it
the Welcome Screen. So you can not configure it
but you can delete it and create a new one.
</div>
......
......@@ -15,7 +15,7 @@ which is a much slower operation.</p>
1. Start Tails from the USB stick on which you want to delete the
persistent volume.
Do not enable the persistent volume in <span class="application">Tails Greeter</span>.
Do not enable the persistent volume in the Welcome Screen.
1. Choose
<span class="menuchoice">
......
Markdown is supported
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