netdev - Re: [PATCH] [NET] Exporting of some IPv6 symbols for HIP and SHIM6 experimentation

lists.openwall.net		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 linux-hardening linux-cve-announce 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:	Tue, 6 May 2008 11:07:49 +0300 (EEST)
From:	Miika Komu <miika@....fi>
To:	YOSHIFUJI Hideaki / 吉藤英明 
	<yoshfuji@...ux-ipv6.org>
cc:	davem@...emloft.net, netdev@...r.kernel.org
Subject: Re: [PATCH] [NET] Exporting of some IPv6 symbols for HIP and SHIM6
 experimentation

On Mon, 5 May 2008, YOSHIFUJI Hideaki / µÈÆ£±ÑÌÀ wrote:

Hi,

> In article <Pine.SOL.4.64.0805050847400.8815@...konen.cs.hut.fi> (at Mon, 5 May 2008 08:55:49 +0300 (EEST)), Miika Komu <miika@....fi> says:
>
>> On Tue, 29 Apr 2008, David Miller wrote:
> :
>>> This is not how we do things.
>>>
>>> When the HIP implementation is submitted for inclusion, the module
>>> exports can be added, not before.
>>
>> I am sorry but this somewhat conflicts with your earlier statement:
>>
>> http://www.linux.sgi.com/archives/netdev/2005-03/msg01214.html
>>
>> We took an huge effort in our project to move the HIP implementation to
>> the userland. I feel puzzled on how to continue. Please give some advice?
>
> Miika, where are your other patches on top of this?
> This kind of change might be okay, but it must be along with
> its users, at least.

we are maintaining a separate kernel module (GPLv2) for the HIP socket 
handler for experimentation purposes. If you want to have a look it, you 
can e.g. download the nightly tarball and have a look at the hipsock 
directory:

http://infrahip.hiit.fi/hipl/hipl.tar.gz

The kernel module is currently out of synch with the latest draft, so I 
need to update it. The purpose of the kernel module is to be a "wrapper" 
for IPv6 socket calls because HIP can use ORCHID IPv6 addresses. We would 
like to experiment with various socket options for HIP and SHIM6. 
Exporting the symbols would make HIPL developers and users life easier. 
Once we have a clear set of requirements for the kernel module, we can 
contribute the changes to the vanilla kernel.

-- 
Miika Komu                                       http://www.iki.fi/miika/