?
ifconfig-kdump.result.2021-12-17_12-34
Description: Binary data
"Theo de Raadt" writes:
> Claudio Jeker wrote:
>
>> On Thu, Dec 16, 2021 at 03:55:43PM +0800, Vladimir Nikishkin wrote:
>> > Hello, everyone
>> >
>> > Recently I had a
.
What am I doing wrong? Is there something specific that needs to be
permitted to profile ifconfig?
--
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)
those who are, comment on that issue.
--
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)
Go.pm does not expect to be called the second time with a name.
Hope this helps.
--
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)
This has actually been reported before:
https://www.mail-archive.com/bugs@openbsd.org/msg14189.html
Jean-Pierre de Villiers writes:
> On 21/08/11 04:34pm, Vladimir Nikishkin wrote:
>> I do not think my setup is related to "TLS Inspection".
>
> Apologies, my misunders
6:15, Jean-Pierre de Villiers
wrote:
>
> On 21/08/11 02:40pm, Vladimir Nikishkin wrote:
> > However, if I keep "with tls", the requests to port 81 are going
> > encrypted, and are failing with the following message in relayd logs:
> > `SSL routines:ST_CONNECT:tlsv1
going
encrypted, and are failing with the following message in relayd logs:
`SSL routines:ST_CONNECT:tlsv1 alert protocol version`,
`TLS handshake error: handshake failed:`.
There should not be any TLS handshakes at port 81, because the backend
at port 81 is http-only.
Could someone verify that this is the ca
t, obviously, the laptop does not work then.
How to correct the setup?
--
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)
w fresh structures are initialised in OpenBSD) In
either case, it is not useful.
In effect, `ndp -s ` always fails, because this check is
always false.
--
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)
o have the adoption rate of 33%, not such an uncommon
thing any more.
--
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)
10 matches
Mail list logo
