On 07/27/2011 01:35 PM, Matthew J. Roth wrote:
This feature would actually be a bit like "alwaysauthreject" in that it breaks RFC compliance for the sake of security, so it's not a completely lost cause. However, pining away on a mailing list about how simple the work would be instead of doing it yourself is.
'alwaysauthreject' in not imcompliant with any RFCs; the RFCs define response codes that *can* be used to indicate (for example) that the Request URI does not represent a target known to the receiver (404 Not Found), but does not mandate that the server respond with that code in that situation.
-- Kevin P. Fleming Digium, Inc. | Director of Software Technologies Jabber: [email protected] | SIP: [email protected] | Skype: kpfleming 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
