Changes between Version 248 and Version 249 of doc/TorBOX/Dev


Ignore:
Timestamp:
Mar 2, 2012, 12:59:28 AM (7 years ago)
Author:
proper
Comment:

closed "front page - how to install: download, build/shell script, manual configuration"

Legend:

Unmodified
Added
Removed
Modified
  • doc/TorBOX/Dev

    v248 v249  
    4040== SELinux AppArmor grsecurity [ENHANCEMENT] ==
    4141 * (proper) [http://www.cyberciti.biz/tips/selinux-vs-apparmor-vs-grsecurity.html SELinux AppArmor grsecurity - introduction]. Related to [https://trac.torproject.org/projects/tor/wiki/doc/TorBOX/SecurityAndHardening TorBOX/SecurityAndHardening]. We can provide instructions to add an additional security layer for critical (network communicating) components, such as iptables, Tor, kernel (if possible), Tor Browser, XChat, etc. It shouldn't end in a maintenance hell. We got to discover which system is the most easy to use one, click and go, if that is possible.
    42 
    43 == front page - how to install: download, build/shell script, manual configuration [DONE?] ==
    44  * (proper) I'd like to further tweak the front page. Therefore I suggest three ways. 1. [https://trac.torproject.org/projects/tor/wiki/doc/TorBOX/Download?action=edit download] - binaries (for most end users) 2. using the build/shell script - the source code (for developers, advanced linux users, bare metal users, unsupported virtual machines, people who distrust) 3. manual configuration - the technical documentation (for developers, advanced linux users, interest people). Each site must offer all information needed for the chosen method.
    45  * (proper) Right now the first time user clicks on the front page, clicks to how to install, and then it's a very little mess. Not optimal. As of right now the shell script has also to much discussion inside (gpg keys, which is clarified one page before already...). Your opinion?
    46  * (anonymous) Sounds great! Shell script is fixed.
    47  * (anonymous) IMPLEMENTED? Anything missing?
    48  * (proper) Very well... The only thing which is slightly suboptimal is, that TorBOX/HowToInstall and TorBOX/ManualConfiguration have some redundancy. Until step "sudo apt-get install openssh-server" the pages are equal. First drawback of this is, if you edit one page, you also have to edit the other one. HowToInstall is the easy configuration and should contain as little background information as possible. ManualConfiguration should be fully technically justified. [[BR]]
    49 Solution? Maybe we could delete the redundancy under ManualConfiguration and link to HowToInstall and tell 'do it until "sudo apt-get install openssh-server" and then come back here'. And tell on HowToInstall after "sudo apt-get install openssh-server" 'you can also do it manually, see ManualConfiguration'. [[BR]]
    50 Let's image we get the spoiler plugin, that would allow us to hide the technical comments on HowToInstall and leave it available for interested people. (spoiler plugin is very likely to happen, the author said, it may be possible to use it, even without the plugin through an alternative)
    51  * (proper) What would maybe also confuse me, if you wouldn't know, that there is also a shell script for the Tor-Workstation. The user isn't informed how to use it. Perhaps it would be more logical to let the user install the Tor-Gateway first and install the Tor-Workstation after that. The EasyConfiguration / Tor-Workstation script could do more useful tasks in the future, such as downloading and configuring TorBrowser for TorBOX.
    52  * (anonymous) Fixed all suggestions. T-W script is pointless anyway because it's difficult to transfer to the VM (this would only entice users to do unsafe things), I moved it to Dev/ClientVM. I think we should just delete the whole Manual Config. It's pretty pointless IMO. It's only intended for power users and those can modify the shell script (which is pretty well commented, more than necessary I would think). There is the network test step which was missing in the how to but I've fixed that. There isn't much information left that is only available on manual but not on easy config. It's all pretty obvious.
    53  * (proper) I wouldn't have thought, that the shell script is taking over the project. =) You're right, your solution solves the redundancy quite elegant. There is no need to have ManualConfiguration and a ShellScript at the same time. Let's cannibalise ManualConfiguration, make it a scratch pad. Cut from ManualConfiguration and paste into shell script. IMO the shell script should contain all comments, explanations, reasoning, it's obvious to us, but not necessarily for other new developers who audit our project or want to contribute. Please don't delete anything, like "tor --verify-config" or "usewithtor...", these where all useful findings during development. Do you think we could continue the 'step layout' in the shell script (like "Step 3.5: Firewall Configuration" "Step 3.5a: Create Firewall script"), imo that improves readability and explains.
    54  * (anonymous) Sure, comments don't hurt. But I don't think we should run something like "tor -verify-config" when we already control the content of torrc and know that it's valid. usewithtor is already in the how to. Generally I'd say things belong into the how to if users should run them (or have to run them if things don't work), the rest can go into the script comments.
    55  * (proper) All right, agreed. Small clarification: things like "tor -verify-config", don't put it in the script, but also please don't let it get lost in nirvana -> scratch pad, as it was useful in development. Sidenote: thanks for fixing my typos. =)
    5642
    5743== do not turn off screen after a while (OPTIONAL) [OPEN] ==
     
    568554 * (proper) Sidenote: I suggested to use stenography for private bridges. [https://lists.torproject.org/pipermail/tor-talk/2012-February/023351.html tor-talk - bridges: stenography to hide Tor traffic] Unfortunally I messed up to monitor the mailing list and to answer again. Not sure if obsfproxy is real stenography. At the moment it looks for me as the censurer and the developers have a race, one updating, another one updating. But with real stenography they could never detect it, also not after seeing the source code. (Only the private key has to remain private.) About this topic: agreed, it's done.
    569555
     556== front page - how to install: download, build/shell script, manual configuration [IMPLEMENTED] ==
     557 * (proper) I'd like to further tweak the front page. Therefore I suggest three ways. 1. [https://trac.torproject.org/projects/tor/wiki/doc/TorBOX/Download?action=edit download] - binaries (for most end users) 2. using the build/shell script - the source code (for developers, advanced linux users, bare metal users, unsupported virtual machines, people who distrust) 3. manual configuration - the technical documentation (for developers, advanced linux users, interest people). Each site must offer all information needed for the chosen method.
     558 * (proper) Right now the first time user clicks on the front page, clicks to how to install, and then it's a very little mess. Not optimal. As of right now the shell script has also to much discussion inside (gpg keys, which is clarified one page before already...). Your opinion?
     559 * (anonymous) Sounds great! Shell script is fixed.
     560 * (anonymous) IMPLEMENTED? Anything missing?
     561 * (proper) Very well... The only thing which is slightly suboptimal is, that TorBOX/HowToInstall and TorBOX/ManualConfiguration have some redundancy. Until step "sudo apt-get install openssh-server" the pages are equal. First drawback of this is, if you edit one page, you also have to edit the other one. HowToInstall is the easy configuration and should contain as little background information as possible. ManualConfiguration should be fully technically justified. [[BR]]
     562Solution? Maybe we could delete the redundancy under ManualConfiguration and link to HowToInstall and tell 'do it until "sudo apt-get install openssh-server" and then come back here'. And tell on HowToInstall after "sudo apt-get install openssh-server" 'you can also do it manually, see ManualConfiguration'. [[BR]]
     563Let's image we get the spoiler plugin, that would allow us to hide the technical comments on HowToInstall and leave it available for interested people. (spoiler plugin is very likely to happen, the author said, it may be possible to use it, even without the plugin through an alternative)
     564 * (proper) What would maybe also confuse me, if you wouldn't know, that there is also a shell script for the Tor-Workstation. The user isn't informed how to use it. Perhaps it would be more logical to let the user install the Tor-Gateway first and install the Tor-Workstation after that. The EasyConfiguration / Tor-Workstation script could do more useful tasks in the future, such as downloading and configuring TorBrowser for TorBOX.
     565 * (anonymous) Fixed all suggestions. T-W script is pointless anyway because it's difficult to transfer to the VM (this would only entice users to do unsafe things), I moved it to Dev/ClientVM. I think we should just delete the whole Manual Config. It's pretty pointless IMO. It's only intended for power users and those can modify the shell script (which is pretty well commented, more than necessary I would think). There is the network test step which was missing in the how to but I've fixed that. There isn't much information left that is only available on manual but not on easy config. It's all pretty obvious.
     566 * (proper) I wouldn't have thought, that the shell script is taking over the project. =) You're right, your solution solves the redundancy quite elegant. There is no need to have ManualConfiguration and a ShellScript at the same time. Let's cannibalise ManualConfiguration, make it a scratch pad. Cut from ManualConfiguration and paste into shell script. IMO the shell script should contain all comments, explanations, reasoning, it's obvious to us, but not necessarily for other new developers who audit our project or want to contribute. Please don't delete anything, like "tor --verify-config" or "usewithtor...", these where all useful findings during development. Do you think we could continue the 'step layout' in the shell script (like "Step 3.5: Firewall Configuration" "Step 3.5a: Create Firewall script"), imo that improves readability and explains.
     567 * (anonymous) Sure, comments don't hurt. But I don't think we should run something like "tor -verify-config" when we already control the content of torrc and know that it's valid. usewithtor is already in the how to. Generally I'd say things belong into the how to if users should run them (or have to run them if things don't work), the rest can go into the script comments.
     568 * (proper) All right, agreed. Small clarification: things like "tor -verify-config", don't put it in the script, but also please don't let it get lost in nirvana -> scratch pad, as it was useful in development. Sidenote: thanks for fixing my typos. =) -> (proper) Yep, done very nicely.
     569
    570570= wiki editing =
    571571 * [http://trac.edgewall.org/wiki/WikiFormatting list of all commands]