Ulrike Uhlig:
> I agree with you that there should be a long term solution such as
> creating a vendor specific file. However, right now I have not enough
> time to test that in detail and I want to bring out the new upstream
> version nevertheless.
> So I'll do that for now, leave this bug open a
Hi,
Right, it would not work out of the box without the dependency.
I agree with you that there should be a long term solution such as
creating a vendor specific file. However, right now I have not enough
time to test that in detail and I want to bring out the new upstream
version nevertheless.
intrigeri:
> I mean, there are (somewhat) good reasons why OnionShare needs to use
> an instance of Tor on which it has full control, hence the dependency
> on torbrowser-launcher (until that's fixed thanks to onion-grater :)
If by "good reasons" you mean "OnionShare also is a Tor controller so it
Hi,
Ulrike Uhlig:
> Indeed, these (old) patches are actually
> not even needed. I've decided to delete them from the packaging. This
> will result in
> * new users will use the default TorBirdy configuration, which uses port
> 9150, or TorBrowser's tor.
Does it imply that xul-ext-torbirdy will ne
Hi!
thanks for pointing this out. Indeed, these (old) patches are actually
not even needed. I've decided to delete them from the packaging. This
will result in
* new users will use the default TorBirdy configuration, which uses port
9150, or TorBrowser's tor.
* every user is able to modify TorBird
5 matches
Mail list logo
