Hello,
On Mon 08 Apr 2024 at 07:15pm +02, Salvatore Bonaccorso wrote:
> Hi Sebastian,
>
> On Mon, Apr 08, 2024 at 06:43:01PM +0200, Sebastian Andrzej Siewior wrote:
>> control: tags -1 patch
>> control: reassign -1 yapet 2.6-1
>>
>> On 2024-04-08 08:32:58 [+0200], Kurt Roeckx wrote:
>> > There
Hi Sebastian,
On Mon, Apr 08, 2024 at 06:43:01PM +0200, Sebastian Andrzej Siewior wrote:
> control: tags -1 patch
> control: reassign -1 yapet 2.6-1
>
> On 2024-04-08 08:32:58 [+0200], Kurt Roeckx wrote:
> > There might be a related change that doesn't allow restarting the
> > operation with the
control: tags -1 patch
control: reassign -1 yapet 2.6-1
On 2024-04-08 08:32:58 [+0200], Kurt Roeckx wrote:
> There might be a related change that doesn't allow restarting the
> operation with the same context without setting things up again.
Yapet is broken and the openssl update revealed the
On 2024-04-07 15:36:37 [+0800], Sean Whitton wrote:
> Hello,
Hi,
> On Sat 06 Apr 2024 at 03:24pm +02, Salvatore Bonaccorso wrote:
>
> > As it is a regression caused by libssl3 3.0.11 based to 3.0.13, why is
> > it reassigned to yapet? (the regression is as well present in
> > unstable).
>
> I
Hello,
On Sat 06 Apr 2024 at 03:24pm +02, Salvatore Bonaccorso wrote:
> As it is a regression caused by libssl3 3.0.11 based to 3.0.13, why is
> it reassigned to yapet? (the regression is as well present in
> unstable).
I was just thinking that it may be a flaw in how YAPET calls into
openssl,
Hello,
On Sat 06 Apr 2024 at 09:30pm +02, Sebastian Andrzej Siewior wrote:
> On 2024-04-06 17:17:45 [+0800], Sean Whitton wrote:
>> Hello,
> Hi,
>
>> It looks like the problem is opening YAPET1.0-format databases, which
>> the manpage explicitly says is meant to work.
>>
>> I've made a sample
On 2024-04-06 17:17:45 [+0800], Sean Whitton wrote:
> Hello,
Hi,
> It looks like the problem is opening YAPET1.0-format databases, which
> the manpage explicitly says is meant to work.
>
> I've made a sample YAPET1.0 database using a stretch VM. Using the
> attached:
>
> - On bookworm, invoke
Hi Sean,
On Sat, Apr 06, 2024 at 04:54:14PM +0800, Sean Whitton wrote:
> control: reassign -1 libssl3,yapet
> control: found -1 libssl3/3.1.5-1
> control: found -1 yapet/2.6-1
> control: retitle -1 libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB
>
> Hello,
>
> On Sat 30 Mar 2024 at
Hello,
On Sat 30 Mar 2024 at 03:01pm +01, Sebastian Andrzej Siewior wrote:
> On 30 March 2024 13:14:37 CET, Sean Whitton wrote:
>
>>I downgraded, changed the password for my database to 'asdf',
>>changed it back to the password it had before, upgraded libssl3,
>>and the bug did not appear.
>>
control: reassign -1 libssl3,yapet
control: found -1 libssl3/3.1.5-1
control: found -1 yapet/2.6-1
control: retitle -1 libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB
Hello,
On Sat 30 Mar 2024 at 03:01pm +01, Sebastian Andrzej Siewior wrote:
>>
>>> Also, yapet is unchanged in unstable.
On 30 March 2024 13:14:37 CET, Sean Whitton wrote:
>Hello,
Hi,
>I downgraded, changed the password for my database to 'asdf',
>changed it back to the password it had before, upgraded libssl3,
>and the bug did not appear.
>
>I reverted to my original db, downgraded again, deleted an entry
Hello,
On Sat 30 Mar 2024 at 09:29am +01, Sebastian Andrzej Siewior wrote:
> On 2024-03-30 09:25:27 [+0800], Sean Whitton wrote:
>> Package: libssl3
>> Version: 3.0.13-1~deb12u1
>> Severity: grave
>> Justification: renders package unusable
>> X-Debbugs-Cc: t...@security.debian.org
>> Control:
On 2024-03-30 09:25:27 [+0800], Sean Whitton wrote:
> Package: libssl3
> Version: 3.0.13-1~deb12u1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: t...@security.debian.org
> Control: affects -1 + yapet
>
> Dear maintainer,
>
> This version of libssl3 from
13 matches
Mail list logo
