Banana error?

[Brian Warner]

On 9/28/14 2:34 PM, Roland Haeder wrote:

>> Cannot Tahoe "anonymize" these files, e.g. replacing ids with
>> abc123, changing IP addresses to 1.2.3.4 and such?

Ticket #57 is a plan to do that anonymization, but it's not been
implemented yet, unfortunately.

> I'm still getting those error messages:
> 
> --------------------------------------- File
> "/usr/lib/python2.7/dist-packages/foolscap/referenceable.py", line 
> 821, in decode_location_hints hint = ("tcp", fields["host"], 
> int(fields["port"])) exceptions.KeyError: 'host' 
> ---------------------------------------

(and your --version pastebin says that you've got foolscap-0.6.5 and
twisted-14.0.0).

Hrm. That line changed recently (in the subsequent foolscap-0.7.0
release), to accomodate location hints that look like
"tcp:HOSTNAME:PORTNUM". But I don't think any Tahoe nodes should be
emitting location hints like that.. I'd believed they were all of the
form "HOSTNAME:PORTNUM", without the "tcp:" prefix.

Could you look at the nodes on your grid and tell us what the shape of
their FURLs are? The clients will have a file in their basedir named
private/storage.furl or private/logport.furl, and the introducer will
have a private/introducer.furl . FURLs all have the form:

 pb://TUBID@LOCATIONHINTS/SWISSNUM

where "TUBID" is a 32-character-long base32-encoded string,
"LOCATIONHINTS" are comma-separated hints, each hint is
"tcp:HOSTNAME:PORT" or "HOSTNAME:PORT" or "IPADDR:PORT" or something
like that, and "SWISSNUM" is another base32-encoded string.

Don't tell us the swissnum, that's secret. And we don't need to know the
tubid, or the actual hostnames or port numbers. But could you tell us if
the connection hints look like "tcp:HOSTNAME:PORT" or
"ipv4:HOSTNAME:PORT" or "HOSTNAME:PORT" or something else?

It's possible that upgrading to Foolscap-0.7.0 will fix this, but if so,
I'd like to know why it was broken, because foolscap-0.6.5's change to
referenceable.py was supposed to be fully backwards-compatible.

thanks,
 -Brian