Re: [Design] Re: Opportunistic Encryption is now working under Linux 2.5

>>>>> "David" == David S Miller <[email protected]> writes:
    >> I have some questions/comments:
    >> 
    >> 1) do we really need linux/include/rtnetlink.h? Shouldn't this
    >> be coming from the kernel headers?
   
    David>    Yes.  You can't include Linux kernel headers directly in a
    David>    user-space 
    David>    application as they're not guaranteed to compile in user-space.

    David> That's hogwash, including linux/rtnetlink.h and linux/xfrm.h are the
    David> only sane ways you can get at the IPSEC userspace APIs right now.

    David> Or do you suggest that we should wait for GLIBC to get these in

  Would that GLIBC lived in /usr/src next to /usr/src/linux :-)

  I simply would prefer that we -I/my/kernel/source/include to get the right
headers, if they are in the kernel.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] [email protected] http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html