Commit d1da4369 authored by Tails developers's avatar Tails developers
Browse files

Merge branch 'master' of ssh://webmasters.boum.org/~/wiki

parents 221382ae ea80c010
......@@ -8,5 +8,4 @@ was released. If HTP fails a first time, and if the current time clock
is different by more than 6 (?) months, we start by setting the time
clock to the live system release before attempting HTP once more.
This issue will be fixed when
[[todo/remove_the_htp_user_firewall_exception]] is implemented.
> [[pending]] for 0.8
......@@ -84,7 +84,7 @@ Of course, that still allows requests for invalid names like "http://...---...i2
Many apologies if my English is unclear: please feel free to ask for clarification on any points.
> Thanks! All this was fixed in the devel branch (41ee709)
> => [[!taglink pending]]
> => [[pending]]
>> Thanks for the update, and for fixing up my markup - I learned
>> stuff! :D Is the devel branch publicly available on some SVN
......
In Tails 0.8-rc2, the msva does not use the configured keyserver but
pool.sks-keyservers.net.
`.xsession-errors` says:
Not a valid keyserver (from gpg config /home/amnesia/.gnupg/gpg.conf):
hkp://2eghzlv2wwcq7u7y.onion
[Reported upstream](https://labs.riseup.net/code/issues/3457).
......@@ -34,3 +34,7 @@ linux 3.0.0-1 from unstable did not solve the issue either, however.
> to work properly though: settings it to 1000 makes it work in
> VirtualBox with its virtual CD-ROM drive, but no value seems to work
> on the one real machine I have available with a CD-ROM drive.
>> This was half-workaround'd for 0.8 => the eject button now triggers
>> shutdown/sdmem sequence, but the CD is not ejected, which is a
>> regression.
......@@ -111,17 +111,16 @@ Check the output for:
Those tests shall be run using GnuPG on the command-line, the
Seahorse GUI and FireGPG:
* key search/receive: torified? going to the configured hkps://
server?
* key search/receive: torified? going to the configured keyserver?
- `gpg --search` tells what server it is connecting to
- the IP of the configured keyserver must appear in Vidalia's list
of connections
- the connection to the configured keyserver must appear in Vidalia's
list of connections
- if you run a keyserver, have a look there.
# Monkeysphere
* Monkeysphere validation agent key search/receive: torified?
(the MSVA is simply not working currently, ignore this.)
* Monkeysphere validation agent key search/receive: torified? uses
configured keyserver?
# HTP
......@@ -134,11 +133,7 @@ Seahorse GUI and FireGPG:
4. connect the network cable
=> the date should be corrected and Tor/Vidalia should start
correctly. Except it does not work currently as the queried servers'
SSL certificates are invalid if the date is too much wrong
=> also test with a slightly less wrong date, which is supposed to
work already.
correctly.
# erase memory on shutdown
......@@ -153,7 +148,7 @@ steps that are worth [[a dedicated page|test/erase_memory_on_shutdown]].
# Virtualization support
* `modinfo vboxdrv` should work
* `modinfo vboxguest` should work
* test in VirtualBox
# Misc
......@@ -171,3 +166,5 @@ steps that are worth [[a dedicated page|test/erase_memory_on_shutdown]].
* Boot and check basic functionality is working for every supported language.
* Try to start with the `truecrypt` option on boot, see if it can be found in
the Application -> Accessories menu and that it runs correctly
* Virtual keyboard must work and be auto-configured to use the same
keyboard layout as the X session.
Objectives
==========
The objective is to make it easier to navigate through the website by:
- Having more direct accesses to important parts of the website. For that we
propose to have, on some items, two levels of navigation in the sidebar.
- Remapping the filesystem of the git to match better the website navigation.
That would improve the display of the breadcrumbs and make it easier to know
« where you are ».
Reorganization
==============
Abstract of what should go in each part:
- **Documentation**: static documentation on how to use Tails.
- **Contribute**: everything related to advertizing, auditing, improving or
developping Tails.
- **Help & Support**: tools to help the users who require more interaction than
just reading the documentation.
According to that, here are a few movements we propose for existing pages:
- bug_reporting.mdwn → contribute/
- build → contribute/
- chat → support/ for #tails, contribute/ for #tails + #tails-dev
- customize → contribute/
- features → doc/
- forum → support/ + show it in the navigation
- found_a_problem → support/
- git → contribute/
- GnuPG_key → doc/
- license → doc/
- MaxGSoC → contribute/
- patch → contribute/
- stay_tuned → not linked anymore
- support/truecrypt → doc/
- support/virtualization → doc/
- support/walkthrough → doc/
- talk-dev → contribute/
- talk-users → support/
- todo → contribute/tickets
- trusting_tails_signing_key → doc/
- upgrade → doc/
......@@ -2,4 +2,4 @@ Tails ships i2p 0.80 while 0.84 is released.
See [[Tails I2P design page|contribute/design/I2P]] for details about
how it shall be reviewed and upgrade steps.
[[!tag todo/code]]
> [[!taglink pending]] for Tails 0.8
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