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] [day] [month] [year] [list]
Message-ID: <AANLkTina0PZmTaQLw228k5kQnE=GPyYJzcUbO3nkkHF3@mail.gmail.com>
Date:	Mon, 2 Aug 2010 16:42:47 +0200
From:	Damjan Jovanovic <damjan.jov@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: a Great Idea - include Kademlia networking protocol in kernel

If all you want to do is share a Kademlia implementation among
applications, it should be in a user-space shared library. This
library could also be ported to other operating systems, unlike a
Linux-only kernel module that portable applications wouldn't want to
use anyway.

I think Kademlia only belongs in the kernel if something in the kernel
itself needs it. And even then it shouldn't be exported to user space.

Damjan Jovanovic

On Mon, Aug 2, 2010 at 4:29 PM, hp fk <fkhp101@...il.com> wrote:
> ---------- Forwarded message ----------
> From: hp fk <fkhp101@...il.com>
> Date: 2010/8/2
> Subject: Re: a Great Idea - include Kademlia networking protocol in kernel
> To: Valdis.Kletnieks@...edu
>
>
> popular file sharing p2p applications like emule and bittorrent,
> innovative application like Osiris each has its own Kademlia protocol
> implementation in userspace presently. the imaginable kernel support
> needed is to reduce many repeated (different or same) Kademlia
> protocol implementations running in userspace to a consolidated one at
> kernel level, so that the Kademlia protocol as a p2p network
> infrastructure is provided in kernel and any p2p application could
> just use the interface provided by kernel, thus a great p2p network is
> easily created, and  applications on that network infrastructure could
> grow rapidly.
>
> 2010/8/2  <Valdis.Kletnieks@...edu>:
>> 1) You failed to explain what kernel support, if any, would be needed for this
>> protocol.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ