[IPSec]A problem with xfrm_check_output()

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

 



Hi, Alexey

After reading the code, I found a problem with function
xfrm_check_output()

As you have pointed out in the last mail, if we check against
precaluclated 
dst->pmtu before doing transformation, it will result in underestimation
of mtu 
for esp due to alignment paddings and for IPCOMP it will be totally
unfair.

The function xfrm_check_output() has the same problem, because it's
invoked 
before doing transformation.

I think it's appropriate to invoke xfrm_check_output() after the
transformation.
Only after doing the transformation can we know the actual esp alignment
padding
and the actual IPCOMP packet size.

What's your advice?

Thanks,
Forrest

-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux