Re: Logging the source port?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Stephane Bortzmeyer writes:
On Fri, Nov 13, 2009 at 10:49:36AM +0100,
Arnt Gulbrandsen <arnt@xxxxxxxxxxxxxxxxxxx> wrote a message of 11 lines which said:

Therefore, I think it's safer to say that it's the NAT operator's responsibility to log enough. Umpteen million web sites will continue to use apache's common log format, so the NAT operator has to log what's needed to work with that format anyway.

How could it be possible? The only way I see for the NAT operator to
be able to say that the customer X went to www.priv.no at 2241 UTC is
to log not only the source-address/source-port mapping but also the
*destinations*, which create obvious privacy issues (and would make the log *much* larger).

Yes. But do you see a way to avoid that, except by unrealistic declarations such as "all apache installations that use the common log format must be changed"? It's not just apache either, all other (web and other) servers that don't log source port.

(Btw, there is no www.priv.no, and these days I don't think you can get anything else under .priv.no either. The dozen-odd people who have .priv.no domains are allowed to keep them, that's all.)

Arnt
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]