[tahoe-lafs-trac-stream] [tahoe-lafs] #1694: package client and server separately

[tahoe-lafs]

#1694: package client and server separately
--------------------------+------------------------------------------------
     Reporter:  zooko     |      Owner:  somebody
         Type:            |     Status:  new
  enhancement             |  Milestone:  undecided
     Priority:  normal    |    Version:  1.9.1
    Component:            |   Keywords:  performance security packaging p2p
  packaging               |
   Resolution:            |
Launchpad Bug:            |
--------------------------+------------------------------------------------
Changes (by zooko):

 * keywords:  performance security packaging => performance security
     packaging p2p


Old description:

> 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.

New description:

 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.

--

Comment:

 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]

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1694#comment:3>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage