asterisk users - Dec 2017 - Explain how to maintain a compiled from source Asterisk instance ?

Hello,

When compiling Asterisk from source, the classical ./configure, make and
make install commands are issued.


If a vulnerabilty is found within Asterisk code, then Asterisk source code
is patched and depending on what files were touched parts or all of above
commands need to be re-issued.

What should be done for Asterisk runtime dependencies ?

Which of the following sentences is or are correct ?

1. All Asterisk runtime dependencies are delivered as .so files. Is this
correct ?
2. I don't need to re-configure, re-compile or even re-start asterisk when
a such .so file is updated
3. Script install_prereq gives an approximate list of both build and
runtime dependencies.

Best regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20171208/6a1647ca/attachment.html>

On Fri, Dec 8, 2017 at 8:08 AM, Olivier <oza.4h07 at gmail.com> wrote:
> Hello,
>
> When compiling Asterisk from source, the classical ./configure, make and
> make install commands are issued.
>
>
> If a vulnerabilty is found within Asterisk code, then Asterisk source code
> is patched and depending on what files were touched parts or all of above
> commands need to be re-issued.
>
> What should be done for Asterisk runtime dependencies ?
>
> Which of the following sentences is or are correct ?
>
> 1. All Asterisk runtime dependencies are delivered as .so files. Is this
> correct ?
>
Generally, yes but not delivered by the Asterisk team of course.  There may
be exceptions such as libsrtp.  Some older distributions only provide an
outdated version so we recommend that you compile and install it yourself
from source.

> 2. I don't need to re-configure, re-compile or even re-start asterisk
when
> a such .so file is updated
>
This really depends on the nature of the change.  Generally you don't need
to re-configure or re-compile but if the dependent library changed some
public API that clients like us rely on, asterisk may behave very badly if
if the steps aren't re-run.  As for re-start, you do need to re-start.  The
operating system takes care of loading dependent libraries that aren't
actually asterisk modules and they are usually held in memory until the
process using them ends.  If they weren't and you did a package update to
replace a shared library, every process using it would crash.

> 3. Script install_prereq gives an approximate list of both build and
> runtime dependencies.
>
True.


>
> Best regards
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> Check out the new Asterisk community forum at: https://community.asterisk.
> org/
>
> New to Asterisk? Start here:
>       https://wiki.asterisk.org/wiki/display/AST/Getting+Started
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>


-- 
George Joseph
Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20171208/9ec71228/attachment.html>

On Fri, Dec 08, 2017 at 04:08:02PM +0100, Olivier wrote:
> Hello,
> 
> When compiling Asterisk from source, the classical ./configure, make and
> make install commands are issued.
> 
> 
> If a vulnerabilty is found within Asterisk code, then Asterisk source code
> is patched and depending on what files were touched parts or all of above
> commands need to be re-issued.
> 
> What should be done for Asterisk runtime dependencies ?
> 
> Which of the following sentences is or are correct ?
> 
> 1. All Asterisk runtime dependencies are delivered as .so files. Is this
> correct ?
In standard Linux distributions, yes.
> 2. I don't need to re-configure, re-compile or even re-start asterisk
when
> a such .so file is updated
Hopefully, not reconfigure / recompile. Generally on properly-maintained
distributions those libraries will change their name (SONAME) if they
have non backward-compatible changes. In such a case you need to
rebuild. This is why there's a number after the .so .

As mentioned before, you need to restart, because otherwise you still
use the original version of the library.

-- 
               Tzafrir Cohen
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com