eXosip2_license(3)

📦 version 5.3.0, in epel 9

🎀 NAME 🎀

eXosip2_license — COPYING

okay so bestie, real talk: this man page isn't like the others. there's no synopsis, no flags, no cute little options list. it's literally just the whole license, front to back, and it's long, so buckle up. this is eXosip2_license(3) from libeXosip2 (yes the man page header says all three: eXosip2_license(3), libeXosip2, eXosip2_license(3) — iconic self-reference tbh) 💅

also important: this is legal text. so everything below in the code blocks is word-for-word — i'm not slangifying actual license clauses, that would be a crime and also a terrible idea. my commentary is my own, the clauses are the clauses. periodt.

📜 GNU GENERAL PUBLIC LICENSE, Version 2, June 1991 📜

        Copyright (C) 1989, 1991 Free Software Foundation, Inc.
            59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
        Everyone is permitted to copy and distribute verbatim copies
        of this license document, but changing it is not allowed.

like — the address, the year, the "changing it is not allowed" — all of it stays, exactly. you may copy and distribute verbatim copies of this license doc, but you may not change it. got it? 🫶

🌸 Preamble 🌸

the vibes section. the "why are we doing this" section. here she is:

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.

okay so the whole point: most licenses take your freedom, this one guarantees it. also note the throwaway about the GNU Library General Public License covering some other FSF software instead — don't forget that, iykyk 💜

       When we speak of free software, we are referring to freedom, not
       price.  Our General Public Licenses are designed to make sure that you
       have the freedom to distribute copies of free software (and charge for
       this service if you wish), that you receive source code or can get it
       if you want it, that you can change the software or use pieces of it
       in new free programs; and that you know you can do these things.

free as in freedom, not free as in free coffee. and yes you can charge for the act of distributing a copy if you want. no cap ☕

       To protect your rights, we need to make restrictions that forbid
       anyone to deny you these rights or to ask you to surrender the rights.
       These restrictions translate to certain responsibilities for you if you
       distribute copies of the software, or if you modify it.

the way that "protecting your rights" = "adding restrictions" is such a plot twist but it makes sense. it's giving legal jiu-jitsu 💀

       For example, if you distribute copies of such a program, whether
       gratis or for a fee, you must give the recipients all the rights that
       you have.  You must make sure that they, too, receive or can get the
       source code.  And you must show them these terms so they know their
       rights.

three things, every time: give them your rights, make sure they can get the source, show them these terms. gratis or fee, doesn't matter. 🔥

       We protect your rights with two steps: (1) copyright the software, and
       (2) offer you this license which gives you legal permission to copy,
       distribute and/or modify the software.

two steps, that's it: copyright it, then license it. 🎀

       Also, for each author's protection and ours, we want to make certain
       that everyone understands that there is no warranty for this free
       software.  If the software is modified by someone else and passed on, we
       want its recipients to know that what they have is not the original, so
       that any problems introduced by others will not reflect on the original
       authors' reputations.

there is no warranty. say it with me. and if someone else modded it and handed it to you, you deserve to know it's not the original, so nobody blames the og authors for someone else's chaos 😭

       Finally, any free program is threatened constantly by software
       patents.  We wish to avoid the danger that redistributors of a free
       program will individually obtain patent licenses, in effect making the
       program proprietary.  To prevent this, we have made it clear that any
       patent must be licensed for everyone's free use or not licensed at all.

patents. the final boss. the rule here is clean: a patent gets licensed for everyone's free use, or it doesn't get licensed at all. no sneaky individual patent grabs, tyvm 🙈

       The precise terms and conditions for copying, distribution and
       modification follow.

and now we get into it. deep breath bestie 🫶

🔥 GNU GENERAL PUBLIC LICENSE 🔥

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

✨ 0 ✨

       0. This License applies to any program or other work which contains
       a notice placed by the copyright holder saying it may be distributed
       under the terms of this General Public License.  The "Program", below,
       refers to any such program or work, and a "work based on the Program"
       means either the Program or any derivative work under copyright law:
       that is to say, a work containing the Program or a portion of it,
       either verbatim or with modifications and/or translated into another
       language.  (Hereinafter, translation is included without limitation in
       the term "modification".)  Each licensee is addressed as "you".

definitions time!! "Program" = the thing with the notice. "work based on the Program" = the Program itself or any derivative work under copyright law — verbatim, modified, or translated. and yes, translation counts as modification, they said so explicitly. also hi, "you" is you. hiii 👋

       Activities other than copying, distribution and modification are not
       covered by this License; they are outside its scope.  The act of
       running the Program is not restricted, and the output from the Program
       is covered only if its contents constitute a work based on the
       Program (independent of having been made by running the Program).
       Whether that is true depends on what the Program does.

running it is not restricted. huge. the output only gets caught up in this if the output itself counts as a work based on the Program — and whether that's true depends on what the Program actually does. vibe check on a per-program basis, basically 🦋

✨ 1 ✨

       1. You may copy and distribute verbatim copies of the Program's
       source code as you receive it, in any medium, provided that you
       conspicuously and appropriately publish on each copy an appropriate
       copyright notice and disclaimer of warranty; keep intact all the
       notices that refer to this License and to the absence of any warranty;
       and give any other recipients of the Program a copy of this License
       along with the Program.

       You may charge a fee for the physical act of transferring a copy, and
       you may at your option offer warranty protection in exchange for a fee.

verbatim copies? slay, go off. any medium. but conspicuously publish the copyright notice + warranty disclaimer on each copy, keep all the notices intact (license notice AND the no-warranty notice), and hand every recipient a copy of this License with the Program. don't lose the paperwork 📄✨

and yeah — you can charge a fee for the physical act of transferring a copy, and optionally sell warranty protection for a fee too. hustle respectfully 💸

✨ 2 ✨

       2. You may modify your copy or copies of the Program or any portion
       of it, thus forming a work based on the Program, and copy and
       distribute such modifications or work under the terms of Section 1
       above, provided that you also meet all of these conditions:

modding is allowed!! but section 1 still applies, and you gotta hit all of these:

           a) You must cause the modified files to carry prominent notices
           stating that you changed the files and the date of any change.
  • a) — prominent notice: "i changed these files" + the date of any change. put a timestamp on it, bestie 🕐
           b) You must cause any work that you distribute or publish, that in
           whole or in part contains or is derived from the Program or any
           part thereof, to be licensed as a whole at no charge to all third
           parties under the terms of this License.
  • b) — anything you distribute or publish that contains or derives from the Program (whole or in part) gets licensed as a whole, at no charge, to all third parties, under these terms. the whole thing. not just your bits 👑
           c) If the modified program normally reads commands interactively
           when run, you must cause it, when started running for such
           interactive use in the most ordinary way, to print or display an
           announcement including an appropriate copyright notice and a
           notice that there is no warranty (or else, saying that you provide
           a warranty) and that users may redistribute the program under
           these conditions, and telling the user how to view a copy of this
           License.  (Exception: if the Program itself is interactive but
           does not normally print such an announcement, your work based on
           the Program is not required to print an announcement.)
  • c) — if it's one of those interactive, reads-commands-when-run programs, then on the most ordinary startup it has to print/display an announcement with: an appropriate copyright notice, the no-warranty notice (or a note that you provide a warranty), that users may redistribute under these conditions, and how to view a copy of this License. and there's an exception — if the Program is interactive but doesn't normally print such an announcement, your work based on it doesn't have to either 🎀
       These requirements apply to the modified work as a whole.  If
       identifiable sections of that work are not derived from the Program,
       and can be reasonably considered independent and separate works in
       themselves, then this License, and its terms, do not apply to those
       sections when you distribute them as separate works.  But when you
       distribute the same sections as part of a whole which is a work based
       on the Program, the distribution of the whole must be on the terms of
       this License, whose permissions for other licensees extend to the
       entire whole, and thus to each and every part regardless of who wrote it.

okay this is the nuance paragraph, don't skip it: the requirements apply to the modified work as a whole. if some identifiable sections genuinely aren't derived from the Program and can reasonably be considered independent separate works, then this License doesn't apply to those when you distribute them as separate works. but the second you distribute those same sections as part of a whole that's a work based on the Program, the whole distribution has to be on these terms — and the permissions for other licensees stretch to the entire whole, every single part, no matter who wrote it. no vibes-based carve-outs 💀

       Thus, it is not the intent of this section to claim rights or contest
       your rights to work written entirely by you; rather, the intent is to
       exercise the right to control the distribution of derivative or
       collective works based on the Program.

to be clear (they said it, not me): this section is not trying to claim rights over or contest your rights to stuff you wrote entirely yourself. the intent is controlling distribution of derivative or collective works based on the Program. read it right, bestie 🌸

       In addition, mere aggregation of another work not based on the Program
       with the Program (or with a work based on the Program) on a volume of
       a storage or distribution medium does not bring the other work under
       the scope of this License.

mere aggregation on a storage/distribution medium ≠ pulling the other work under this License. just because they're on the same disk doesn't mean they're dating 💅

✨ 3 ✨

       3. You may copy and distribute the Program (or a work based on it,
       under Section 2) in object code or executable form under the terms of
       Sections 1 and 2 above provided that you also do one of the following:

object code / executable distribution is fine under Sections 1 and 2 — if you also do one of these three:

           a) Accompany it with the complete corresponding machine-readable
           source code, which must be distributed under the terms of Sections
           1 and 2 above on a medium customarily used for software interchange; or,
  • a) — ship the complete corresponding machine-readable source code with it, distributed under Sections 1 and 2 on a medium customarily used for software interchange. bring the source, basically 🧚
           b) Accompany it with a written offer, valid for at least three
           years, to give any third party, for a charge no more than your
           cost of physically performing source distribution, a complete
           machine-readable copy of the corresponding source code, to be
           distributed under the terms of Sections 1 and 2 above on a medium
           customarily used for software interchange; or,
  • b) — or a written offer, valid at least three years, to give any third party a complete machine-readable copy of the corresponding source code, for a charge no more than your cost of physically performing source distribution, distributed under Sections 1 and 2 on a medium customarily used for software interchange. three years minimum, cap the charge at cost. write it down ✍️
           c) Accompany it with the information you received as to the offer
           to distribute corresponding source code.  (This alternative is
           allowed only for noncommercial distribution and only if you
           received the program in object code or executable form with such
           an offer, in accord with Subsection b above.)
  • c) — or pass along the info you received about the offer to distribute corresponding source code. head's up though: this one's only for noncommercial distribution, and only if you got the program in object code or executable form with such an offer, in accord with Subsection b) above. read the fine print fr fr 🙈
       The source code for a work means the preferred form of the work for
       making modifications to it.  For an executable work, complete source
       code means all the source code for all modules it contains, plus any
       associated interface definition files, plus the scripts used to
       control compilation and installation of the executable.  However, as a
       special exception, the source code distributed need not include
       anything that is normally distributed (in either source or binary
       form) with the major components (compiler, kernel, and so on) of the
       operating system on which the executable runs, unless that component
       itself accompanies the executable.

defining "source code" properly: the preferred form of the work for making modifications to it. for an executable, "complete source code" = all source for all modules it contains + any associated interface definition files + the scripts used to control compilation and installation of the executable. that's the full package 📦

special exception though: you don't need to include anything normally distributed (source or binary) with the major components — compiler, kernel, and so on — of the OS the executable runs on... unless that component itself accompanies the executable. read that twice 🔍

       If distribution of executable or object code is made by offering
       access to copy from a designated place, then offering equivalent
       access to copy the source code from the same place counts as
       distribution of the source code, even though third parties are not
       compelled to copy the source along with the object code.

handy shortcut: if you distribute the executable/object code by offering access to copy from a designated place, then offering equivalent access to copy the source from the same place counts as distributing the source. even though third parties aren't compelled to copy the source along with the object code. convenient! ✨

✨ 4 ✨

       4. You may not copy, modify, sublicense, or distribute the Program
       except as expressly provided under this License.  Any attempt
       otherwise to copy, modify, sublicense or distribute the Program is
       void, and will automatically terminate your rights under this License.
       However, parties who have received copies, or rights, from you under
       this License will not have their licenses terminated so long as such
       parties remain in full compliance.

the serious one ⚠️ no copying, modifying, sublicensing, or distributing the Program except as expressly provided under this License. any attempt otherwise is void and automatically terminates your rights under this License. that's not a warning, that's the mechanism. 😭

the good news: parties who received copies or rights from you under this License don't get their licenses terminated — as long as they stay in full compliance. your mess doesn't nuke your friends' licenses 🫶

✨ 5 ✨

       5. You are not required to accept this License, since you have not
       signed it.  However, nothing else grants you permission to modify or
       distribute the Program or its derivative works.  These actions are
       prohibited by law if you do not accept this License.  Therefore, by
       modifying or distributing the Program (or any work based on the
       Program), you indicate your acceptance of this License to do so, and
       all its terms and conditions for copying, distributing or modifying
       the Program or works based on it.

nobody's forcing you to accept it — you didn't sign anything. but nothing else gives you permission to modify or distribute the Program or its derivative works, and those actions are prohibited by law if you don't accept. so the moment you modify or distribute the Program (or any work based on it), you're indicating acceptance of this License and all its terms for copying, distributing, or modifying it. consent via action, basically 🤝

✨ 6 ✨

       6. Each time you redistribute the Program (or any work based on the
       Program), the recipient automatically receives a license from the
       original licensor to copy, distribute or modify the Program subject to
       these terms and conditions.  You may not impose any further
       restrictions on the recipients' exercise of the rights granted herein.
       You are not responsible for enforcing compliance by third parties to
       this License.

every single time you redistribute the Program (or a work based on it), the recipient automatically gets a license from the original licensor to copy, distribute or modify it under these terms. automatic. no paperwork needed 🎀

and you may not impose any further restrictions on the recipients exercising the rights granted here — that's the whole point, no extra locks on the door. last bit: you are not responsible for enforcing third parties' compliance with this License. not your job, not your problem, go live your life 💜

7. Okay so boom — if a court judgment, or a patent infringement allegation, or literally any other reason (and nope, not just patent issues, bestie) imposes conditions on you — whether by court order, by agreement, or otherwise — and those conditions contradict the conditions of this License? That does not excuse you from the conditions of this License. Periodt. 💅 If you can't distribute in a way that satisfies your obligations under this License and any other pertinent obligations at the same time, then as a consequence you may not distribute the Program at all. Example time: if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. 😭

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances.

And a little vibe check on intent, because this matters: it is not the purpose of this section to induce you to infringe any patents or other property right claims, or to contest validity of any such claims. The section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it's up to the author/donor to decide if he or she is willing to distribute software through any other system, and a licensee cannot impose that choice. ✨ This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries — so distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 🌍 iykyk.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Those new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. New drop, same vibes. 🦋

Each version gets a distinguishing version number. If the Program specifies a version number of this License that applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. Pick your fighter. 💖

10. Wanna fold parts of the Program into other free programs whose distribution conditions are different? Write to the author and ask for permission. For software copyrighted by the Free Software Foundation, write to the Free Software Foundation; they sometimes make exceptions for this. And the decision is guided by two goals, iconic behavior honestly: preserving the free status of all derivatives of the free software, and promoting the sharing and reuse of software generally. 🌈

💀 NO WARRANTY 💀

11. What it says on the tin, and we're doing it in caps because it's serious: BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. Except when otherwise stated in writing, the copyright holders and/or other parties provide the Program "AS IS" without warranty of any kind, either expressed or implied — including, but not limited to, the implied warranties of MERCHANTABILITY and FITNESS FOR A PARTICULAR PURPOSE. The entire risk as to the quality and performance of the Program is with you. Should the Program prove defective, you assume the cost of all necessary servicing, repair or correction. No cap, that's the deal. 🫶

😭 NO LIABILITY 😭

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING will any copyright holder, or any other party who may modify and/or redistribute the Program as permitted above, be liable to you for damages — including any general, special, incidental or consequential damages arising out of the use or inability to use the Program (including but not limited to loss of data or data being rendered inaccurate, or losses sustained by you or third parties, or a failure of the Program to operate with any other programs) — even if such holder or other party has been advised of the possibility of such damages. 💀

🏁 END OF TERMS AND CONDITIONS 🏁

✨ How to Apply These Terms to Your New Programs ✨

So you're building something new and you want it to be of the greatest possible use to the public? Slay. The best way to achieve this is to make it free software which everyone can redistribute and change under these terms. 🎀

To do so, attach the following notices to the program. It's safest to attach them to the start of each source file to most effectively convey the exclusion of warranty, and each file should have at least the "copyright" line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year>  <name of author>

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

Also add information on how to contact you by electronic and paper mail. 📬

If the program is interactive, make it output a short notice like this when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year  name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.

The hypothetical commands show w' and show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than show w' and show c' — they could even be mouse-clicks or menu items — whatever suits your program. 🖱️

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here's a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.

<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License. 👑

🔥 eXosip2 (5.3.0) - 2021-11-22 🔥

  • socket error management got a glow-up: rewritten in order to apply them to all pending ICT and NICT transactions — with previous code, some transactions won't see the transport-error and will fail with unnecessary delay. 😤
  • add time information in cb_xixt_kill_transaction callback for debugging 🔍
  • eXosip_lock will now include read on sockets
  • [TLS] allow to accept wildcard with a new bit in tls_verify_client_certificate
  • [TLS] disable loading OS certifiate with a new bit in tls_verify_client_certificate (that spelling is the original's, love it, keeping it 💅)
  • [TLS] I beleive there is no reason to cut packet in 500 bytes chunks on ios (again: their spelling, their truth ✨)
  • [EXOSIP_OPT_SET_CONTACT_DIALOG_EXTRA_PARAMS] new option to set Contact parameters in request/answers dialogs
  • [AMSIP_OPTION_SET_SIP_INSTANCE] allow any value inside +sip.instance instead of only urn:uuid
  • [epoll] fix eXosip_event_wait when using epoll implementation where events are distributed in the next eXosip_event_wait call

🦋 eXosip2 (5.2.1) - 2020-05-21 🦋

  • [ENABLE_MAIN_SOCKET] fix epoll mechanism for server socket with TCP and TLS
  • [crash] check scheme upon processing 3xx
  • [ssl] fix to be compatible with libressl
  • [ssl] https://savannah.nongnu.org/patch/?10046 compatibility with openssl below 1.1.0
  • fix when Content-Type indicates application/sdp, but there is no body
  • [TLS] modify the code for TLS validation in order to improve logs and details on the connection
  • use time_t instead of int for r_retry_after_delay variable [fix 1367a34ca commited on March 1st]
  • eXosip_default_action will return OSIP_RETRY_LIMIT when limit is reached
  • make sure to obey the Retry-After header from REGISTER reply
  • use newer osip_timersub MACRO
  • [bug#60024] fix openssl usage to always use callback mode for private key password, even when missing
  • eXosip_reset_transports was not effective any more since [5.1.2] [commit 705643fa 2020-07-07] [do not use unless you understand it] — bestie, that bracketed warning is doing a LOT of heavy lifting here 😭
  • [windows] a HANDLE is leaked when loading trusted certificates
  • dp layer: handle WSAEMSGSIZE when buffer is too short for complete incoming messag
  • cleaner code to retreive an SDP from a SIP message
  • fix crash when ENABLE_MAIN_SOCKET is defined and epoll is used

🌸 eXosip2 (5.2.0) - 2020-11-10 🌸

  • fix memory and socket leak [major] [affected TCP, TLS, UDP: since 5.1.2, need update asap] — genuinely, update asap, this one's not a drill 🚨
  • fix to make sure a non yet established TLS descriptor with read descriptor set will be processed when no outgoing transaction is in a state to handle it [since 5.1.2]
  • fix SRV rotation for TLS [was rotating TCP records instead of TLS] [since 5.1.2]
  • fix duplicate packets for TCP and TLS when several outgoing NICT are happening at the same time [since 5.1.2]
  • add outbound proxy parameter in sip_monitor tool
  • ABI update: modification of "eXosip_tls_ctx_t" — extend the structure to set:
    • cipher list
    • add TLS openssl flags (to disable TLSv1, TLSv1.1, etc...)
    • add DTLS openssl flags (to disable DTLSv1, etc...)

🎀 eXosip2 (5.1.3) - 2020-08-25

  • EXOSIP_OPT_FORCE_CONNECTIONREUSE — brand new option bestie, it forces reuse of an already-established socket for ACK and dialog messages 💅
  • tls — fixed building the DH parameter with 5.1.2 and openssl < 1.1.0

✨ eXosip2 (5.1.2) - 2020-08-20

  • tls — now uses RFC 5114 dh param at 2048 bits size 🌸
  • tls — uses 2048 bits for ephemeral RSA key generation
  • tls — uses SSL_OP_NO_COMPRESSION to make sure it's actually disabled
  • tls — uses SSL_OP_NO_TICKET to disable ticket
  • tls — uses the HIGH:!COMPLEMENTOFDEFAULT:!kRSA:!PSK:!SRP cipher list for higher security and fewer ciphers 🔥
  • fixed a possible race condition in the sample code [sip_reg and sip_monitor]
  • new format style using clang-format
  • reduced and rewrote the logs for readability
  • fixed the broken epoll implementation. DO NOT USE 5.1.1 with epoll 💀
  • rewrite of UDP/TCP/TLS (and DTLS, untested) for both select and epoll mode. Complete rewrite of socket (c-ares and UDP/TCP/TLS) in order to accelerate socket establishment, and to correctly handle socket failure. The change also helps recover faster after a socket failure and switch to the next SRV record available — that last feature was previously broken, ngl
  • Fix NAPTR/SRV on windows when CARES is not used. (not advised) 🙈
  • ACK sent out of transaction with no existing connection may be sent later. (TCP/TLS)
  • Upon TLS loss, try to use domain or NAPTR SNI when the TLS connection is not initiated by an outgoing transaction.
  • sip_monitor — new tool to monitor sip service 👑
  • add support for authentication using SHA-256 (openssl required)
  • only use the first supported proposed authentication when the same realm is used
  • fix: upon UDP errors, like ICMP, buffer size may reach abnormal values (avoid useless reallocation)

🦋 eXosip2 (5.1.1) - 2020-01-16

  • new API — generate random string (low entropy, only hexa):
int eXosip_hexa_generate_random(char *val, int val_size);
  • generate random string (high entropy when compiled with openssl):
int eXosip_byte_generate_random(char *val, int val_size)
  • provide more entropy with eXosip_byte_generate_random (with openssl when available) ✨
  • fix TLS security issue reported by Alexander Traud regarding hostname validation when using NAPTR/SRV 🔒
  • add support for epoll (detected by configured) // becomes the default on linux platforms with autotools
  • fix bug #56839: The cnonce should not be static -this is identified as replay attack by some services-.
  • fix tcp and tls connection failure detection (accelerate error detection and recovery)
  • fix: fixed a crash with DTLS

💖 eXosip2 (5.1.0) - 2019-03-27

  • minor API update — API parameter change: eXosip_call_build_ack / eXosip_call_send_ack API to use tid instead of did as parameter.
  • new API — add an API to insert one extra header in BYE:
int eXosip_call_terminate_with_header(struct eXosip_t *excontext, int cid, int did, const char *header_name, const char *header_value);
void eXosip_dnsutils_release(struct osip_naptr *naptr_record);

which is required after usage of eXosip_dnsutils_naptr. 🫶

  • new OPTION — EXOSIP_OPT_SET_SESSIONTIMERS_FORCE option to force session timer to be used when the remote side does not support it.
  • structure change — new param in eXosip_tls_credentials_t for pinning: "public_key_pinned". A file with the expected public key of server. If you use eXosip_tls_ctx_t / eXosip_tls_credentials_t / EXOSIP_OPT_SET_TLS_CERTIFICATES_INFO, you need to recompile 😭
  • fix processing response out of transaction. (avoid incorrect logs and extra work)
  • fix https://savannah.nongnu.org/bugs/?54628 where ACK was only retransmitted for initial outgoing INVITE.
    • fix: retransmit ACK for both initial INVITE and re-INVITE.
    • fix: retransmit ACK for 2xx from forking (with a BYE) even if call does not exist.
    • ACK for "old transaction" within the established dialog won't be retransmitted because the parameter only hold the latest ACK.
  • fix bug report: https://savannah.nongnu.org/bugs/index.php?54624
    • another patch to fix more issue related to cseq & PRACK.
    • The newer code better handle forking use-case with PRACK.
    • The newer code better handle several 1xx from same user.
  • fix bug report: https://savannah.nongnu.org/bugs/index.php?54624 cseq wasn't increasing after a PRACK.
  • improve portability code, detection of headers, windows compilation detection, sockaddr_storage was not correctly defined.
  • fix udp layer: set ipbuf before using it.
  • fix: allow socket descriptor to be 0 (posix requirement).
  • fix: compile with any openssl version.
  • allow compilation with OPENSSL_NO_DH, OPENSSL_NO_RSA, OPENSSL_NO_ECDH and/or OPENSSL_NO_DEPRECATED.
  • remove old windows specific RSA obsolete code.
  • add in eXtl_tls.c some explanations on usage of TLS with eXosip2. READ THEM. 👀
  • improve reliability for naptr/srv lookup (but still a short time).
  • fix/improve _eXosip_mark_registration_expired: it was working correctly only if registration had previously failed.
  • fix: attach call/dialog to CANCEL transaction (so EXOSIP_CALL_MESSAGE_ANSWERED will be received instead of EXOSIP_MESSAGE_ANSWERED).
  • windows: fix DnsQuery to use UTF8 even if compiled without UNICODE (not applicable if you use c-ares).
  • windows: add ENUM capability and improve NAPTR/SRV record (not applicable if you use c-ares).
  • windows: you should use c-ares AND you should compile with UNICODE. (much better) 💅
  • add ability to define a dnsserver when doing NAPTR and SRV record (c-ares only).
  • format of domain string for "eXosip_dnsutils_naptr" is "domain.com!+AUS|IP_DNSSERVER".
  • fix for on android, DNS are not available any more (restricted access) (c-ares only).
  • add support ENUM and regex for res_query API (not applicable if you use c-ares).
  • sync with newer osip: use newer osip_naptr & osip_srv_record structures to hold ENUM sip result and improvements to retrieve (and release) it via eXosip_dnsutils_naptr and eXosip_dnsutils_release APIs.
  • TLS improvements: simplify client and server config, add ECDH cipher suite if missing, password for private key is optional, add support for public key pinning. 🔐
  • improve to report EXOSIP_CALL_NOANSWER upon transport error for INVITE for faster detection.
  • fix possible memory leak for X509 server certificate.
  • fix crash if dialog has been already closed between 200ok and a received BYE.
  • improve windows pipe replacement (use a free allocated port automatically).
  • fix to optimize detection of TCP or TLS establishment, fix to optimize sending REGISTER after establishment.
  • patch for call transfer to keep dialog after BYE, in order to be able to handle incoming/outgoing NOTIFY within calls after BYE.
  • handle incoming UPDATE from alternative dialogs in early dialog mode.
  • fix to reject any NOTIFY without established dialog coming later than 64 seconds after initial SUBSCRIBE.
  • After a NAPTR query, some DNS server returns SUCCESS without NAPTR answers. In such use-case, fallback to manual SRV records.
  • add SOCK_CLOEXEC option to sockets // add missing SO_KEEPALIVE options on TLS socket.
  • EXOSIP_OPT_ENABLE_IPV6 now support 0 (ipv4 only), 1 (ipv6 only) and 2 (ipv4 OR ipv6). With option 2, choice is made based on DNS and the stack can fallback between IPv4 and IPv6. 🌈
  • fix possible memory leak when using wrong tid for eXosip_insubscription_send_answer.
  • fix possible memory leak upon allocation error.
  • fix leak upon syntax error in parameters provided for PUBLISH.
  • fix leak upon syntax error in parameters provided for REGISTER.
  • increase size of proto_ifs for IPv6 local address.
  • RFC 2617 erratum: Errata ID: 1649 (minor issue).
  • _exosip_isipv4addr: fix checking IPv4 address (minor issue).
  • other minor updates.

⭐ eXosip2 (5.0.0)

  • major API update — add a new parameter to eXosip_call_build_prack in order to create the PRACK for this specific response and not for the latest.
  • major API update — removal of eX_refer.h API. REFER are now handled with subscriptions APIs.
    • eXosip_refer_build_request removed
    • eXosip_refer_send_request removed
  • major API update — subscription now handle both SUBSCRIBE and REFER with the same APIs:
eXosip_subscription_build_initial_refer ADDED
eXosip_subscribe_build_initial_request renamed eXosip_subscription_build_initial_subscribe
eXosip_subscribe_send_initial_request renamed eXosip_subscription_send_initial_request
eXosip_subscribe_build_refresh_request renamed eXosip_subscription_build_refresh_request
eXosip_subscribe_send_refresh_request renamed eXosip_subscription_send_refresh_request
eXosip_subscribe_remove renamed eXosip_subscription_remove

and EXOSIP_IN_SUBSCRIPTION_* and EXOSIP_SUBSCRIPTION_* events may now relate to REFER subscription.

  • major API change — eXosip_automatic_refresh is obsolete and has been removed. Only use eXosip_automatic_action instead 🙅
  • API update:
    • eXosip_options_send_request returns a positive transaction id (tid) on success.
    • eXosip_publish returns a positive transaction id (tid) on success.
    • note: eXosip_message_send_request was already returning the transaction id (tid) on success.
  • new API options:
    • EXOSIP_OPT_REMOVE_PREROUTESET: to keep Route Set
    • EXOSIP_OPT_SET_SIP_INSTANCE: define +sip.instance parameter in Contact headers
    • EXOSIP_OPT_ENABLE_USE_EPHEMERAL_PORT: option to use/not use ephemeral port in Contact.
    • EXOSIP_OPT_ENABLE_REUSE_TCP_PORT: option to reuse port.
    • EXOSIP_OPT_AUTO_MASQUERADE_CONTACT: option to enable automatic masquerading for Contact headers.
    • EXOSIP_OPT_UDP_LEARN_PORT: obsolete and will be removed in the future.
    • EXOSIP_OPT_SET_DEFAULT_CONTACT_DISPLAYNAME: define a display name to be added in Contact headers
  • new API options: (high load traffic use-case: DO NOT USE FOR COMMON USAGE) 💀
    • EXOSIP_OPT_SET_MAX_MESSAGE_TO_READ: set the number of message to read at once for each network processing.
    • EXOSIP_OPT_SET_MAX_READ_TIMEOUT: set the period in nano seconds during we read for sip message.
    • EXOSIP_OPT_GET_STATISTICS: retrieve numerous statistics.
  • rewrite/update autotools and ./configure options
--enable-pthread=[autodetect|force]
  autodetect POSIX threads or force -DHAVE_PTHREAD [default=autodetect]
--enable-semaphore=[autodetect|semaphore|sysv]
  select your prefered semaphore [default=autodetect].
  • fix the selection of the Contact header for 3xx — it defaults to a tel/sip/sips one with any transport 🫶
  • keep the call context around long enough to actually handle redirection, bestie
  • fix a race condition for processing SRV results (not likely to happen, but like… it could)
  • fix the bug when reading a SIP message longer than 8000 over UDP and TLS 😭
  • improve eXosip_add_authentication_info so it stops creating duplicate credentials
  • if a SUBSCRIBE gets rejected, the context gets released automatically now, periodt
  • add failover after a DNS failure ✨
  • fall back to SRV even if we get a NOTFOUND reply for NAPTR
  • fix the route set with a strict router
  • rename the usage of -DHAVE_CARES_H into -DHAVE_ARES_H, which is the real name of the header, iykyk
  • remove warnings, mostly the ones from the socket API (getnameinfo/bind/accept/recv/connect/sendto)
  • rewrite all the loops using an iterator for better performance (super useful for high load traffic 🔥)
  • rewrite Via and Contact management: both now contain the IP of the real network interface instead of the default one
  • improve NAPTR failover, it's more reliable now // and add failover for 503 answers
  • improve the interval that forces a REGISTER refresh on network error and failover
  • improve TCP socket management
  • add a callback to simplify/optimize/accelerate the usage of wakelocks in an android application using exosip2 💅
  • improve TLS, add TLSv1.1, TLSv1.2, disable the weak cipher (FREAK) and enable ECDHE cipher 🔐
  • add support for the SNI tls extension (openssl 1.0.2)
  • add try/except on windows to catch a possibly missing qwave (windows server)
  • implement a timeout (32 seconds) for establishing a TCP and TLS connection
  • if a connection is failing, report the failure asap
  • fix a memory leak in eXosip_call_get_referto
  • remove the extra connect on the socket for TCP and TLS (not allowed for a tcp stream, no cap)
  • fix it so an INVITE retransmission with the same branch, received after the original INVITE was replied, is correctly discarded
  • add WSACleanup for each WSAStartup call (windows)
  • do not include contact in BYE and CANCEL
  • fix it to use sips when appropriate (in Contact)
  • fix it to avoid handling a negative content-length 💀
  • do not start naptr for incoming transactions
  • fix the bug when rseq is empty but exists
  • add support for QOS on windows
  • improve connection handling / failure detection and the keep alive options, in TLS, TCP, UDP
  • update the static IDs (cid/did/rid/pid) to use the range from 0 to INT_MAX so collisions stop being a thing
  • other minor updates.

eXosip2 (4.1.0) 🎀

  • improve the timer and use UPDATE if it's advertised, INVITE otherwise
  • improve PRACK support
  • option to disable the automatic BYE answer
  • option to enable/disable IPv6 per eXosip_t instance
  • option to disable the DNS cache
  • improve network support for several eXosip_t instances
    • keepalive setting is per instance
    • ipv4/ipv6 setting is per instance
    • improve the network setting to avoid conflict upon transport change
  • fix tcp and tls connect() for slow connections
  • use TCP_NODELAY on more platforms
  • use the Authorization header for 401 // simplify the authentication code
  • minor expires improvements for REGISTER
  • copy call-info over a SUBSCRIBE refresh
  • allow more TLS errors if verification is disabled
  • fix it if there's NO NAPTR available
  • add support for Windows Phone 8
  • fix it to use the cache for TCP and TLS
  • fix possible leaks on implementation errors
  • add TSC experimental support

eXosip2 (4.0.0) 🦋

  • modify the configuration APIs to use eXosip_set_option
  • fix the bug: do not create a new PRACK if it already exists for an answer
  • update to the latest osip // test time compensation for android
  • use an ephemeral port in the standard TCP and TLS version
  • return the tid number so we can match the response event
  • use a system independent time for osip_gettimeofday on the unix platform
  • major API update: several "struct eXosip_t" can be handled at the same time. This can be used to have several transport layers running at the same time 🫶
  • many tiny other changes

eXosip2 (3.6.0) 🌸

  • use the optional c-ares DNS library for non blocking DNS access, plus improvements over DNS operations like NAPTR and SRV records
  • again, so many minor changes/fixes/improvements, sorry for not being able to have a history here… the git on savannah will bring you all the details!

eXosip2 (3.5.0) 💖

  • iphone with TCP/TLS background support
  • android support
  • a lot of minor changes/fixes/improvements, sorry for not being able to have a history here…

eXosip2 (3.4.0) ✨

  • modification to allow using the "windows certificate store" for TLS
  • handle keep alive for TCP/TLS
  • fix when receiving additional CRLF on a reliable transport
  • modification to allow a non-blocking socket for reliable transport (TLS/TCP)
  • fix the tag issue with an application where the tag is missing
  • fix compilation for mingw
  • fix the Contact header in a request within a dialog for non-udp protocol
  • fix some DNS issue with vista?
  • remove the 481 auto answer for an unsolicited NOTIFY
  • fix the static id range
  • initial code for TCP fragmentation
  • osip_list prototypes and warnings fix
  • fix transport matching for redirection using a transport other than udp

eXosip2 (3.3.0) 🧚

  • fix when 200ok includes a contact with an empty line parameter
  • fix for a replaces header longer than 256 char
  • fix SRV record with more than 10 answers
  • sort SRV record
  • option to disable NAPTR requests

eXosip2 (3.2.0) 🍓

  • improve TLS support and add an API for ssl information & files
  • return a new error code for all API
  • remove automatic answers to PRACK (it must be done in the application now)
  • remove automatically outgoing non established subscriptions

eXosip2 (3.1.0) 👑

  • AKA authentication
  • improve compliance & flexibility

eXosip2 (3.0.4) 💜

  • fix building SUBSCRIBE refresh
  • fix a compliance issue with the refer-to to-tag/from-tag parameters
  • fix the bug for retransmissions or ACK with a proxy that resolves to several IP
  • handle the "expires" parameter to update the registration interval
  • handle the "expires" parameter to update the publication interval
  • handle automatically publish refresh, and some error codes (423)

eXosip2 (3.0.3) 🌈

  • add TLS support
  • rewrite transport layer
  • add the line= parameter in Contact headers for registrations
  • a few changes related to interop. issues
  • add missing *_REQUESTFAILURE events on no answer
  • update the registration interval when the Expires header is in 200ok

eXosip2 (3.0.2) ⭐

  • fix the call transfer issue with the "Replaces" header
  • allow build/run eXosip in a non-threaded model (without -DOSIP_MT)
  • initial support for ucos
  • add support for qop authentication
  • remove the registration context immediately upon eXosip_register_remove
  • TCP: fix missing Contact in the sent INVITE
  • TCP: fix missing "transport" in Contact for answers within a dialog
  • TCP: fix possible race conditions

eXosip2 (3.0.1) 🎀

  • add Windows CE support with Visual Studio 2005 (WM5.0, PocketPC 2003/2005, Smartphone)
  • update to osip2-3.0.1
  • add SRV record capabilities
  • add new OPTIONS: do not send 101, remove pre-route set from message

eXosip2 (2.2.3) 💅

  • announce NOTIFY answers to the application
  • fix authentication bugs from the previous patch
  • fix a TCP bug
  • fix using code 699

eXosip2 (2.2.2) 🦋

  • new version synchronized with osip2
  • total rewrite of eXosip
    • -> new API for more flexibility
    • -> media negotiation must now be handled outside of eXosip2

eXosip (0.9.1) 🌸

  • add publish support through a nice API

eXosip (0.9.0) 💖

  • improve presence support (busy, away, onthephone…)
  • new eXosip_automatic_refresh() to refresh SUBSCRIBE and REGISTER
  • fix dialog establishment when receiving NOTIFYs
  • this ChangeLog has not been updated seriously… many changes
  • have been done but they don't appear here. Sorry.
  • status of libexosip:
    • call transfer : OK
    • redirection of calls (3XX) : OK
    • SUB/NOTIFY for presence : nearly OK (usable)
    • authenthication (REGISTER and INVITE only) : ok

eXosip (0.8.0) ✨

  • fix processing of 180 Ringing?
  • fix the bug when BYE is processed before a 2xx for INVITE

eXosip (0.7.7) 🧚

  • memory leaks
  • tiny bugs, code clean-up

eXosip (0.7.6) 🍓

  • fix the bug when the 1st proxy is using strict routing
  • support for IPv4 and IPv6
  • do not send 180 Ringing any more on new INVITEs
  • close correctly rtp streams in josua
  • improve the eXosip_event_wait method
  • performance updated on win32 for event handling

eXosip (0.7.5) 👑

  • small improvements for josua
  • patch for IPv6 (uncomplete)
  • patch for authentication
  • improve the configure.in file
  • allow a fancy reason phrase in a SIP answer
  • allow NAT traversal (firewall IP in SDP packet)

eXosip (0.7.3) 💜

  • warning fix
  • support for multiple registrations
  • support for authentifications for REGISTER

eXosip (0.7.2) 🌈

  • add RTP support with the common ucl library
  • fix some memory leak
  • improve the facility to change the local_sdp_port
  • add an event when the ACK for 2xx is received

eXosip (0.7.1) ⭐

  • rewrite of header files and new directory architecture
  • support for INFO and OPTIONS within calls
  • support for AUDIO

eXosip (0.6.3) 🎀

  • use of the event oriented interface in josua

eXosip (0.6.2) 🦋

  • new Event oriented interface with applications
  • support for both MSN or compliant UAs
  • SUBSCRIBE/NOTIFY for SIMPLE support
  • script for adding/updating subscribers (eXosip_addsubscriber.sh)

eXosip (0.6.1) 🌸

  • INVITE, CANCEL, BYE, REGISTER, MESSAGE, REFER
  • script for adding/updating contact (eXosip_addfreind.sh)
  • script for adding/updating identity (eXosip_addidentity.sh)
  • NCURSES interface
  • options for current session

okay bestie that's literally the whole history, from 0.6.1 all the way up to the big 5.3.0 era, and you ate every single line of it 💅 this whole glow-up is from Version 5.3.0, dated Thu May 18 2023 — go off, eXosip2_license(3) 🫶✨

📦 where this page comes from