Opened at 2012-03-26T13:11:24Z
Last modified at 2016-05-05T01:09:46Z
#1694 new enhancement
package client and server separately — at Version 3
| Reported by: | zooko | Owned by: | somebody |
|---|---|---|---|
| Priority: | normal | Milestone: | undecided |
| Component: | packaging | Version: | 1.9.1 |
| Keywords: | performance security packaging p2p | Cc: | |
| Launchpad Bug: |
Description (last modified by zooko)
https://tahoe-lafs.org/pipermail/tahoe-dev/2012-March/007084.html
https://tahoe-lafs.org/pipermail/tahoe-dev/2012-March/007085.html
Here is a story that we should implement:
As a system administrator, I install the tahoe-lafs server software on a machine, and I know that since I didn't install the client software, the process running there will not import any code which is useful only to clients, will not open connections to other servers (which is #344), will not expose client-only services (which could be a security risk), and will not use up extra RAM or other computational resources to do client-only behavior. Also, installing the tahoe-lafs server doesn't depend on other software packages which are needed solely for the client.
Likewise, I can install the tahoe-lafs client software on a machine and have all the equivalent freedom from unexpected serverish behavior.
Change History (3)
comment:1 Changed at 2012-03-29T19:09:24Z by davidsarah
- Priority changed from major to normal
comment:2 Changed at 2012-11-22T01:10:37Z by davidsarah
- Keywords performance security packaging added
comment:3 Changed at 2013-06-25T15:47:33Z by zooko
- Description modified (diff)
- Keywords p2p added
adding keyword p2p to tag tickets that have to do with the open question of "Is Tahoe-LAFS client-server or is it peer-to-peer?": pipermail/tahoe-dev/2012-July/007533.html