You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 14, 2020. It is now read-only.
OnionBalance fails when an instance address with the .onion extension is listoed in the config file. It fetches the correct descriptor but it does not successfully compare the onion addresses.
And shortly after start up I would get
| [WARNING]: Received a descriptor with address kpw6vrobjzz4yd7x.onion that did not match any configured service instances.
Digging a little, suggests that onionbalance would try to set up things
and fetch the descriptor for kpw6vrobjzz4yd7x.onion. However, when it
was getting the descriptor, it ended up being confused about the .onion
extensioni. I added some log lines to descriptor.py's descriptor_received():
| [WARNING]: [weasel] iterating over configured services
| [WARNING]: [weasel] service <onionbalance.service.Service object at 0x7f03bff246d8>
| [WARNING]: [weasel] instance <onionbalance.instance.Instance object at 0x7f03bff24588>
| [WARNING]: [weasel] onion_address kpw6vrobjzz4yd7x.onion
| [WARNING]: [weasel] descriptor_onion_address kpw6vrobjzz4yd7x
^^^^^^^^^^ of course, == will fail between these.
| [WARNING]: Received a descriptor with address kpw6vrobjzz4yd7x.onion that did not match any configured service instances.
I suggest that onionbalance either handle .onion as address everywhere,
or that it reject them earlier.
OnionBalance fails when an instance address with the .onion extension is listoed in the config file. It fetches the correct descriptor but it does not successfully compare the onion addresses.
Original ticket: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832821
The text was updated successfully, but these errors were encountered: