[sr-dev] [kamailio/kamailio] failed `tls` module build on master (Issue #3621)
failed `tls` module build on master ``` CC (gcc) [M crypto.so] api.o CC (gcc) [M crypto.so] crypto_aes.o CC (gcc) [M crypto.so] crypto_evcb.o CC (gcc) [M crypto.so] crypto_mod.o CC (gcc) [M crypto.so] crypto_uuid.o LD (gcc) [M crypto.so] crypto.so CC (gcc) [M tls.so] tls_bio.o CC (gcc) [M tls.so] tls_cfg.o CC (gcc) [M tls.so] tls_config.o CC (gcc) [M tls.so] tls_ct_wrq.o CC (gcc) [M tls.so] tls_domain.o CC (gcc) [M tls.so] tls_dump_vf.o CC (gcc) [M tls.so] tls_init.o CC (gcc) [M tls.so] tls_locking.o CC (gcc) [M tls.so] tls_map.o CC (gcc) [M tls.so] tls_mod.o CC (gcc) [M tls.so] tls_rand.o CC (gcc) [M tls.so] tls_rpc.o CC (gcc) [M tls.so] tls_select.o CC (gcc) [M tls.so] tls_server.o CC (gcc) [M tls.so] tls_util.o CC (gcc) [M tls.so] tls_verify.o LD (gcc) [M tls.so] tls.so CC (gcc) [M auth_identity.so] auth_crypt.o auth_crypt.c: In function 'rsa_sha1_enc': auth_crypt.c:214:9: warning: 'RSA_sign' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 214 | if(RSA_sign(NID_sha1, sstrcrypted, sizeof sstrcrypted, | ^~ In file included from /usr/include/openssl/x509.h:36, from /usr/include/openssl/pem.h:23, from auth_crypt.c:33: /usr/include/openssl/rsa.h:356:27: note: declared here 356 | OSSL_DEPRECATEDIN_3_0 int RSA_sign(int type, const unsigned char *m, | ^~~~ auth_crypt.c: In function 'rsa_sha1_dec': auth_crypt.c:258:9: warning: 'EVP_PKEY_get1_RSA' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 258 | hpubkey = EVP_PKEY_get1_RSA(pkey); | ^~~ In file included from /usr/include/openssl/pem.h:22, from auth_crypt.c:33: /usr/include/openssl/evp.h:1359:16: note: declared here 1359 | struct rsa_st *EVP_PKEY_get1_RSA(EVP_PKEY *pkey); |^ auth_crypt.c:266:9: warning: 'RSA_verify' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 266 | if(RSA_verify(NID_sha1, (unsigned char *)ssha, sshasize, | ^~ In file included from /usr/include/openssl/x509.h:36, from /usr/include/openssl/pem.h:23, from auth_crypt.c:33: /usr/include/openssl/rsa.h:359:27: note: declared here 359 | OSSL_DEPRECATEDIN_3_0 int RSA_verify(int type, const unsigned char *m, | ^~ auth_crypt.c:273:17: warning: 'RSA_free' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 273 | RSA_free(hpubkey); | ^~~~ In file included from /usr/include/openssl/x509.h:36, from /usr/include/openssl/pem.h:23, from auth_crypt.c:33: /usr/include/openssl/rsa.h:301:28: note: declared here 301 | OSSL_DEPRECATEDIN_3_0 void RSA_free(RSA *r); |^~~~ auth_crypt.c:298:9: warning: 'RSA_free' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 298 | RSA_free(hpubkey); | ^~~~ In file included from /usr/include/openssl/x509.h:36, from /usr/include/openssl/pem.h:23, from auth_crypt.c:33: /usr/include/openssl/rsa.h:301:28: note: declared here 301 | OSSL_DEPRECATEDIN_3_0 void RSA_free(RSA *r); |^~~~ CC (gcc) [M auth_identity.so] auth_dynstr.o CC (gcc) [M auth_identity.so] auth_hdrs.o CC (gcc) [M auth_identity.so] auth_http.o CC (gcc) [M auth_identity.so] auth_identity.o auth_identity.c: In function 'mod_init': auth_identity.c:414:9: warning: 'PEM_read_RSAPrivateKey' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 414 | glb_hmyprivkey = PEM_read_RSAPrivateKey(hpemfile, NULL, NULL, NULL); | ^~ In file included from auth_identity.c:43: /usr/include/openssl/pem.h:447:1: note: declared here 447 | DECLARE_PEM_rw_cb_attr(OSSL_DEPRECATEDIN_3_0, RSAPrivateKey, RSA) | ^~ auth_identity.c:425:9: warning: 'RSA_size' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 425 | if(initdynstr(&glb_encedmsg, RSA_size(glb_hmyprivkey))) | ^~ In file included from /usr/include/openssl/x509.h:36, from /usr/include/openssl/pem.h:23, from auth_identity.c:43: /usr/include/openssl/rsa.h:212:27: note: declared here 212 | OSSL_DEPRECATEDIN_3_0 int RSA_size(const RSA *rsa); | ^~~~ auth_identity.c:429:9: warning: 'RSA_size' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 429 | if(initdynstr(&glb_b64encedmsg, (RSA_size(glb_hmyprivkey) / 3 + 1) * 4)) | ^~ In file
[sr-dev] Re: [kamailio/kamailio] failed `tls` module build on master (Issue #3621)
The error was generated during the packaging `wolfssl` module and does not relate to `tls` module. Closing. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3621#issuecomment-1783903685 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
[sr-dev] Re: [kamailio/kamailio] failed `tls` module build on master (Issue #3621)
Closed #3621 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3621#event-10798438655 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
[sr-dev] Re: [kamailio/kamailio] pkg: RPM packaging add kamailio-tls_wolfssl subpackage (PR #3592)
I have packaged `wolfssl` and placed at For CentOS 9 - https://rpm.kamailio.org/centos/9/master/master/x86_64/Packages/w/ For CentOS 8 - https://rpm.kamailio.org/centos/8/master/master/x86_64/Packages/w/ If you need another dist, then you rebuild `.src.rpm`. Could you install packaged wolfssl and update Makefile to use param to allow the use of shared library linking? As example, you can find [in spec file](https://github.com/kamailio/kamailio/blob/55b3ce67709e56be116bb7077931ba7f4c79dff5/pkg/kamailio/obs/kamailio.spec#L1196) [in Makefile](https://github.com/kamailio/kamailio/blob/master/src/Makefile.radius#L24) -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3592#issuecomment-1783911374 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
[sr-dev] sip/voip : DID, URI, ENUM, opened networks : how to understand it better?
hello im coming back to ask on this forum, sorry if im at the wrong place, but i guess there are some sip experts around here (if it's not the right place, tell me where...) i was wondering, what about the public enum usage for sip networks? i mean, is there any type of public networks, known for having an opened/accessible users scheme? eg : here in france there are linphone and ippi, and others (providing software+service) both, offers both software+service, but can be dissociated means its possible (normally) to use another sip software with a provider, etc the idea is, there is what i think called a DID/URI, whom looks like email principle : u...@domain.com ; but in a way, it's a bit similar for xmpp and sip : al...@first.com could email, call or message b...@second.net ; and normally, it's minded to be interoperable (or federated) on an opened-network circuit. what i try to understand is : URI or DID might be i guess, the u...@domain.net. however, if sip is really used today, it's on closed networks. I mean, using data, only whatsapp and others, I guess uses xmpp or sip, but not in an opened-way, means not +123...@whatsapp.org, what would be great to be communicate with, without having to install their app. on ""real"" opened-community, such as callcentrix or voip.ms, it's the case : a user of a domain could reach another domain, using it's DID/URI email. well, I found then that there is a kind of ENUM thing I discovered few days ago. instead of defunct iNum, where it was supposed to be as an online voip accessible and free from internet (like skype) new kind of voip network, ENUM looks like to be enclosed one. As operators mainly looks for ""security"" (or security of closed-business), i found those things : https://wiki.freepbx.org/display/DIMG/SIP+Enum+Support https://en.wikibooks.org/wiki/Voice_over_IP/ENUM_and_E146_Technology https://www.lightreading.com/cable-technology/the-impact-of-enum-on-voip https://lafibre.info/images/peering/201506_efort_carrier_enum.pdf so if i understand well, mainly operators took SIP protocol to create their own voIP network, to their susbcribers ; not bad if it wasnt totally-closed? imho, i then discovered that all operators around the world have (for a part of them) a voip/sip account for all volte or even for business lines. My mind was, sip looks like to be great working. But what surprised me in the bad way : why isnt it possible, because it's 100% data usage, to call them directly from a common "voip/callcentric/linphone/other" sip account? i guess it's a question of money, but i dont understand then why people dont go directly on a sip account if their computer is internet connected h24 or even LTE/5G running permanently on their phone : it would be double unlimited plus free of charge international calls. Know people will tell me "just it's whatsapp", but no : whatsapp brings just simplicity + zero rating in some countries, not privacy-compliant and opened and federated usage. am I wrong? on my own, I would have a little question for the nerds or passionate, like me, to SIP protocol for opened-networks, to ensure it's possible to simple voip communicate with relatives, on the same scheme as email : just call a contact by it's u...@domain.net, and it might work. How could you convince your relatives to go on a such scheme? I mean, in EU we have several voip initiative, whom are fully accessible from worldwide callers, where in N/america there are voip.ms and callcentric, maybe others.. are those users only using it for pstn-paid calls? why not skype then? in addition : is there a directory of opened-sip URI/DID/ENUM to be in touch with, to see what operators/voip service providers permits their users to be called from anywhere around the world? the main advantage of this is like email (or xmpp) : just with a voip/sip software, + a sip account, calls to any other sip user around the world, is generally totally free and unlimited. Why dont people adopt it, instead of whatsapp&etc? are they some opened-voip providers directory, where some individuals or organisations could be called from over the world, through sip? do you know some organisation, NGO or companies whom can be called from just a opened-sip network provider? thank you for reading, and much more if you share your thoughts (and sorry for bad eng..) ___ Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
