Hi,
Nicolas Braud-Santoni:
> PS: Both bugs are now closed (weasel@ handled it in tor, and I did an NMU
> to ooniprobe);
Great, thanks!
So, given:
> fteproxy is now the only package depending on obfsproxy.
… and:
> - fteproxy hard-depends on obfsproxy, but uses it as a library so
> AppA
On Thu, Dec 14, 2017 at 05:04:35PM +0100, Nicolas Braud-Santoni wrote:
> Hi,
>
> On Tue, Dec 12, 2017 at 08:48:06AM +0100, intrigeri wrote:
> > Hi pkg-privacy-tools & fteproxy maintainers!
> >
> > Nicolas Braud-Santoni:
> > > - tor and ooniprobe suggest obfsproxy, and that should be dropped;
> >
Hi,
On Tue, Dec 12, 2017 at 08:48:06AM +0100, intrigeri wrote:
> Hi pkg-privacy-tools & fteproxy maintainers!
>
> Nicolas Braud-Santoni:
> > - tor and ooniprobe suggest obfsproxy, and that should be dropped;
> > ooniprobe should suggest obfs4proxy instead.
>
> Indeed since upstream commit e603
Hi pkg-privacy-tools & fteproxy maintainers!
Nicolas Braud-Santoni:
> On Mon, Dec 11, 2017 at 07:21:50AM +0100, intrigeri wrote:
>> I suggest first checking why we're still including obfsproxy:
>> I suspect most of the reverse-dependency relationships might be
>> obsolete nowadays (the last upstre
Hi,
On Mon, Dec 11, 2017 at 07:21:50AM +0100, intrigeri wrote:
> Hi,
>
> I suggest first checking why we're still including obfsproxy:
> I suspect most of the reverse-dependency relationships might be
> obsolete nowadays (the last upstream version was released 3 years ago,
> and AFAIK obfs4proxy
Hi,
I suggest first checking why we're still including obfsproxy:
I suspect most of the reverse-dependency relationships might be
obsolete nowadays (the last upstream version was released 3 years ago,
and AFAIK obfs4proxy is the future).
If obfsproxy is still useful in contexts where AppArmor con
6 matches
Mail list logo
