[Pkg-privacy-maintainers] TorBirdy 0.2.2

[Sukhbir Singh]

Hi,

> Hi!
> 
> intrigeri:
> > u:
> >> it looks like in components/torbirdy.js the port for the keyserver is
> >> now hardcoded to be 9050 - system tor's port. In the previous version it
> >> used to be 9150 - TorBrowser's port.
> > 
> > I think I broke this with
> > commit 09acfd09c465ba9cb50b6a4d03f155f02a081391. Sorry!
> 
> oops!
> 
> > Sukhbir: please let me know if I should prepare+test+submit a fix or
> > if you'll handle it yourself.
> > 
> >> I'm unsure what this means. For the official Debian package this is
> >> practical because we want people to use system tor by default, however I
> >> wonder if this setting can be modified by the user when changing
> >> TorBirdy's settings or if people will get stuck when operating in other
> >> configurations (using TorBrowser or Tails for example). See line 276 on
> >> https://gitweb.torproject.org/torbirdy.git/tree/components/torbirdy.js
> > 
> > Last time I checked, this could be changed in the expert/advanced
> > TorBirdy settings.
> 
> It can be changed but the change does need seem to have any effect. I've
> tried it, but I've not extensively tested it.

I am sorry for delaying this; somehow I had marked this as read. I have pushed
a fix. Do I also need to make a new release for the Debian package or is that
fine for now? (I see that the package has been uploaded but thought I should
confirm.)

Thanks,

-- 
Sukhbir