From miconda@gmail.com Tue Apr  4 05:48:43 2023
From: Daniel-Constantin Mierla <miconda@gmail.com>
To: sr-users@lists.kamailio.org
Subject: [SR-Users] Re: segfault during Identity verification (stirshaken)
Date: Tue, 04 Apr 2023 07:48:28 +0200
Message-ID: <4c9af157-663b-f1bf-f74a-fe763d9b7b7a@gmail.com>
In-Reply-To:
 <CADihe3JLt-bh29dGUO9CRHqs1DUvYjhXk7wHAGDM81MZ0qTeUw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0187451559=="

--===============0187451559==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello,

I cannot help with stirshaken module, not being involved in its
development, but I could suggest to try the secsipid module, which I
wrote and I can fix bugs if any is reported. secsipid offers stir/shaken
functionality as well.

Cheers,
Daniel

On 03.04.23 18:31, Yuriy Nasida wrote:
> Hello,
>
> It's kamailio 5.6.4.
>
> I can say that there is no segfault in case Identity is OK but bad
> attempts sometimes are the reason for segfault. Not sure I can
> duplicate but it happens several times per day.
>
> Please look at logs.
>
> in messages:
> Apr =C2=A03 09:40:02 kam1 kernel: [6381565.762987] kamailio[9141]: segfault
> at 746c75616665 ip 00007f20c4cab6df sp 00007ffe7ec51470 error 4 in
> libcrypto.so.1.1[7f20c4c3b000+19e000]
>
> kamailio.log:
> Apr =C2=A03 09:40:02 kam1 kamailio[9141]: NOTICE: <script>: it is INVITE
> with Identity. Lets check Identity
> Apr =C2=A03 09:40:02 kam1 kamailio[9141]: CRITICAL: <core>
> [core/mem/q_malloc.c:501]: qm_free(): BUG: bad pointer
> 0x645f6d6574737973 (out of memory block!) called from tls: tls_init.c:
> ser_free(323) - ignoring
> Apr =C2=A03 09:40:02 kam1 kamailio[9182]: CRITICAL: <core>
> [core/pass_fd.c:277]: receive_fd(): EOF on 53
> Apr =C2=A03 09:40:02 kam1 kamailio[9100]: ALERT: <core> [main.c:774]:
> handle_sigs(): child process 9141 exited by a signal 11
> Apr =C2=A03 09:40:02 kam1 kamailio[9100]: ALERT: <core> [main.c:777]:
> handle_sigs(): core was not generated
> Apr =C2=A03 09:40:02 kam1 kamailio[9100]: CRITICAL: <core>
> [core/mem/q_malloc.c:501]: qm_free(): BUG: bad pointer
> 0x645f6d6574737973 (out of memory block!) called from tls: tls_init.c:
> ser_free(323) - ignoring
>
>
> loadmodule "stirshaken.so"
>
> ####### STIRSHAKEN ######
> modparam("stirshaken", "vs_verify_x509_cert_path", 1)
> modparam("stirshaken", "vs_ca_dir", "/etc/kamailio/stir_CA")
> #modparam("stirshaken", "vs_crl_dir", "/etc/kamailio/CRL")
> modparam("stirshaken", "as_default_key",
> "/etc/kamailio/key/private_key.pem")
> modparam("stirshaken", "vs_cache_certificates", 1)
> modparam("stirshaken", "vs_cache_dir", "/tmp/cert_cache")
> modparam("stirshaken", "vs_cache_expire_s", 100)
>
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0if (is_method("INVITE") && is_present_hf("Identi=
ty")) {
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0xlog("L_NOTICE", "it=
 is INVITE with Identity. Lets
> check Identity\n");
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0if (1 =3D=3D stirsha=
ken_check_identity()) {
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 xlog("L_NOTICE", "Shaken Identity is OK\n");
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0} else {
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0xlog("L_NOTICE", "Shaken Identity is invalid\n");
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0}
> =C2=A0 =C2=A0 =C2=A0 =C2=A0}
>
>
> Please give me some advice.
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to th=
e sender!
> Edit mailing list options or unsubscribe:

--=20
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com


--===============0187451559==--