lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 08 Mar 2008 23:46:13 +0900
From:	Kazunori MIAZAWA <>
To:	David Miller <>
Subject: Re: [PATCH][IPSEC] inter address family IPsec tunnel on the fly

David Miller wrote:
> From: Kazunori MIYAZAWA <>
> Date: Fri, 07 Mar 2008 15:32:09 +0900
>> David Miller wrote:
>>> I also wonder if the PF_KEY limitation really exists.  For example we
>>> will set x-> etc. from the SADB_EXT_ADDRESS_PROXY attribute
>>> if present.
>> Yes, we have SADB_EXT_ADDRESS_PROXY. But it is not enough, I think.
>> xfrm_selector has both src and dst so that we need some way to
>> specify the address is src or dst.
>> from RFC2367
> Thank you for this information.
>>> Finally, if the determination can be made in the data path, it
>>> by definition could be made during rule insertion which is much
>>> more efficient and appropriate.
>> I agree with you.
> I am sure there is a simple solution to this problem somewhere,
> it is just hiding :-)

I think one solution is xfrm_state has two inner_modes
and switch them when the family is any.

This is just an idea :-p

Kazunori Miyazawa
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists