Hi,
Le 14/08/2024 à 22:19, Adam D. Barratt a écrit :
On Wed, 2024-08-14 at 21:47 +0200, Clément Hermann wrote:
So I did the change (changes + debdiff attached), and tested on a
fresh bullseye install. Of course, obfs4proxy was pulled from
Recommends when I installed my version, but everything
On Wed, 2024-08-14 at 21:47 +0200, Clément Hermann wrote:
> So I did the change (changes + debdiff attached), and tested on a
> fresh bullseye install. Of course, obfs4proxy was pulled from
> Recommends when I installed my version, but everything works fine
> without it, except, of course, the obf
Hi again,
Le 14/08/2024 à 19:37, Salvatore Bonaccorso a écrit :
In my opinion, it should work. I hope to be able to test later today and
will report then.
Ack! Just a reminder: Just make sure we have the uploads in place
before 25th of august, where the window for uploads closes for the
last
Hi,
On Wed, Aug 14, 2024 at 08:54:51AM +0200, Clément Hermann wrote:
> Hi,
>
> Sorry, the emails went to a strange filter. Pinging on IRC was a good move.
> ;)
:-) glad it was of help!
> Le 12/08/2024 à 22:38, Adam D. Barratt a écrit :
> > Re-ping, given that we're less than three weeks from th
Hi,
Sorry, the emails went to a strange filter. Pinging on IRC was a good
move. ;)
Le 12/08/2024 à 22:38, Adam D. Barratt a écrit :
Re-ping, given that we're less than three weeks from the final bullseye
point release.
Regards,
Adam
On Mon, 2024-07-08 at 19:24 +0100, Jonathan Wiltshire
Re-ping, given that we're less than three weeks from the final bullseye
point release.
Regards,
Adam
On Mon, 2024-07-08 at 19:24 +0100, Jonathan Wiltshire wrote:
> Hi,
>
> Ping on this? Adding the maintenance list as well.
>
> Thanks.
>
> On Sat, Aug 05, 2023 at 11:05:52PM +0200, Moritz Müh
I think having a good version of obfs4proxy in bullseye-backports should be
fine to
remove it from bullseye.
The development of obfs4proxy is stopped since a while, at Tor we have forked
it
into lyrebird[0]. At some point we should package lyrebird and deprecate
obfs4proxy.
[0]
https://gitl
Hi,
Ping on this? Adding the maintenance list as well.
Thanks.
On Sat, Aug 05, 2023 at 11:05:52PM +0200, Moritz Mühlenhoff wrote:
> Am Mon, Jul 31, 2023 at 08:05:29AM +0100 schrieb Jonathan Wiltshire:
> > Hi,
> >
> > On Mon, Jul 04, 2022 at 07:36:12PM +0100, Adam D. Barratt wrote:
> > > Control
Am Mon, Jul 31, 2023 at 08:05:29AM +0100 schrieb Jonathan Wiltshire:
> Hi,
>
> On Mon, Jul 04, 2022 at 07:36:12PM +0100, Adam D. Barratt wrote:
> > Control: retitle -1 RM: obfs4proxy -- RoM; security issues
> > Control: tags -1 + moreinfo
> >
> > On Sat, 2022-03-26 at 21:21 +0100, Paul Gevers wro
Hi,
On Mon, Jul 04, 2022 at 07:36:12PM +0100, Adam D. Barratt wrote:
> Control: retitle -1 RM: obfs4proxy -- RoM; security issues
> Control: tags -1 + moreinfo
>
> On Sat, 2022-03-26 at 21:21 +0100, Paul Gevers wrote:
> > Control: tag -1 bullseye
> >
> > Hi Ana,
> >
> > On 23-03-2022 13:13, Ana
Control: retitle -1 RM: obfs4proxy -- RoM; security issues
Control: tags -1 + moreinfo
On Sat, 2022-03-26 at 21:21 +0100, Paul Gevers wrote:
> Control: tag -1 bullseye
>
> Hi Ana,
>
> On 23-03-2022 13:13, Ana Custura wrote:
> > Opening this bug after a recomendation from debian-security.
> > Ver
Control: tag -1 bullseye
Hi Ana,
On 23-03-2022 13:13, Ana Custura wrote:
Opening this bug after a recomendation from debian-security.
Version 0.0.8 of obfs4proxy has a security bug, which has only been fixed in a
later
version (0.0.13, see bug number #1004374), and also suffers from incompatib
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Opening this bug after a recomendation from debian-security.
Version 0.0.8 of obfs4proxy has a security bug, which has only been fixed in a
later
version (0.0.13, see bug number #1004374), and a
13 matches
Mail list logo