Hello,
Theo Buehler wrote on Tue, May 06, 2025 at 06:26:55AM +0200:
> LWS wrote:
>> So it is an openbsd decision although it is not clear to me if it is a
>> security
>> design decision or rather a standards adherence decision, since it seems to
>> me
>> that the software that implements this fea
On Tue, 06 May 2025 01:27:11 +0200,
LWS wrote:
>
> So it is an openbsd decision although it is not clear to me if it is a
> security
> design decision or rather a standards adherence decision, since it seems to
> me
> that the software that implements this feature does it outside the
> standards.
> So it is an openbsd decision although it is not clear to me if it is a
> security
> design decision or rather a standards adherence decision, since it seems to
> me
> that the software that implements this feature does it outside the
> standards.
It's a debugging tool amounting to a complete com
> >
> > If you capture traffic by mitmdump or mitmproxy or mitmweb, and you had
> > installed their certificate to client, it may work, see:
> > https://github.com/mitmproxy/mitmproxy/blob/main/mitmproxy/net/tls.py
> >
>
> * if libssl supports it
>
>
Apparently it doesn't work. This is really annoy
Il giorno lun 5 mag 2025 alle ore 22:20 Theo Buehler
ha scritto:
> On Mon, May 05, 2025 at 10:03:35PM +0200, LWS wrote:
> > So I don't understand why they should not be supported by libssl.
>
> The software uses python bindings to libssl. libssl establishes the keys,
> so it must support the keyl
On Mon, May 05, 2025 at 10:03:35PM +0200, LWS wrote:
> oh, you speak too difficult for me.
> The variables are supported by the software it is written in the
> documentation.
> Also the software is used to analyze the traffic and do deep inspection.
> So I don't understand why they should not be su
On Mon, 05 May 2025 22:15:09 +0200,
Kirill A. Korinsky wrote:
>
> On Mon, 05 May 2025 21:40:27 +0200,
> LWS wrote:
> > Another thing I noticed is the non-functioning of the variables:
> >
> > MITMPROXY_SSLKEYLOGFILE
> > SSLKEYLOGFILE
> >
> > here is some doc: https://docs.mitmproxy.org/stable/
On Mon, 05 May 2025 22:03:35 +0200,
LWS wrote:
>
> [1 ]
> oh, you speak too difficult for me.
> The variables are supported by the software it is written in the
> documentation.
> Also the software is used to analyze the traffic and do deep inspection.
> So I don't understand why they should not
On Mon, 05 May 2025 21:40:27 +0200,
LWS wrote:
>
> hi, the problem seems to be solved only on the first screen. But when you
> start using mitmproxy the logs come back in console.
> I saw that another post on the subject has passed but it seems to me that
> the py3-passlib packages have not been
oh, you speak too difficult for me.
The variables are supported by the software it is written in the
documentation.
Also the software is used to analyze the traffic and do deep inspection.
So I don't understand why they should not be supported by libssl.
I know that the variable has been disabled i
> Another thing I noticed is the non-functioning of the variables:
>
> MITMPROXY_SSLKEYLOGFILE
> SSLKEYLOGFILE
>
> here is some doc: https://docs.mitmproxy.org/stable/howto/wireshark-tls/
> these variables are used to export the encryption keys
Read that last line again and ask yourself why this
hi, the problem seems to be solved only on the first screen. But when you
start using mitmproxy the logs come back in console.
I saw that another post on the subject has passed but it seems to me that
the py3-passlib packages have not been updated.
I only use the system packages because I find the
On Wed, 30 Apr 2025 12:53:21 +0200,
Stuart Henderson wrote:
>
> On 2025/04/30 12:24, Kirill A. Korinsky wrote:
> > On Wed, 30 Apr 2025 01:04:16 +0200,
> > LWS wrote:
> > >
> > > hello,
> > > i hope this is the correct mailing list.
> > > i installed mitmproxy on an openbsd virtual machine on vm
On 2025/04/30 12:24, Kirill A. Korinsky wrote:
> On Wed, 30 Apr 2025 01:04:16 +0200,
> LWS wrote:
> >
> > hello,
> > i hope this is the correct mailing list.
> > i installed mitmproxy on an openbsd virtual machine on vmm, then i updated
> > both the vm and the host to openbsd 7.7.
> > i have a pr
On Wed, 30 Apr 2025 01:04:16 +0200,
LWS wrote:
>
> hello,
> i hope this is the correct mailing list.
> i installed mitmproxy on an openbsd virtual machine on vmm, then i updated
> both the vm and the host to openbsd 7.7.
> i have a problem with mitmproxy because when i launch it on the terminal i
hello,
i hope this is the correct mailing list.
i installed mitmproxy on an openbsd virtual machine on vmm, then i updated
both the vm and the host to openbsd 7.7.
i have a problem with mitmproxy because when i launch it on the terminal in
ssh i don't get the gui interface but a whole series of deb
16 matches
Mail list logo
