MIME-Version: 1.0
In-Reply-To: <rt-3.8.6-50549-1331637960-532.28038-0-0@isc.org>
X-Mailer: MIME-tools 5.428 (Entity 5.428)
Content-Disposition: inline
References: <RT-Ticket-28038@isc.org> <4F461680.1090205@redhat.com>
 <4F4625A7.7080009@redhat.com> <20120223115149.GB9312@movementarian.org>
 <rt-3.8.6-50542-1329997918-1756.28038-5-0@isc.org>
 <rt-3.8.6-50535-1330033936-1055.28038-5-0@isc.org>
 <4F5F2E06.7080609@redhat.com>
 <rt-3.8.6-50549-1331637960-532.28038-0-0@isc.org>
Content-Type: text/html; charset="UTF-8"
Message-ID: <rt-3.8.6-50182-1333408513-1669.28038-0-0@isc.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
RT-Send-CC:
Content-Length: 774

On Tue Mar 13 11:26:00 2012, jpopelka@redhat.com wrote: <br />
&gt; Hi, <br />
&gt;  <br />
&gt; Red Hat's Security Response Team would like to know <br />
&gt; whether you consider this to be a security related flaw <br />
&gt; or just an ordinal bug so we could possibly close our <br />
&gt; security-related tickets. <br />
&gt;  <br />
&gt; Thank you <br />
&gt;  <br />
&gt; -- <br />
&gt; Jiri <br />
&gt; <br />
I apologize for the delay in responding. &nbsp;<br />
<br />
Currently we do not consider this to be a security related flaw, as<br />
it appears to be mostly a configuration issue. &nbsp;However the user<br />
seeing this with a value of 80 000 is a concern. &nbsp;We never<br />
received additional information for that case though.<br />
<br />
<br />