[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2860: tahoe create-node writes tcp=tor even for i2p

[Tahoe-LAFS]

#2860: tahoe create-node writes tcp=tor even for i2p
--------------------------------+----------------------------
     Reporter:  dawuud          |      Owner:
         Type:  defect          |     Status:  new
     Priority:  normal          |  Milestone:  1.12.1
    Component:  code-nodeadmin  |    Version:  1.12.0
   Resolution:                  |   Keywords:  i2p cli config
Launchpad Bug:                  |
--------------------------------+----------------------------
Changes (by warner):

 * component:  unknown => code-nodeadmin
 * milestone:  undecided => 1.12.1


Old description:

> str4d has found that even without txtorcon installed you can trigger a
> bug where configuring a storage node via the CLI doesn't work as
> expected:
>
> ```
> tahoe create-node --hide-ip --listen=i2p
>
> tahoe create-client --hide-ip --introducer=i2p:...
> ```
>
> these two commands result in the tahoe.cfg being written with:
>
> ```
> [connections]
> tcp=tor
> ```
>
> the subsequent tahoe start command will of course fail.

New description:

 str4d has found that even without txtorcon installed you can trigger a bug
 where configuring a storage node via the CLI doesn't work as expected:

 {{{
 tahoe create-node --hide-ip --listen=i2p

 tahoe create-client --hide-ip --introducer=i2p:...
 }}}

 these two commands result in the tahoe.cfg being written with:

 {{{
 [connections]
 tcp=tor
 }}}

 the subsequent tahoe start command will of course fail.

--

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2860#comment:1>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage