[asterisk-bugs] [Asterisk 0013285]: New config parameter to enforce encryption

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13285 
====================================================================== 
Reported By:                sgofferj
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13285
Category:                   Channels/chan_iax2
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-08-11 12:02 CDT
Last Modified:              2008-08-11 13:38 CDT
====================================================================== 
Summary:                    New config parameter to enforce encryption
Description: 
Currently, Asterisk does not indicate in any way if an IAX connection is
really encrypted. Even the (E) in iax2 show peers only indicates the
configured capability.
In sensitive environments it is imperative to know if a call is actually
encrypted.

Therefore I'd like to suggest a new directive per peer for iax.conf:
forceencryption=(yes|no)
The directive will cause a call not to be set up (=fail) if not both sides
agree on encryption.


====================================================================== 

---------------------------------------------------------------------- 
 (0091311) blitzrage (administrator) - 2008-08-11 13:38
 http://bugs.digium.com/view.php?id=13285#c91311 
---------------------------------------------------------------------- 
I do agree with the suggestion, however features need to be filed with
code. 

I will leave this bug open for a few days to see if anyone would like to
pick this up and make the change since it appears that it should be fairly
straight forward. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-11 13:38 blitzrage      Note Added: 0091311                          
======================================================================