readme first
This commit is contained in:
parent
07b009cf76
commit
b241439cce
14
usage.org
14
usage.org
|
@ -8,11 +8,21 @@
|
|||
[[./images/logo.png]]
|
||||
#+END_CENTER
|
||||
|
||||
| [[Operating Systems]] | [[Using Email]] | [[Mailing List]] | [[Play Music]] | [[Syncing to the Cloud]] | [[Microblogging]] | [[Social Network]] | [[Chat Services]] |
|
||||
| [[Readme]] | [[Operating Systems]] | [[Using Email]] | [[Mailing List]] | [[Play Music]] | [[Syncing to the Cloud]] | [[Microblogging]] | [[Social Network]] | [[Chat Services]] |
|
||||
|
||||
* Readme
|
||||
After the system has installed a README file will be generated which contains passwords and some brief advice on using the installed systems. You can read this with the following commands:
|
||||
|
||||
#+BEGIN_SRC bash
|
||||
ssh username@domainname -p 2222
|
||||
emacs ~/README
|
||||
#+END_SRC
|
||||
|
||||
You should transfer any passwords to a password manager such as [[http://www.keepassx.org/][KeepassX]] and then delete them from the README file. To save the file after removing passwords use *CTRL-x CTRL-s*.
|
||||
|
||||
To exit you can either just close the terminal or use *CTRL-x CTRL-c* followed by the *exit* command.
|
||||
* Operating Systems
|
||||
Since many of the systems on the Freedombone are web based your choice of operating system for laptops or desktop machines doesn't matter all that much, but some version of GNU/Linux or on mobile devices Android/Cyanogenmod is recommended. Microsoft Windows may be fine for playing games and other trivia but *do not use it for any serious private communications or data storage purpose*. If you are a journalist, political activist, systems administrator or other professional with a need for confidentiality then using Microsoft Windows will put yourself and your sources, colleages or other group members at heightened risk of surveillance.
|
||||
|
||||
* Using Email
|
||||
** A technical note about email transport security
|
||||
Currently port 465 is used for SMTP. This port is supposedly deprecated for secure email. However, using TLS from the start of the communications seems far more secure than starting off with insecure communications and then trying to upgrade it with a command to begin TLS, as happens with STARTTLS. There are possible attacks against STARTTLS in which the command to begin secure communications is removed or overwritten which could then result in email being transferred in plain text over the internet and be readable by third parties.
|
||||
|
|
Loading…
Reference in New Issue