tis 2006-10-03 klockan 00:35 +0200 skrev Henrik Nordstrom:
> I have actually used it in in real life. Was a some vendor support forum
> NNTP server requiring authentication and encryption to protect the
> passwords. But I have no problem with removing the port from the
> suggested default configur
fre 2006-09-29 klockan 16:07 -0600 skrev Duane Wessels:
> Our default ACL configuration allows CONNECT requests to port 563,
> which is for NNTP over SSL. Assuming that nobody really uses NNTP
> over SSL, especially through an HTTP proxy, I suggest that we
> remove it from the defaults.
I have ac
On Sat, 2006-09-30 at 18:33 +0200, Guido Serassio wrote:
> Hi,
>
> At 03.34 30/09/2006, Robert Collins wrote:
> >On Fri, 2006-09-29 at 16:07 -0600, Duane Wessels wrote:
> > > Our default ACL configuration allows CONNECT requests to port 563,
> > > which is for NNTP over SSL. Assuming that nobody
Hi,
At 03.34 30/09/2006, Robert Collins wrote:
On Fri, 2006-09-29 at 16:07 -0600, Duane Wessels wrote:
> Our default ACL configuration allows CONNECT requests to port 563,
> which is for NNTP over SSL. Assuming that nobody really uses NNTP
> over SSL, especially through an HTTP proxy, I suggest
On Fri, 2006-09-29 at 16:07 -0600, Duane Wessels wrote:
> Our default ACL configuration allows CONNECT requests to port 563,
> which is for NNTP over SSL. Assuming that nobody really uses NNTP
> over SSL, especially through an HTTP proxy, I suggest that we
> remove it from the defaults.
Agreed.
Our default ACL configuration allows CONNECT requests to port 563,
which is for NNTP over SSL. Assuming that nobody really uses NNTP
over SSL, especially through an HTTP proxy, I suggest that we
remove it from the defaults.
