Alan Cox wrote:
> > associated with each connection. If you have multiple boxes under your
> > control, this information can be useful (i.e. if you control the
> > client system, then you can assume that the information which identd
> > provides is valid).
>
> This is not the case. You cannot prove a third party intercepted and
> changed the session. identd needs to have secure hashes added to it to make
> it useful for anything.
Are you talking about generic TCP hijacking, or something specific to
ident?
--
Glynn Clements <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]