wardmundy - any chance of an 11.13.0 at some point?
cd /root
wget http://pbxinaflash.com/upgrade-asterisk11-piaf.tar.gz
tar zxvf upgrade-asterisk11-piaf.tar.gz
rm upgrade-asterisk11-piaf.tar.gz
./upgrade-asterisk-piaf
what are the advantages to this update ?
Any chance of an upgrade to Asterisk 12 w/PIAF coming soon?
drwxr-xr-x 29 root root 4096 Dec 4 18:52 asterisk
drwxr-xr-x 2 1000 1000 4096 Dec 4 18:59 asterisk-flite
drwxr-xr-x 6 1000 1000 4096 Dec 4 18:59 asterisk-perl-0.10
... ...
tar (child): asterisk: Cannot read: Is a directory
tar (child): At beginning of tape, quitting now
tar (child): Error is not recoverable: exiting now
gzip: stdin: unexpected end of file
tar: Child returned status 2
tar: Error is not recoverable: exiting now
11.16.0 is out from the Asterisk folks.
2015-02-06 Asterisk Development Team <[email protected]>
* Asterisk 11.16.0 Released.
2015-01-30 Asterisk Development Team <[email protected]>
* Asterisk 11.16.0-rc1 Released.
2015-01-30 16:55 +0000 [r431423-431472] Mark Michelson
* main/pbx.c: Backport memory leak fix in pbx.c from branch 13
revision 431468
* channels/chan_sip.c: Use SIPS URIs in Contact headers when
appropriate. RFC 3261 sections 8.1.1.8 and 12.1.1 dictate
specific scenarios when we are required to use SIPS URIs in
Contact headers. Asterisk's non-compliance with this could
actually cause calls to get dropped when communicating with
clients that are strict about checking the Contact header. Both
of the SIP stacks in Asterisk suffered from this issue. This
changeset corrects the behavior in chan_sip. ASTERISK-24646
#close Reported by Stephan Eisvogel Review:
https://reviewboard.asterisk.org/r/4346
2015-01-29 12:08 +0000 [r431384] Joshua Colp
* res/res_rtp_asterisk.c: res_rtp_asterisk: Fix DTLS when used with
OpenSSL 1.0.1k A recent security fix for OpenSSL broke DTLS
negotiation for many applications. This was caused by read ahead
not being enabled when it should be. While a commit has gone into
OpenSSL to force read ahead on for DTLS it may take some time for
a release to be made and the change to be present in
distributions (if at all). As enabling read ahead is a simple one
line change this commit does that and fixes the issue.
ASTERISK-24711 #close Reported by: Jared Biel
2015-04-08 Asterisk Development Team <[email protected]>
* Asterisk 11.17.1 Released.
* Mitigate MitM attack potential from certificate with NULL byte in CN.
When registering to a SIP server with TLS, Asterisk will accept CA
signed certificates with a common name that was signed for a domain
otherthan the one requested if it contains a null character in the
common name portion of the cert. This patch fixes that by checking
that the common name length matches the the length of the content we
actually read from the commonname segment. Some certificate
authorities automatically sign CA requests when the requesting CN
isn't already taken, so an attacker could potentially register a CN
with something like www.google.com\x00www.secretlyevil.net and have
their certificate signed and Asterisk would accept that certificate
as though it had been for www.google.com.
ASTERISK-24847 #close
Reported by: Maciej Szmigiero
patches:
asterisk-null-in-cn.patch uploaded by mhej (license 6085)
AST-2015-003
2015-04-01 Asterisk Development Team <[email protected]>
Link up your team and customers Phone System Live Chat Video Conferencing
Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.
Check your inbox!
We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).
Upon verification you will be directed to the 3CX setup wizard.