On Fri, 02 May 2025 17:13:29 +0200,
Kirill A. Korinsky wrote:
>
> On Thu, 01 May 2025 12:54:21 +0200,
> Stuart Henderson wrote:
> >
> > Good find.
> >
> > Seeing
> > https://github.com/ThirVondukr/passlib/pull/15#issuecomment-2844561564
> > do you think it might be worth waiting to see what g
On Thu, 01 May 2025 12:54:21 +0200,
Stuart Henderson wrote:
>
> Good find.
>
> Seeing https://github.com/ThirVondukr/passlib/pull/15#issuecomment-2844561564
> do you think it might be worth waiting to see what gets committed
> upstream first?
>
Here a diff which updates security/py-passlib to 1
On Thu, 01 May 2025 12:54:21 +0200,
Stuart Henderson wrote:
>
> Good find.
>
> Seeing https://github.com/ThirVondukr/passlib/pull/15#issuecomment-2844561564
> do you think it might be worth waiting to see what gets committed
> upstream first?
>
Absolutley, I'll wait until upstream commit it, or
Good find.
Seeing https://github.com/ThirVondukr/passlib/pull/15#issuecomment-2844561564
do you think it might be worth waiting to see what gets committed
upstream first?
On 2025/05/01 10:14, Kirill A. Korinsky wrote:
> ports,
>
> I had narrowed down the issue with mitmproxy too verbose logging
ports,
I had narrowed down the issue with mitmproxy too verbose logging to a the
root cause: update of security/py-passlib.
The new fork includes
https://github.com/ThirVondukr/passlib/commit/650121d0cd7a6da775b2f44573de4c165b80d93c
which had switched the code to use logging in the way like loggi
