But what prevent you from throwing away ID content in this case,
as you know that it is unauthenticated (you may even not to log it), and
allow user to connect? User has already exposed the
content of ID, the damage (if any) has already occured,
so what you will you protect by rejecting the connection?
Making the problem visible to it will not happen in the future.
If you consider it as a problem, than there ara other
means to make it visible, e.g. audit that something is
probably wrong.
But you said:
And I feel that I need to reject anonymous connections that have an ID
to protect the anonymity of the user.
And I just wonder how you are going to protect
user's anonimity if user himself has already exposed
his identity.
_______________________________________________
IPsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipsec
