[asterisk-bugs] [Asterisk 0017282]: UPGRADE-1.6.txt doesn't mention insecure=very/yes removal

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17282 
====================================================================== 
Reported By:                stuarth
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17282
Category:                   Documentation
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.6 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-05-04 09:37 CDT
Last Modified:              2010-05-04 14:43 CDT
====================================================================== 
Summary:                    UPGRADE-1.6.txt doesn't mention insecure=very/yes
removal
Description: 
The previously-deprecated insecure=very and insecure=yes options have been
removed but this isn't mentioned in UPGRADE-1.6.txt
====================================================================== 

---------------------------------------------------------------------- 
 (0121360) stuarth (reporter) - 2010-05-04 14:43
 https://issues.asterisk.org/view.php?id=17282#c121360 
---------------------------------------------------------------------- 
There's a patch here if you can use it.

http://www.openbsd.org/cgi-bin/cvsweb/ports/telephony/asterisk/patches/patch-UPGRADE-1_6_txt?rev=1.1;content-type=text%2Fx-cvsweb-markup

By the way I marked this as major as insecure=very is in sample configs
all over the net and as port maintainer I've heard from a few people ran
into this problem. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-04 14:43 stuarth        Note Added: 0121360                          
======================================================================