[tahoe-lafs-trac-stream] [tahoe-lafs] #649: Validation of configuration settings

[tahoe-lafs]

#649: Validation of configuration settings
--------------------------------+------------------------
     Reporter:  ndurner         |      Owner:
         Type:  enhancement     |     Status:  new
     Priority:  minor           |  Milestone:  eventually
    Component:  code-nodeadmin  |    Version:  1.3.0
   Resolution:                  |   Keywords:  usability
Launchpad Bug:                  |
--------------------------------+------------------------

Old description:

> Configuration settings like tub.location and introducer.furl are not
> validated by the code.
> tub.location is silently ignored if a port spec is missing. The same is
> true for introducer.furl if there's an error in the FURL ("at" instead of
> "@", as copied from http://allmydata.org/pipermail/tahoe-
> dev/2009-February/001341.html)

New description:

 Configuration settings like tub.location and introducer.furl are not
 validated by the code.
 tub.location is silently ignored if a port spec is missing. The same is
 true for introducer.furl if there's an error in the FURL ("at" instead of
 "@", as copied from http://allmydata.org/pipermail/tahoe-
 dev/2009-February/001341.html)

--

Comment (by saeftl):

 The documentation in {{{docs/configuration.rst}}} should state that
 {{{tub.location}}} MUST include a portnumber,
 even if {{{tub.port}}} already specified one.



 It would be very good if {{{tahoe}}} would check if the {{{tub.location}}}
 in {{{tahoe.cfg}}} corresponds to the values
 in existing {{{private/*.furl}}} files.


 As of 1.9.2 it does not, so that the {{{tub.location}}} in {{{tahoe.cfg}}}
 is in fact
 overridden by existing {{{private/*.furl}}} files
 (why these files have to be in {{{private/ }}} for storage nodes but not
 for introducers is another question...)

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